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: test-installation.pl problem


At 02:10 PM 24/07/2000 +0200, you wrote:
<snip>

>The libraries have initialization functions which might get called.
>The program is linked against each and every lib!  It could be a bug
>in the dynamic linker or in one of these initialization functions.
>Debug with LD_DEBUG set in the environment (LD_DEBUG=help ls gives
>options).
>
>Andreas

Well, I gave the LD_DEBUG settings a try. It's funny, the linker didn't
actually recognize the settings unless I called it explicitly
(/lib/ld-linux.so.2 -> /lib/ld-2.1.3.so), ie. /lib/ld-2.1.3 test-prg9414.

Here is a list of my linkers: (in /lib)
ld-2.1.3.so
ld-linux.so -> ld-linux.so.2
ld-linux.so.1 -> ld-linux.so.1.9.9
ld-linux.so.1.9.9
ld-linux.so.2 -> ld-2.1.3.so

I tried using ld-linux.so.1, which segfaulted.

These two points led me to believe that for some reason ld-linux.so.1 was
being called and no so.2. This was confirmed when I looked at the FAQ again
(grepped for LD_DEBUG). There was an item about upgrading from glibc 2 to 2.1.

So, I set LD_LIBRARY_PATH=/tmp (previously not set), and tried running
/tmp/test-prog9414, which worked. So, the question is, why is ld-linux.so.1
my default linker, and how do I change that? Was I supposed to move it
along with my other libc5 libraries out to /usr/i486-linuxlibc5/lib ?

Austin
----------
Austin Hung * University of Waterloo, 3N Computer Engineering
wizard_auz@engineer.com  *  http://ece.uwaterloo.ca/~a2hung/
"I Want To Believe"

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