This is the mail archive of the
fortran@gcc.gnu.org
mailing list for the GNU Fortran project.
Re: [libgfortran,patch] New autoconf test
- From: "François-Xavier Coudert" <fxcoudert at gmail dot com>
- To: "Daniel Franke" <franke dot daniel at gmail dot com>
- Cc: fortran at gcc dot gnu dot org
- Date: Tue, 9 Jan 2007 10:34:17 +0100
- Subject: Re: [libgfortran,patch] New autoconf test
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=uots+8MTsjQBPIPnT4WFtnv8kOR7NXAm23DwhvYGR1TuaBZfd84iAAfjYpp8OEuTW3eOigoExKv9BXk8A0YKj1gW/645pKYQuRakqNGjdHXmaPYRUR1phw+iP92T61FZ9+Q22Ih+JhQbScGY8Ht99nfVbSOV6lZG8q7q+YBZauQ=
- References: <19c433eb0701082354iefe2eahc6a41cc74fd03622@mail.gmail.com> <200701091020.04541.franke.daniel@gmail.com>
b) would it work in a cross-compiler setup?
When building non-native binaries, e.g. build=i686-pc-linux-gnu and
host=target=sparc-sun-solaris2.9, this will probably fail since one can not
execute sparc binaries on i686?!
I thought that, for a (build = B) != (host = target = T), we need two
different gfortran compilers: the final one, with configuration
described above, and one with (build = host = B) and target = T; then,
libgfortran is configured and built with the second one. At least,
that's what I think.
FX