Re: SCO 5.0.6 with oss646b has old /usr/lib/libc.so.1

From: Brian K. White (brian_at_aljex.com)
Date: 09/28/05 

Date: 28 Sep 2005 13:36:55 -0400

> || GNU Development Tools (ver 5.0.7Kj)
> ^ |
> || Netscape Communicator (ver 4.7.0e)
> | |
> || OpenSSH - Secure Shell remote access utilities (ver 3.4p1)
> * |
> || PRNGD - Pseudo Random Number Generator Daemon (ver 0.9.23)
> * |
> || SCO OpenServer Enterprise System (ver 5.0.6j)
> * |
> || SCO OpenServer Linker and Application Development Libraries (ver
> 5. * |
> || SCO Skunkware 2000 (ver 2000.1)
> * |
> || Supplemental Graphics, Web and X11 Libraries (ver 1.3.2Ag)
> * |
> || zlib - unencumbered lossless data-compression library (ver 1.1.4)
> | |
> || OSS642a - Cron supplement (ver 1.0.0)
> | |
> || OSS646B - Execution Environment Supplement (ver 1.1.0j)
> v |
>
> Ooops Gcc is not listed in custom ????

heh, yes it is.
GNU Development Tools (ver 5.0.7Kj)

And I thought oss646c is a prerequisite of gnutools-5.0.7Kj and
gwxlibs-1.3.2Ag anyways.
...just checked, b or later so your supposed to be ok there.

You will have constant nagging problems on this box because a lot of whats
installed there overlaps and/or displaced each other.
ex: libz probably did some of both.
gwxlibs includes a libz that gets installed in /usr/lib, and which will be
found by some binaries once it appears even if they previously used the libz
that you have in /usr/local/lib
"skunkware2000" is a massive package that includes Glib, which also includes
a libz in /usr/local/lib, I bet there is at least one file in /usr/local/lib
that starts with libz and ends with a #
which would be one file being displaced by the same file in another package.
So you have at least 3 libz's , 2 in effect in different paths, and one
renamed so nothing sees it.

At one point Glib-1.5 from skunkware was the closest thing to what is now
gwxlibs.
A lot of skunkware hasn't been updated in a while and was all compiled
against the libraries in that Glib package.
Later to keep things sane, I didn't install Glib on new boxes but only
install the latest gnutools and gwxlibs and recompiled or found newer
versions of anything I was using that used to need Glib.
Much of that was included right in gnutools and gwxlibs anyways. The rest I
managed to build with gnutools and the linker-library package and is on my
web page you referenced originally.

The simplest way to assure all my binaries work is just install the latest
oss646 and gwxlibs. (or the latest MP on 5.0.7)
That's reasonably safe if your starting point is a box that only ever had
gwxlibs and isn't running for instance an old version of prngd or ssh that
may fail to start up when you take away it's particular version of some
library from /usr/local/lib or introduce a new library by the same name in
/usr/lib that didn't used to exist there.
Ever since gwxlibs came into existence, and as long as you start out not
needing any of the older library packages, then so far it's been pretty
"safe" to update gwxlibs to later versions without breaking things.

But starting with a box that has a lot of gnu software in production use
that was built from older skunware libs, it may possibly introduce a little
breakage installing gwxlibs for the first time.
Really you should uninstall any of the older stuff that appears in gwxlibs
and gnutools and then install gnutools & gwxlibs. That almost certainly will
break something but once you identify those and replace them with newer
versions that want gwxlibs, after that you should have painless updates as
long as sco keeps making gwxlibs compatible with previous versions. It's
been at least 4 releases by now and it's been the case so far.

If you don't uninstall the old skunkware packages and libs, that things are
less likely to break, many binaries do specifically look in /usr/local/lib
and gwxlibs installs it's stuff in /usr/lib, but you are left with a "messy"
box that's worth the bother to clean it up in my opinion.

Brian K. White -- brian@aljex.com -- http://www.aljex.com/bkw/
+++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
filePro BBx Linux SCO FreeBSD #callahans Satriani Filk!

Relevant Pages

  • Re: Locating a lost symlink file name
    ... Jeff Hyman wrote: ... Install gwxlibs and/or gnutools. ...
    (comp.unix.sco.misc)
  • Re: Locating a lost symlink file name
    ... | Jeff Hyman wrote: ... | Install gwxlibs and/or gnutools. ...
    (comp.unix.sco.misc)
  • Re: gwxlibs, mp5, gnutools5.0.7Kj symlinks conflict.
    ... It's not really an MP5 thing, it's an old issue that was raised ... gwxlibs, and gwxlibs has been updated with several new versions since then, ... use the box-to-box network install method in custom to install it on new ... filePro BBx Linux SCO FreeBSD #callahans Satriani Filk! ...
    (comp.unix.sco.misc)
  • Re: samba 3 on 5.0.5?
    ... Subject: samba 3 on 5.0.5? ... have been requested to install and configure Samba on it. ... I will be installing this remotely from a ssh connection. ... You probably have some version of oss646 and possibly gwxlibs too. ...
    (comp.unix.sco.misc)
  • osr6 gnutools gwxlibs
    ... Where is the equivalent of gnutools and gwxlibs for osr 6? ... I'm testing out my first osr6 box and installed the only updates I find ... I didn't knowingly install gwxlibs 2.0.0Eb and it doesn't appear in custom. ... That still leaves gnutools. ...
    (comp.unix.sco.misc)