chroot'd toolchain & gnu libc issue? (was Re: Proper use of libtool under buildroot?)

Marcus Crafter crafterm at gmail.com
Mon Dec 12 10:52:52 UTC 2005


Hi Guys,

Ok, below seems to be the problem. If I add $(TARGET_CONFIGURE_OPTS)  
to the Makefile's for gcc-target and binutils-target then I get a  
working toolchain inside of buildroot/build_i386/root. Awesome.

Thanks heaps for your help. I'll submit a patch/bug. On to the next  
step!... :)

Cheers,

Marcus

On 12/12/2005, at 11:13 AM, Marcus Crafter wrote:
> Ok, the only thing I can see at this stage is that buildroot/ 
> packages are usually 'configure'd/built with $ 
> (TARGET_CONFIGURE_OPTS) provided. eg from make.mk:
>
> $(GNUMAKE_DIR)/.configured: $(GNUMAKE_DIR)/.unpacked
>         (cd $(GNUMAKE_DIR); rm -rf config.cache; \
>                 $(TARGET_CONFIGURE_OPTS) \
>                 CFLAGS="$(TARGET_CFLAGS)" \
>                 ./configure \
>                 --target=$(GNU_TARGET_NAME) \
>                 --host=$(GNU_TARGET_NAME) \
>                 --build=$(GNU_HOST_NAME) \
>                 --prefix=/usr \
> 		... and so on
>
> whereas the target gcc compiler doesn't have this:
>
> GCC_BUILD_DIR3:=$(BUILD_DIR)/gcc-$(GCC_VERSION)-target
>
> $(GCC_BUILD_DIR3)/.configured: $(GCC_BUILD_DIR2)/.installed
>         mkdir -p $(GCC_BUILD_DIR3)
>         (cd $(GCC_BUILD_DIR3); PATH=$(TARGET_PATH) \
>                 $(GCC_DIR)/configure \
>                 --prefix=/usr \
>                 --build=$(GNU_HOST_NAME) \
>                 --host=$(REAL_GNU_TARGET_NAME) \
>                 --target=$(REAL_GNU_TARGET_NAME) \
>                 --enable-languages=$(TARGET_LANGUAGES) \
> 		..... and so on
>
> Seems like $(TARGET_CONFIGURE_OPTS) which defines:
>
> TARGET_CONFIGURE_OPTS=PATH=$(TARGET_PATH) \
>                 AR=$(TARGET_CROSS)ar \
>                 AS=$(TARGET_CROSS)as \
>                 LD=$(TARGET_CROSS)ld \
>                 NM=$(TARGET_CROSS)nm \
>                 CC=$(TARGET_CROSS)gcc \
>                 GCC=$(TARGET_CROSS)gcc \
>                 CXX=$(TARGET_CROSS)g++ \
>                 RANLIB=$(TARGET_CROSS)ranlib \
>                 OBJCOPY=$(TARGET_CROSS)objcopy
>
> isn't provided when buiding the target's gcc compiler. I can't see  
> anything similar that would point it to some other CC other than  
> what's in the default path at this stage. hmm.
>
> Still digging... just thought i'd mention it in case you/anyone had  
> any other thoughts as to what might be wrong.
>
> Cheers,
>
> Marcus




More information about the uClibc mailing list