On Wed, 1 Mar 2006, Alasdair Allan wrote:
> Tim Jenness wrote:
>> You haven't got the right flags for building libraries (the warnings are
>> irrelevant).
>>
>> On OSX tiger with g95 the only wqay we have got starlink built is:
>>
>> 1. Build a libf95 shared library from the g95 source (the default
>> distribution only has a .a)
>> 2. Remove the -nostdlib from the libtool library building line.
>>
>> Otherwise you get all sorts of problems with the SystemStubs not being
>> properly resolved.
>
> Oh joy...
>
It's not overly complicated. Brad can send you a libf95.dylib (which will
work so long as you put it in the same place he built it for) and you can
tweak the installed libtool (from buildsupport) so that ./configure will
pick up the correct mod. (I think the -nostdlib was added by Peter so that
the Panther g77 build would work - it is probably needed for static
libraries like you have).
Of course, this may all be a red herring and the real problem is simply
that the g95 binary is built for Panther using gcc3 and that a relink of
libf95.a using gcc4 will fix it (but I don't recall that working for me
when I was investigating this back in August).
Note that you can build libf95 without needing a gcc source tree or
anything. The runtime library is simply a library that you untar from
within the g95 source tarball and build separately.
--
Tim Jenness
JAC software
http://www.jach.hawaii.edu/~timj
|