This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: patch to libffi/configure.in to allow crosscompiling
Alexandre Oliva <aoliva@redhat.com> writes:
> On Jan 31, 2002, Adam Megacz <patches@lists.megacz.com> wrote:
> > Thank you; I will upgrade my autoconf to 2.50, research this, and
> > submit a reworked patch.
> Note that, unfortunately, we're not yet in a position of adopting
> autoconf 2.50, but by doing so, no patch will be necessary to address
> your concern: the new autoconf will probably generate code exactly as
> you expect (in fact, even better, because it won't possibly use
> incorrect defaults).
I don't quite understand. As it is, if somebody checks gcc out of CVS
and builds it, autoconf is never run -- instead, the CVS copy of
configure is used. It doesn't work when crosscompiling, so the build
fails.
If I am not mistaken, this means that in order to make gcc
crosscompile, we must do one of the following:
1) Add an invocation of autoconf to the configure scripts, and
require autoconf2.50 in order to build a cross-libffi
2) Re-run autoconf2.50 and check in the resultant configure script
3) Put in all the crud that was in my patch (I agree that this is
not a desirable option) so that autoconf2.13 works.
Is there another option that I don't see here?
- a