> -----Original Message----- > From: Bernd Schmidt [mailto:[EMAIL PROTECTED] > Sent: den 24 juni 2007 16:42 > To: Joakim Tjernlund > Cc: 'uClibc' > Subject: Re: libpthread vs libc dynamic link order > > Joakim Tjernlund wrote: > > I never got the hang of the hidden_{proto,def} stuff. I think these > > are way overcomplex. > > I don't see anything complex about hidden_proto/def. All they do is > create a hidden version of the symbol (e.g. __GI_pthread_cond_signal) > and an exported alias (pthread_cond_signal). Then, by using > hidden_proto inside the library code before referencing the > function, we > access the hidden symbol instead of the exported one, which gives us > exactly what we want. > > > I don't think this is the way either and > > that you need a thread expert to make sense of all the details. > > Any particular reason to object to this?
After looking a little more I can't say I have any objection, but then again, I am no expert at this either. Try it and let list get back if it doesn't work out. Jocke _______________________________________________ uClibc mailing list [email protected] http://busybox.net/cgi-bin/mailman/listinfo/uclibc
