[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: libc.so.6 with link time reference
- To: Hava Lester <hava18(at-nospam)hadassah.org.il>
- Subject: Re: libc.so.6 with link time reference
- From: guy keren <choo(at-nospam)actcom.co.il>
- Date: Wed, 31 Oct 2001 12:22:12 +0200 (EET)
- cc: <linux-il(at-nospam)linux.org.il>
- Delivered-To: linux.org.il-linux-il@linux.org.il
- In-Reply-To: <3BDFB16B.AEB3D60A@hadassah.org.il>
- Sender: linux-il-bounce(at-nospam)cs.huji.ac.il
On Wed, 31 Oct 2001, Hava Lester wrote:
> I'm trying to run a program based on vtk on a linux with RedHat (I guess
> version 7.1 - the source is called linux-2.2.16) and get the error:
>
> vtk: error while loading shared libraries: /usr/lib/libVTKCommon.so: symbol
> __sysconf, version GLIBC_2.2 not defined in file libc.so.6 with link time reference
>
> Please could someone throw some light on this?
> ls -l /lib/libc* gives /lib/libc.so.6 -> libc-2.1.92.so
as you see (and said) you have glibc 2.1, and that 'vtk' (whatever it is)
was compiled with glibc 2.2 .
> Would installing glibc22 mess up my kde?
upgrading the C library (glibc) affects not just kde, but rather your
whole system. its a rather delicate issue, and not too rarely causes one's
system to become completely broken (some people on this list reported such
cases in the past).
alternative, and perhaps easier solutions:
1. get vtk's sources and compile it on your PC
2. search in 'rpmfind.net' for an rpm of vtk that was compiled on the same
system as the one you are using. by the way - not the kernel's version
(2.2.16) - but the distribution type and version (on red hat systems,
if you login via a regular console, not gdm/kdm/xdm, you see the
version number before the 'login:' prompt).
3. install glibc2 and all the other libraries that 'vtk' needs in a
seperate directory, and run 'vtk' with your LD_LIBRARY_PATH set
to that seperate directory (e.g. if you use tcsh:
setenv LD_LIBRARY_PATH /path/to/new/dir:${LD_LIBRARY_PATH}
or if you use bash:
LD_LIBRARY_PATH=/path/to/new/dir:${LD_LIBRARY_PATH}
export LD_LIBRARY_PATH
this will require performing library hunting. it'lll be easiest if you
set LD_LIBRARY_PATH to contain ONLY the seperate directory, and then
you'll be told of missing lbraries, which you'll need to take from a
distribution that uses glibc2, and place there, and repeat until it
works.
i'd go for '2', and if it doesn't work - go for '1'.
or you could simply upgrade your system to a new distribution that _is_
based on glibc2 - and that might prove to be the easiest path to take.
> Also (unrelated) has anyone had experience inserting a linux pc into a Sun
> environment running NIS+ (server SunOS 5.5.1, other hosts Solaris 2.4, 2.5 and 8) ?
only NIS here - and it mostly works now (used to cause a lot of problems
in the past, thought that was with redhat 4.2). not sure linux's NIS has
support for NIS+ - but perhaps it does by now.
--
guy
"For world domination - press 1,
or dial 0, and please hold, for the creator." -- nob o. dy
=================================================================
To unsubscribe, send mail to linux-il-request@linux.org.il with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail linux-il-request@linux.org.il