On Thu, Jan 13, 2011 at 10:31:56AM -0700, Eric Blake wrote:
> On 01/13/2011 08:44 AM, David Nečas wrote:
> >
> > is it possible to enforce cross-compilation by some configure arugments
> > or env vars?
>
> Yes: call configure with explicit --build and --host arguments that differ.
OK, thanks als
I have a configure.ac with the following just after AC_INIT
It works well.
host=mips-elf
host_alias=mips-elf
ac_tool_prefix=mips-elf-
cross_compiling=yes
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-
On 2011-01-13 16:44 +0100, David Nečas wrote:
> 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.
>From the autoconf
In your case that the prefix of compilers are clearly different,
something like
./configure --host=i586-mingw32msvc --build=i386-pc-linux-gnu
may configure recognize that now it is working for cross compiling.
Please try.
Regards,
mpsuzuki
David Nečas wrote:
Hello,
is it possible to enforce
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?
Yes: call configure with explicit --build and --host arguments that differ.
>
> I cross-compile for win32 using the mingw32 cross-compiler toolchain
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 var
