On 21 Apr 2000, Alexandre Oliva wrote:
> On Apr 21, 2000, Mo DeJong <[EMAIL PROTECTED]> wrote:
>
> > So if it should have been "internal" then why do I need to add the
> > AC_CANONICAL_BUILD macro to my configure.in file to get cross
> > compiling to work?
But the docs tell me I only need AC_CANONICAL_SYSTEM if I am
a tool in a cross compiler toolchain. The docs need to be
updated.
> You'd use AC_CANONICAL_SYSTEM.
>
> > In looking at the source, I also came across this AC_CHECK_TOOL_PREFIX
> > macro which seems to be doing exactly what I want, running the
> > host and build check and then comparing the host and the build.
>
> Indeed. Stupid me, this macro didn't occur to me :-(
>
> > Problem is, it not seem to work. It looks for the right compiler
> > but it does not actually use it.
Doh! Sorry about that, I goofed. Cross compiler detection
is now working if I used the AC_CHECK_TOOL(CXX, c++) macro.
mo(~/foo)% ./configure --host=i586-cygwin32
checking host system type... i586-pc-cygwin32
checking build system type... i686-pc-linux-gnu
checking for i586-cygwin32-c++... i586-cygwin32-c++
checking for c++... (cached) i586-cygwin32-c++
later
Mo
> Is CXX set in your environment?
>
> --
> Alexandre Oliva Enjoy Guaran�, see http://www.ic.unicamp.br/~oliva/
> Cygnus Solutions, a Red Hat company aoliva@{redhat, cygnus}.com
> Free Software Developer and Evangelist CS PhD student at IC-Unicamp
> oliva@{lsd.ic.unicamp.br, gnu.org} Write to mailing lists, not to me
>
>
