I'm using autoconf 2.53.
When I run configure, I override CC and the like
in the environment to point to my cross-compiler like this:
CC=/opt/hardhat/devkit/ppc/405/bin/ppc_405-gcc
AR=/opt/hardhat/devkit/ppc/405/bin/ppc_405-ar
RANLIB=/opt/hardhat/devkit/ppc/405/bin/ppc_405-ranlib CFLAGS="-mcpu=403
-D__PPC405__" ./configure --prefix=/
Configuring without --host or --build yields the error
"If you meant to cross compile, use `--host'."
Configuring with --host but without --build yields the warning
"configure: WARNING: If you wanted to set the --build type, don't use
--host.
If a cross compiler is detected then cross compile mode will be used."
So I configure with both --host and --build, but that's really annoying,
as I posted originally. I just can't win. How do I configure for
cross-compiling
without warnings or errors, and without hard-coding info about the build
machine into my build scripts?
- Dan
-----Original Message-----
From: Akim Demaille
To: Guido Draheim
Cc: Dan Kegel; 'address@hidden'
Sent: 01.10.2002 23:02
Subject: Re: When crosscompiling, does configure really need --build?
"Guido" == Guido Draheim <address@hidden> writes:
Guido> Dan Kegel wrote:
I've noticed lately that I need to specify --build when configuring
software for cross-compilation. This is a big burden, because I
write portable build scripts that invoke configure, make, etc. It
seems somewhat absurd, but the best way I can figure to find out
what to pass to --build is to run a second layer of autoconf on my
build script. Please, someone tell me I don't really need to
specify --build...
Guido> I never did, --host was all what was needed...
Maybe he is referring to 2.13 (who knows: I see no version number)
which was quite different wrt this.