On Tue, Mar 22, 2005 at 07:07:10PM +0100, Rafael Garcia-Suarez wrote: > Steve Peters wrote: > > This failure started after yum decided that I needed bind on my system > > to run some other piece of software (hate!). > > mmm, yum. (sorry) > > > Since then, the smokes started > > failing. Apparently, there are some differences between the structures > > used for the re-entrant functions above in libc and libbind. > > > > I tested a change in hints/linux.sh to remove libbind as a library Perl > > would > > attempt to link to and this make failure went away. My question is > > whether the blanket exclusion of libbind is correct or not. Are there > > versions of Linux in use that require libbind to function? If so, should, > > or > > can we even, limit the the inclusion of libbind to non-threaded Perls? > > I'm under the impression that removing libbind from libswanted > completely could help. (Journeying through known perl -V outputs to see > if its included in libs could help. Maybe this would broke under some > older glibcs.)
Well, here we go then. Below is a patch to hints/linux.sh that will remove bind from libswanted. Steve Peters [EMAIL PROTECTED] --- linux.sh.orig Fri Apr 16 11:13:58 2004 +++ linux.sh Tue Mar 22 17:09:48 2005 @@ -41,7 +41,8 @@ # BSD compatability library no longer needed # 'kaffe' has a /usr/lib/libnet.so which is not at all relevent for perl. -set `echo X "$libswanted "| sed -e 's/ bsd / /' -e 's/ net / /'` +# bind causes issues with several reentrant functions +set `echo X "$libswanted "| sed -e 's/ bsd / /' -e 's/ net / /' -e 's/ bind / / '` shift libswanted="$*"
