Martin Costabel wrote:
> Jean-François Mertens wrote:
> []
>> Do not understand fully this argument.
>> I have exactly the same output from the above 'nm -m' command on 10.4;
>> so apparently _ up to what is visible from this output _ the result
>> of the nmedit command is the same on 10.4 and 10.5...
>> (that is what made me ask rather about possible differences in ld).
> 
> If I understand correctly what nmedit -s is supposed to do, it does two 
> things, one visible and the other one invisible (except when it leads to 
> crashes):
> 
> The visible part is that is transforms external symbols into private 
> externals, thus rendering them inaccessible from the outside.
> 
> The invisible part is that it makes sure that other parts of the library 
> that need this symbol still have access to it. And this is where I 
> suspect Leopard's nmedit fails. But I don't know how to test this 
> hypothesis.
> 

So the symbol is still there on 10.5, but is private extern? That is,
indeed, what nmedit is supposed to do. There are other issues with
nmedit on Leopard (it refuses to strip global coalesced symbols -
whatever they are) that mean that I will have to patch libtool.

I'll try to get around to building xmms.

In the meantime, does something like this work for you in a patchscript
(sed script is all on one line)?

sed -e "[EMAIL PROTECTED]@ -exported_symbols_list
\$output_objdir/\${libname}-symbols.expsym\'@g" < configure > configure.new
mv configure.new configure

Peter
-- 
Peter O'Gorman
http://pogma.com

-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Fink-devel mailing list
[email protected]
http://news.gmane.org/gmane.os.apple.fink.devel

Reply via email to