[Top] [All Lists]

RE: [uClibc] Re: uclibc mips and undefined symbols with nonzerosym

To: "Bradley D. LaRonde" <>, "Richard Sandiford" <>
Subject: RE: [uClibc] Re: uclibc mips and undefined symbols with nonzerosymbol table entry st_value
From: "Joakim Tjernlund" <>
Date: Mon, 10 May 2004 14:21:13 +0200
Cc: <>, <>
Importance: Normal
In-reply-to: <012701c43607$83aa65f0$8d01010a@prefect>
Original-recipient: rfc822;
> > The x86 and MIPS ABIs are very different though.
> I notice that the debian mipsel in
> has
> st_value == 0 for every UND FUNC, just like my x86 debian libraries.  This
> is very different than the uClibc where every UND FUNC has
> st_value != 0.  Interestingly if I link glibc's libpthread with uClibc's
> I see that most UND FUNCs then have st_value != 0.
> I would like to see how uClibc behaves I could somehow get ld to not
> generate any stubs in  libpthread.  Any idea why libpthread gets full stubs
> when linked with uClibc but no stubs when linked with glibc

This looks like the problem we had with dlopen() and friends when introducing
the new WEAK symbol handling.

in libc/misc/pthread/weaks.c you have stuff like:
weak_alias(__phtread_return_0, __phtread_once);

where __phtread_return_0 is non NULL:
int __phtread_return_0(void)
 return 0;

<Prev in Thread] Current Thread [Next in Thread>