Re: Problem with libtool and Absoft Fortran on Mac OS X

[Jeff Squyres]

Thanks Ralf!

FWIW, I'm not sure it's a mailman issue -- I've seen the bounce messages that 
come back from mailman when you send a message that is over mailman's limit.  
We definitely got something different.  It might be worth asking the 
SMTP-mesiters at gnu.org, if you know those people at all.  I only keep beating 
this dead horse because the bounce message literally did not say why the 
message was refused -- very confusing...


On Feb 6, 2010, at 4:13 AM, Ralf Wildenhues wrote:

> Hello Tony, Jeff,
> 
> I've increased the maximum message size on this list from 200K to 500K
> now.  Hope that helps.
> 
> Now to the actual issue:
> 
> * Jeff Squyres wrote on Wed, Feb 03, 2010 at 06:04:42PM CET:
> > > From: "Tony Goelz" <address@hidden>
> > >
> > > Absoft's ongoing involvement in the Open MPI testing process has 
> > > uncovered a
> > > problem with libtool and our compilers running on Apple's OS X. In a 
> > > nutshell,
> > > libtool is passing unsupported options to our compiler drivers when 
> > > creating
> > > dynamic shared libraries.
> 
> > > The problem is the options libtool is passing when using our compiler to 
> > > perform
> > > the link of the dynamic library (from line 9 of make_output):
> > >
> > > -install_name /usr/local/lib/libtest.0.dylib
> > > -compatibility_version 1
> > > -current_version 1.0
> > >
> > > Our compilers report these as unrecognized options and the link fails.
> 
> The issue is simple: libtool has not been ported to Absoft on darwin.
> If you are interested in helping with such a port, we need the
> following: pointers to manuals for the compiler(s) and the linker that
> the compiler uses; names under which the compiler(s) are known, and
> possibly other ways to identify them (e.g.: --version output matches
> *Absoft\ * or something like that); somebody who would be willing to try
> out proposed patches against the development version of Libtool and run
> its testsuite on the system with those compilers.
> 
> Are you willing to help us with this?
> 
> First simple test: try setting $wl in the generated libtool script of
> the build tree of your package right for the $F77 and $FC compilers:
> something like
> 
>   sed '/BEGIN LIBTOOL TAG CONFIG: F[7C]/,/END LIBTOOL TAG CONFIG/{
>          s/wl=.*/wl="-Wl,"/
>        }' libtool  > libtool-new
>   mv -f libtool-new libtool
> 
> (please check that this looks ok).  Then try to build your software.
> 
> Thanks,
> Ralf
> 


-- 
Jeff Squyres
address@hidden

For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/