[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: shared library problem on macos with free software scientific packag
Re: shared library problem on macos with free software scientific package...
Fri, 7 Jan 2011 14:21:31 +0100
On Fri, Jan 7, 2011 at 13:30, Ed Hartnett <address@hidden> wrote:
> For some reason, the libtool script that ships with the dist is ignored,
> and the build tries to use /usr/bin/libtool instead, and that's where it
> comes unglued. This may have nothing to do with macos, but may mearly be
> happening on this machine because an old version of libtool is installed
Attention! On Mac OS, /usr/bin/libtool is not GNU libtool but rather a
helper script that is called internally when creating a shared
library. Your build log clearly shows that ../libtool (i.e. GNU
libtool) is called to link the library. The compiler, i.e. g95, then
calls /usr/bin/libtool internally. The point where it breaks is that
your /usr/bin/libtool does not understand the -force_load parameter,
which was introduced as " -Wl,-force_load,../f90/.libs/libnetcdff90.a"
in the compiler command line.
As discussed on this very list, in
-force_load linker flag is only supported on Mac OS 10.6 and up.
The first essential in chemistry is that you should perform practical
work and conduct experiments, for he who performs not practical work
nor makes experiments will never attain the least degree of mastery.
-- Abu Musa Jabir ibn Hayyan (721-815)