Re: [PATCH 3/3] Explicitly link against all utilized libraries

2013-05-02 Thread David Michael
Hi, On Wed, May 1, 2013 at 10:03 PM, Samuel Thibault samuel.thiba...@gnu.org wrote: Roland McGrath, le Wed 01 May 2013 19:01:14 -0700, a écrit : So if need be, we should make the installed libc.so linker script do AS_NEEDED ( libmachuser.so.1 libhurduser.so.1 ) or something like that. We

Re: [PATCH 3/3] Explicitly link against all utilized libraries

2013-05-02 Thread David Michael
Hi, I have built the Savannah glibc branch tschwinge/Roger_Whittaker with an AS_NEEDED patch[1], and this corrects the implicit linking issue as well. I would rather that simpler fix be applied to the glibc branch over using the patch in this thread, but the other two patches in this set are

[PATCH 3/3] Explicitly link against all utilized libraries

2013-05-01 Thread David Michael
Since libc is linked against libmachuser and libhurduser, they are implicitly linked against everything else on certain systems. On systems where implicit linking is disabled, a binary must explicitly link against each library from which it references symbols. * auth/Makefile (OTHERLIBS):

Re: [PATCH 3/3] Explicitly link against all utilized libraries

2013-05-01 Thread Roland McGrath
The Hurd API is that these things are available when you just use -lc. So if need be, we should make the installed libc.so linker script do AS_NEEDED ( libmachuser.so.1 libhurduser.so.1 ) or something like that. I'm somewhat confused about what you're doing so that you had an issue, however. How

Re: [PATCH 3/3] Explicitly link against all utilized libraries

2013-05-01 Thread Samuel Thibault
Roland McGrath, le Wed 01 May 2013 19:01:14 -0700, a écrit : So if need be, we should make the installed libc.so linker script do AS_NEEDED ( libmachuser.so.1 libhurduser.so.1 ) or something like that. We already do this actually. Samuel