Peter,
Are you certain it is the need for -fPIC is limited at all with
regard to static code in shared libs. In his article, Drepper says...
The most important recommendation is to always use -fpic or -fPIC
when generating code which ends up in DSOs. This applies to data as
well as code. Code which is not compiled this way almost certainly
will contain text relocations. For these there is no excuse. Text
relocations require extra work to apply in the dynamic linker. And
argumentation saying that the code is not shared because no other
process uses the DSO is invalid. In this case it is not useful to
use a DSO in the first place; the code should just be added to the
application code.
I also notice that on Fedora Core 4, they are adding -fPIC to the
RPM_OPT_FLAGS for x86_64. I see this as a red flag that this issue
exists.
Jack
-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc. Get Certified Today
Register for a JBoss Training Course. Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
_______________________________________________
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fink-devel
