Tim,
Many thanks for this -- as a result of this I believe that shared
libraries now _do_ build successfully on OSX!
It does indeed seem that libtool was messing up the building of shared
_Fortran_ libraries, but managing C ones fine. It initially looked as
if automake was generating the wrong invocation of libtool, but it
wasn't. The libtool ChangeLog doesn't mention anything that seems
relevant, but it transpires that libtool 1.5.6 builds the libraries
correctly. So it was in the end as simple as a libtool deficiency.
As you'll have seen from commit messages, I've imported and merged
Libtool 1.5.6 (we had 1.5 before), so this is now the version we'll be
using when building the tree.
I've confirmed that chr (Fortran) and cnf (C) both still build from
scratch, but haven't checked other components systematically. So keep
an eye out for linking problems.
> the top section a command is issued using g77 as the linker. It
> looks
> like a simple oversight in the port of libtool to f77. Is that
> something that was done by us?
Oh no, wasn't me!
> Of course, why does this work
> on linux?
Though I've barely looked inside at all, I think that libtool is at
heart a big switch statement, with lots of platform-dependent logic in
it. So I'd guess that all this indicates is that when Apple submitted
their OSX libtool mods, they never checked that they could build shared
libraries using the g77 GCC front-end they didn't distribute.
Norman
--
----------------------------------------------------------------------
Norman Gray : Physics & Astronomy, Glasgow University, UK
http://www.astro.gla.ac.uk/users/norman/ : www.starlink.ac.uk
|