libpthread vs libc dynamic link order
Bernd Schmidt
bernds_cb1 at t-online.de
Sun Jun 24 07:41:39 PDT 2007
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?
Bernd
--
This footer brought to you by insane German lawmakers.
Analog Devices GmbH Wilhelm-Wagenfeld-Str. 6 80807 Muenchen
Sitz der Gesellschaft Muenchen, Registergericht Muenchen HRB 40368
Geschaeftsfuehrer Thomas Wessel, William A. Martin, Margaret Seif
More information about the uClibc
mailing list