On Fri, 26 Feb 1999, Tony Nugent wrote:
> On Thu Feb 25 1999 at 11:01, "root of all evil (Rem)" wrote:
>
> > Hello, all of you LINUXers out there. I have upgraded my one machine to
> > SLACKWARE LINUX 2.0.35 and now netscape (several current versions)
>
> 2.0.35 is the version of the kernel, not the version of the slugware
> release. It's also not the latest kernel (2.0.36 - although 2.2.2 has
> only very recently been released), and I suspect this is not the very
> latest slugware release.
*SLAP* For that, you get a slap over the wrists.
> > is complaining that it can't load a library file called
> > libstdc++.<something>.so
> > (I can't remember the <something> which represents the version of
> > the library, but I've located the file and it looks ok to me) Does
> > anyone have a clue how to solve this problem? Is it a problem with
> > netscape or the set of software installed by the upgrade process?
> > I'd really like to get netscape working again.
Is the directory which libstdc++ is in included in your /etc/ld.so.conf?
Try ldd on your netscape binaries, and ldd on your libstdc++, and if you
are missing any of the libraries needed it should tell you. And if it's
trying to link against libc5 and libc6, then you have a real problem.
> >
> > Any help will really be appreciated. Thank you all in advance!
>
> Slackware -- you loose. Last time I heard, slugware was still using
> libc5 (which is broken and no longer supported) instead of glibc6, and
> still using the old g++/c++ development kit rather than the newer
> egcs/c++ compiler which uses the libstdc++ libraries.
Still using libc5, but if he's using Slackware 3.6, then glibc2 is
included (if he chose to include it). And egcs is included in Slackware,
if he chose it in the development series. And besides, why does he loose?
Lose perhaps, but ...
> The short-sighted solution is to install the relevant shared libraries
> onto your system to allow netscape to run.
Not a short-sighted solution. Just a temporary solution which probably
won't last more than a year or two.
> The long-sighted solution is to never touch slugware again and go with
> a real distribution like debian, suse, or redhat.
I would suggest that anyone new to unix/linux use one of those three. But
experienced sysadmins of unix would probably be more comfortable with
Slackware.
> [Ah-oh, I'm probably going to start a "distribution" war with this, but
> quite frankly I don't care. :) Point is that slugware is now a
> historical fossil that has no place except for very specific purposes
> as a hacker's installation.]
Slackware still has its uses. For anyone who's used to it, it can be
annoying to move to a distribution which stuffs about with buggy libc
libraries and strange directories all over the place.
--
.sig under deconstruction. Please watch out for falling stars.
+++ATM2 O- +++ATL3 +++ATM1
