removing -arch from LDFLAGS

[David Strubbe]

Thanks. Well, let us suppose I am not concerned with building universal for
time being: then it sounds like

configure.ld_archflags-delete -arch ${arch}

is the appropriate approach for gfortran, since -m32/-m64 are preserved in
the LDFLAGS. Right?

David


On Tue, Nov 12, 2013 at 10:55 AM, Michael Dickens <michaelld at macports.org>wrote:

>  Hi David - gfortran, and non-Apple GCC in general, uses -m32 and -m64 to
> build for whatever the host arch is.  So, if the host computer is a PowerPC
> ("PPC"), then -m32 will build for 32-bit PPC ("ppc"); similarly, -m64 will
> build for 64-bit PPC ("ppc_64"); you won't be able to cross-compile for
> Intel using PPC-based GCC.  If your host computer is Intel ("i386" type),
> then -m32 will do 32-bit Intel ("x86" or "i386") and -m64 will do 64-bit
> Intel ("x86_64"); you won't be able to cross-compile for PPC using
> Intel-based GCC.   Have a look at the muniversal PortGroup for more
> information.  I hope this helps. - MLD
>
> On Tue, Nov 12, 2013, at 10:40 AM, David Strubbe wrote:
>
> gfortran just doesn't accept the "-arch" argument, so I am not sure if
> there is a way to take the arch into account. Can anyone else comment on
> how, if at all, building with gfortran should deal with build_arch?
>
>
> _______________________________________________
> macports-dev mailing list
> macports-dev at lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-dev/attachments/20131112/4ca026f1/attachment.html>