Re: Enforcing cross-compilation

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

 



I have a configure.ac with the following just after AC_INIT
It works well.

<snip>

host=mips-elf
host_alias=mips-elf
ac_tool_prefix=mips-elf-
cross_compiling=yes

</snip>

This works fine, and when the AC_PROG_CC executes it looks exclusively for 'mips-elf-gcc' and fails if not found. It also sets 'CC=mips-elf-gcc' in all my Makefiles.

This is for a source tree of embedded firmware code.



Rob.





On 01/13/2011 08:44 AM, David NeÄas wrote:
Hello,

is it possible to enforce cross-compilation by some configure arugments
or env vars?

I cross-compile for win32 using the mingw32 cross-compiler toolchain but
I *can* run the created excutables as I have wine installed.  So
configure concludes I am not cross-compiling and this leads to various
problems later.

Of course, I can easily work around it by unregistering the binfmt
interpreter and thus losing the ability to run the MS executables
directly.  But generally, the cross-compilation check does not seem to
be reliable so I would like to be able to ask for cross-compilation
explicitly.

Yeti


_______________________________________________
Autoconf mailing list
Autoconf@xxxxxxx
http://lists.gnu.org/mailman/listinfo/autoconf


_______________________________________________
Autoconf mailing list
Autoconf@xxxxxxx
http://lists.gnu.org/mailman/listinfo/autoconf


[Index of Archives]     [GCC Help]     [Kernel Discussion]     [RPM Discussion]     [Red Hat Development]     [Yosemite News]     [Linux USB]     [Samba]

  Powered by Linux