Updating glibc is very tricky stuff, with many dependencies and
opportunities to break the system midway through installation. The usual
way to do it (at least in RedHat-land) is to update your distribution
installation.
This document discusses how to do a glibc install:
http://www.linuxdoc.org/HOWTO/Glibc2-HOWTO-1.html
it's targeted at upgrading from libc5, and the requirements might not
be as elaborate if you're coming from glibc2.0.
Nathan
On Wed, Dec 01, 1999 at 11:15:59AM -0800, Colin D Bennett wrote:
> I just installed JDK 1.2.2 on my Slackware 4.0 system, and I get a
> strange error message when I try to run anything.
> Here's what happens:
>
> ====
> duke:/usr/local/bin/jdk1.2.2/bin# ./java
> ./java: /bin/realpath: No such file or directory
> ./java: /bin/realpath: No such file or directory
> java was not found in /bin/i386/native_threads/java
> ====
>
> It looks like I have glibc 2.0.7, so I'm downloading glibc 2.1.2 from
> http://metalab.unc.edu/pub/gnu/glibc
>
> I suppose I have to compile it myself, huh?
> I currently have GCC 2.7.2.3 and Linux 2.2.6.
> So, do I need a new GCC also? What about G++? What about the C++
> libraries? Do I need to upgrade them too? How?
>
> Sorry I'm so full of questions! 8-)
>
> Thanks.
>
> Colin
>
>
>
> ----------------------------------------------------------------------
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]