Re: [Fink-beginners] Problem with Installing GILDAS with Fink

[Alexander H. <ale...@gm...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 7/24/11 10:25 AM, Sébastien Maret wrote:
> 
> Le 23 juil. 2011 à 14:17, Alexander Hansen a écrit :
> 
>>> 10.4 is no longer officially supported, but maybe the maintainer
>>>  will fix it--or somebody else can.
>>> 
>>> I get what may be the same error from gildas-201104f-2 with the 
>>> following setup:
>>> 
>>> Package manager version: 0.30.2 Distribution version: 
>>> selfupdate-cvs Fri Jul 22 18:46:43 2011, 10.4, powerpc Trees: 
>>> stable/main stable/crypto unstable/main unstable/crypto 
>>> local/main local/injected Xcode Version: 2.5-1
>>> 
>>> ... gfortran  -Wl,-commons,use_dylibs 
>>> built/powerpc-darwin-gfortran/hlp2tex.o  -o 
>>> /sw/src/fink.build/gildas-201104f-2/gildas-src-apr11f/integ/powerpc-darwin-gfor
>>>
>>>
>>
>>>
>>> 
tran/bin/hlp2tex \
>>> 
>>> -L/sw/src/fink.build/gildas-201104f-2/gildas-src-apr11f/integ/powe
>>>
>>> 
rpc-darwin-gfortran/lib
>>> -L/System/Library/Frameworks/Accelerate.framework/Framew 
>>> orks/vecLib.framework/Versions/Current/ -L/sw/lib 
>>> -L/usr/X11R6/lib -L/sw/lib/pyt hon2.6/config  -lpython2.6 -lutil 
>>> -lpng -lz -lfftw3 -lfftw3f  -L/sw/lib -lgtk-x1 1-2.0 
>>> -lgdk-x11-2.0 -latk-1.0 -lgio-2.0 -lpangoft2-1.0
>>> -lgdk_pixbuf-2.0 -lpangoc airo-1.0 -lcairo -lpango-1.0 -lfreetype
>>> -lfontconfig -lgobject-2.0 -lgmodule-2.0 -lgthread-2.0 -lglib-2.0
>>> -lintl   -lm /usr/bin/ld: unknown flag: -commons ...
>>> 
>>> 10.4's "ld" doesn't understand -commons except on 64-bit builds.
> 
> I don't think that Gildas can work without this flag. Is there an 
> equivalent in 10.4's ld?
> 
> Sébastien

According to 10.4's ld manpage:

- -commons treatment (64-bit only)
Specifies  how common symbols (tentative defintions) from object
files  interact  with  dynamic  libraries.   treatment  can  be:
ignore_dylibs,   use_dylibs,   or   error.    The   default   is
ignore_dylibs which means the static linker will  use  a  common
defintion  from an object file even if a true definition exisits
in a dynamic library.  If you want your code to  use  a  dynamic
library  definition,  then add the extern keyword to your tenta-
tive definition (e.g. change int foo; to extern int foo; ).  The
treatment  use_dylibs  means a definition form a dynamic library
should override a common symbol in an  object  file.

Note,  the 32-bit  linker  always uses this treatment.

The treatment error means the linker should abort whenever if finds a
common  symbol in  an object file and an external definition with the
same name in a dynamic library.

So it sounds to me like if you leave that out, the 32-bit linker will
default to the same behavior as -commons,use_dylib .
- -- 
Alexander Hansen, Ph.D.
Fink User Liaison
http://finkakh.wordpress.com/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk4sOTUACgkQB8UpO3rKjQ+PtwCfRUTqfzcM6oW/rjqq9voX6pMk
D+8An1+hVTdY/bUw1YNNkdUp9IcXByx4
=FUb+
-----END PGP SIGNATURE-----