This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug dynamic-link/21041] Fix for bug 20019 causes linker errors for shared libraries using longjmp
- From: "fweimer at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Thu, 12 Jan 2017 18:39:25 +0000
- Subject: [Bug dynamic-link/21041] Fix for bug 20019 causes linker errors for shared libraries using longjmp
- Auto-submitted: auto-generated
- References: <bug-21041-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=21041
Florian Weimer <fweimer at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also|https://sourceware.org/bugz |https://sourceware.org/bugz
|illa/show_bug.cgi?id=20489 |illa/show_bug.cgi?id=20019
--- Comment #3 from Florian Weimer <fweimer at redhat dot com> ---
(In reply to Phil Blundell from comment #2)
> (In reply to Florian Weimer from comment #1)
> > The bug is here:
> >
> > $ ld.gold -shared -z now -o libbar.so bar.o
> >
> > You must link against the relevant glibc DSOs if you use symbols from glibc,
> > otherwise the resulting shared object is undefined.
>
> Sorry, that was a poor testcase. However, linking -lc at this point doesn't
> make any difference.
And linking with gcc (without specifying -lc) also reproduces this issue.
> Linking -lpthread does, but the point is that libbar
> doesn't use any symbols from libpthread itself and has no reason to link
> with that library.
This is actually a very nice test case, thanks.
The “fix” for bug 20019 is clearly bogus and needs to be reverted.
--
You are receiving this mail because:
You are on the CC list for the bug.