autoconf
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Autoconf fix Darwin/MacOS X Fortran


From: Ralf Wildenhues
Subject: Re: Autoconf fix Darwin/MacOS X Fortran
Date: Fri, 25 Aug 2006 08:54:33 +0200
User-agent: Mutt/1.5.12 (2006-08-10)

Hello Peter, Bill,

* Peter O'Gorman wrote on Thu, Aug 24, 2006 at 02:47:04PM CEST:
> On Aug 24, 2006, at 5:06 PM, Ralf Wildenhues wrote:
> >* Bill Northcott wrote on Thu, Aug 24, 2006 at 09:59:40AM CEST:
> >>_AC_FC_LIBRARY_LDFLAGS

[... and -lgcc_s]

> >>Neither is necessary because ld automatically  includes them.

Only if you don't use -nostdlib, then gfortran automatically includes
them.

> I can't approve or apply this patch, but want to note that it seems  
> reasonable to me. Looks like libgcc_s and libgcc_s.10.4 (essentially  
> the same thing) get added to the link line, one comes from the  
> compiler in /usr/local, the other from the compiler in /usr.

Well, on some systems (also Darwin in some cases), Libtool uses
-nostdlib in shared library creation.  Wouldn't omitting gcc_s in this
case cause missing symbols, at least if the output file is a module
(say, it uses Fortran) and libgcc_s was not previously loaded by the
main application (that, say, only uses C)?

In that case it seems more appropriate to me to strip -lgcc_s from
inside libtool in the cases where we know that we don't need it (i.e.,
when not using -nostdlib), rather than stripping it in
_AC_FC_LIBRARY_LDFLAGS.

Cheers,
Ralf




reply via email to

[Prev in Thread] Current Thread [Next in Thread]