This is the mail archive of the glibc-linux@ricardo.ecn.wfu.edu mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: //lib/libc.so.6: undefined reference to `_dl_...@GLIBC_2.2'


> From: Andreas Jaeger <aj@suse.de>
> Date: 02 Jan 2001 08:19:04 +0100
>
> --prefix=/ is wrong.  RTFM, you need --prefix=/usr 

Are you really telling me that glibc 2.2 can ONLY be installed in
/usr/lib?  In exactly WHAT manual is that explained?  If you mean
"--prefix=/" is wrong because it generates paths like "//lib" and
"//include", wouldn't it be better to use "--libdir=/lib
--includedir=/include" rather than installing a second copy of glibc in
a second location and trying to switch my whole system from using
/lib/libc to using /usr/lib/libc without breaking anything?


> (check how Slackware does it!).  

I did check how Slackware does it.  Did you?  The Slackware binary
package I'm currently using installed everything in /lib, not /usr/lib.
Here are the contents of the Slackware 7.1 package a1/glibcso.tgz:

./
lib/
lib/incoming/
lib/incoming/ld-2.2.so
lib/incoming/libBrokenLocale-2.2.so
lib/incoming/libc-2.2.so
lib/incoming/libcrypt-2.2.so
lib/incoming/libdl-2.2.so
lib/incoming/libm-2.2.so
lib/incoming/libmemusage.so
lib/incoming/libnsl-2.2.so
lib/incoming/libnss_compat-2.2.so
lib/incoming/libnss_dns-2.2.so
lib/incoming/libnss_files-2.2.so
lib/incoming/libnss_hesiod-2.2.so
lib/incoming/libnss_nis-2.2.so
lib/incoming/libnss_nisplus-2.2.so
lib/incoming/libpcprofile.so
lib/incoming/libpthread-0.9.so
lib/incoming/libresolv-2.2.so
lib/incoming/librt-2.2.so
lib/incoming/libthread_db-1.0.so
lib/incoming/libutil-2.2.so
lib/incoming/libnss_db-2.2.so
lib/incoming/libdb-3.1.so
lib/incoming/libdb1.so.2.1.3
lib/incoming/libdb2.so.3
lib/libSegFault.so
usr/
usr/libexec/
usr/libexec/pt_chown
install/
install/doinst.sh

The "doinst.sh" script moves the libraries from /lib/incoming to /lib


> Now your installation is completly broken.  Remove everything from
> *your* broken installation and perhaps you're happy.

Even if I were still using the version that I compiled, what you're
telling me to do, REMOVE glibc, would KILL the system, not fix it.  Or,
by "installation" do you mean more than just the glibc I compiled and
later replaced?  If you're telling me to wipe the hard drive and
reinstall from CD, I'm not willing to do that just so I can get rid of a
few undefined references.


-- 
            -Dave Noelle,                 dave@Straylight.org
            -the Villa Straylight,  http://www.straylight.org
Coalition Against Unsolicited Commercial Email  ==  http://www.cauce.com

Quote of the Day:
I doubt, therefore I might be.   

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]