[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Migrating to glibc-pre2.1



Well, I had a Netscape 4.5 sitting around, and X is sorta working, so I
tried it.  In deb, I fix961212'ed the files in the install directory, then
ran the installer fine.  I fixed the files in the /usr/local/netscape
directory and tried running it.  It asked for libstdc++.so.2.8. I have
.2.9, but when I ln'ed 2.9 to 2.8 and netscape opened up fine.  Note,
however, that there were some errors,  due to the color problems I
mentioned earlier on this list.  I got Slashdot up, though I experienced
the general bugginess of NS 4.5 (which I had noticed before moving to deb
too)  I haven't tried a NS 4.0x yet.

Could someone out there forward me a full "rgb.txt" file from their X?  I
would be grateful.  I am currently using the "minimal" one that xpm
provides, and it's pretty ugly and is constantly spewing about not having
colors.  :-(


>I'm migrating to Debian sid with glibc-pre2.1. The one killer application that
>prevents me from switching away from glibc-1.99 is Netscape Communicator.
>
>If I copy all libraries netscape needs to a directory and let LD_LIBRARY_PATH
>point to that directory, `ldd netscape' shows me that it uses the libraries in
>those directory, except for libdl.so.1. That's with glibc-1.99.
>
>With glibc-pre2.1 and LD_LIBRARY_PATH pointing to the same directory, I just
>get a segmentation fault. I suspect it's a problem with /lib/libdl.so.1.
>Anyone with a clue how to fix this? I really want to get rid of my glibc-1.99
>system, and still be able to use netscape, of course.
>
>BTW, this is communicator 4.05. 4.5 gives me the `unresolved inheritance
>error'.
>
>Greetings,
>
>						Geert
>
>P.S. Needless to say, if I succeed, future XF68_FBDev binaries with hardware
>     acceleration support will be linked against glibc-pre2.1, to encourage
>     other people to upgrade :-) A similar trick caused the dead of libc4 on
>     Linux/m68k in 1995, while the Linux/ia32 guys are still trying to burry
>     libc4, hehe...
>--


--
Eric Anholt
anholt@teleport.com



Reply to: