This is the mail archive of the
mailing list for the autoconf project.
Re: cross compilation
- To: Tom Tromey <tromey at cygnus dot com>
- Subject: Re: cross compilation
- From: Pavel Roskin <pavel_roskin at geocities dot com>
- Date: Wed, 29 Sep 1999 12:17:32 +0400 (EEST)
- cc: Autoconf List <autoconf at gnu dot org>
> Here's another cross-compilation weirdness: in some situations the
> compiler in use can't actually link an executable. This can happen
> when building target libraries. Some code I have here has this
> # FIXME: We temporarily define our own version of AC_PROG_CC. This is
> # copied from autoconf 2.12, but does not call AC_PROG_CC_WORKS. We
> # are probably using a cross compiler, which will not be able to fully
> # link an executable. This should really be fixed in autoconf
> # itself.
> It would be nice to find a way to fix this. For instance, if we know
> we are cross-compiling (from the command-line arguments), then we
> could just not run the body of AC_PROG_CC_WORKS.
I don't think so.
In _most_ cases, the compiler should be able to link executables.
It is only in libc case when the ability to link anything other than
libraries is not required.
So it's libc where specific changes should be used.