Re: Problem with -current of 10/24

["STeve Andre'" <andres_(_at_)_msu_(_dot_)_edu>]

Well, I haven't built anything on my laptop.  This has been a test system
which I've gotten snapshots from and installed each time, so the snapshot
build was faulty.

Right, got you about linking and versions.  After I'd posted this I came
to pretty much the same conclusion.

Thanks.

So far, this is the only glitch I've found in OpenBSD on "my" machines
which I play with.  From my point of view its been pretty stable for a
while now.

--STeve Andre'

At 03:11 PM 10/25/00 -0500, Jeff Bachtel wrote:
> xterm is built by you from /usr/ports/x11/xterm. When you built it
> previously, it linked against the older curses library, and doesn't
> know that it can successfully link against the library a major version
> higher. Rebuild xterm and the error should disappear. Generally,
> unless you know that the newer version of a shared library conforms
> pretty darn closely to the API for its previous major version, its not
> that great of an idea to link them.
>
> This means, of course, that if you delete an old library when doing
> your openbsd upgrade, you can expect some fun going back through the
> ports and recompiling them (esp if you delete the older libc.so, like
> I did ;)
>
> jeff
>
> On Wed, Oct 25, 2000 at 01:55:15AM -0400, STeve Andre' wrote:
> > Running -current of 10/24 with X of 10/23 (i386), I found that I could
> > bring X up, but trying to bring up an xterm failed.
> >
> > Digging into it a bit xterm wants libcurses.so.7.1 and 8.0 is in /usr/lib.
> >
> > Once I did the horrid kludge of linking the 8.0 to 7.1, xterm worked.  What
> > is the *right* way to fix this?
> >
> > --STeve Andre'
> >
> >
> >
>
> --
> Jeff Bachtel  (NOC,CIS,TAMU)    http://www.cepheid.org/~jeff
>                                 [finger jeff_(_at_)_cepheid_(_dot_)_org for PGP key]
> Mountain Dew and doughnuts...
> because breakfast is the most important meal of the day.