This is the mail archive of the
mailing list for the GCC project.
Re: libada cross-compilation
- From: Richard Earnshaw <rearnsha at gcc dot gnu dot org>
- To: Nick Burrett <nick at sqrt dot co dot uk>
- Cc: gcc-patches <gcc-patches at gcc dot gnu dot org>
- Date: Fri, 25 Feb 2005 14:45:54 +0000
- Subject: Re: libada cross-compilation
- Organization: GNU
- References: <421EF417.email@example.com>
On Fri, 2005-02-25 at 09:47, Nick Burrett wrote:
> I found the following patch was required to allow for the successful
> building of the gnattools for a cross-compiler. Without this patch, we
> would be using a mix of the built cross-compiler and the host's gnattool
> Built on i686-pc-linux-gnu and cross-compiled to arm-unknown-elf.
> If this is OK, can somebody commit it as I don't have write-access.
> <date> Nick Burrett <firstname.lastname@example.org>
> * Makefile.in (gnattools-cross): Use native CC.
> --- /home/nick/riscos-aof/masters/gcc-4.0/libada/Makefile.in 2004-05-30 09:51:07.000000000 +0100
> +++ libada/Makefile.in 2005-02-25 09:42:01.142391312 +0000
> @@ -164,6 +164,7 @@
> gnattools-cross: gnatlib
> $(MAKE) -C $(GCC_DIR)/ada $(FLAGS_TO_PASS) $(ADA_FLAGS_TO_PASS) \
> ADA_INCLUDES="-I$(RTS_DIR)../adainclude -I$(RTS_DIR)" \
> + CC="gcc" \
> GNATMAKE="gnatmake" \
> GNATBIND="gnatbind" \
> GNATLINK="gnatlink" \
This can't be right. It's never correct to hard-bind CC to a specific
compiler name (with the exception of the compiler we've just built).
Perhaps you mean $(CC_FOR_BUILD)?