Stupid Newbie Question?

Bob Wirka bobwirka at rtcworks.com
Tue May 2 19:16:47 UTC 2006


Thank you for your reply.

Below is the output of 'make'. There appear to be some spurious 
characters that don't cut&paste well.

[rcw at P733 buildroot]$ make
cp toolchain/uClibc/uClibc.config 
/data/buildroot/toolchain_build_i686/uClibc/.config
/data/buildroot/toolchain_build_i686/bin/sed -i -e 
's,^CROSS_COMPILER_PREFIX=.*,CROSS_COMPILER_PREFIX="/data/buildroot/build_i686/staging_dir/bin/i686-linux-uclibc-",g' 
\
        -e 's,# TARGET_i386 is not set,TARGET_i386=y,g' \
        -e 's,^TARGET_ARCH="none",TARGET_ARCH=\"i386\",g' \
        -e 
's,^KERNEL_SOURCE=.*,KERNEL_SOURCE=\"/data/buildroot/toolchain_build_i686/linux\",g' 
\
        -e 's,^RUNTIME_PREFIX=.*,RUNTIME_PREFIX=\"/\",g' \
        -e 's,^DEVEL_PREFIX=.*,DEVEL_PREFIX=\"/usr/\",g' \
        -e 
's,^SHARED_LIB_LOADER_PREFIX=.*,SHARED_LIB_LOADER_PREFIX=\"/lib\",g' \
        /data/buildroot/toolchain_build_i686/uClibc/.config
/data/buildroot/toolchain_build_i686/bin/sed -i -e 
's,^.*UCLIBC_HAS_LFS.*,UCLIBC_HAS_LFS=y,g' 
/data/buildroot/toolchain_build_i686/uClibc/.config
/data/buildroot/toolchain_build_i686/bin/sed -i -e 
's,.*UCLIBC_HAS_WCHAR.*,UCLIBC_HAS_WCHAR=y,g' 
/data/buildroot/toolchain_build_i686/uClibc/.config
/data/buildroot/toolchain_build_i686/bin/sed -i -e 's,# 
UCLIBC_HAS_THREADS is not set,UCLIBC_HAS_THREADS=y,g' 
/data/buildroot/toolchain_build_i686/uClibc/.config
/data/buildroot/toolchain_build_i686/bin/sed -i -e 's,# 
PTHREADS_DEBUG_SUPPORT is not set,PTHREADS_DEBUG_SUPPORT=y,g' 
/data/buildroot/toolchain_build_i686/uClibc/.config
/data/buildroot/toolchain_build_i686/bin/sed -i -e 's,# LINUXTHREADS_OLD 
is not set,LINUXTHREADS_OLD=y,g' 
/data/buildroot/toolchain_build_i686/uClibc/.config
mkdir -p /data/buildroot/toolchain_build_i686/uClibc_dev/usr/include
mkdir -p /data/buildroot/toolchain_build_i686/uClibc_dev/usr/lib
mkdir -p /data/buildroot/toolchain_build_i686/uClibc_dev/lib
make -C /data/buildroot/toolchain_build_i686/uClibc \
PREFIX=/data/buildroot/toolchain_build_i686/uClibc_dev/ \
DEVEL_PREFIX=/usr/ \
RUNTIME_PREFIX=/data/buildroot/toolchain_build_i686/uClibc_dev/ \
HOSTCC="gcc" \
        pregen install_dev && \
touch /data/buildroot/toolchain_build_i686/uClibc/.configured
/bin/sh: line 1: 
/data/buildroot/build_i686/staging_dir/bin/i686-linux-uclibc-gcc: No 
such file or directory
make[1]: 
/data/buildroot/build_i686/staging_dir/bin/i686-linux-uclibc-gcc: 
Command not found
make[1]: Entering directory `/data/buildroot/toolchain_build_i686/uClibc'
make[1]: 
/data/buildroot/build_i686/staging_dir/bin/i686-linux-uclibc-gcc: 
Command not found
        ??make -C extra/config conf
/bin/sh: line 1: 
/data/buildroot/build_i686/staging_dir/bin/i686-linux-uclibc-gcc: No 
such file or directory
make[2]: 
/data/buildroot/build_i686/staging_dir/bin/i686-linux-uclibc-gcc: 
Command not found
HB0?make[2]: 
/data/buildroot/build_i686/staging_dir/bin/i686-linux-uclibc-gcc: 
Command not found
        ((make[2]: *** No rule to make target `|', needed by 
`../../extra/config/conf.o'.  Stop.
make[1]: *** [extra/config/conf] Error 2
make[1]: Leaving directory `/data/buildroot/toolchain_build_i686/uClibc'
make: *** [/data/buildroot/toolchain_build_i686/uClibc/.configured] Error 2
[rcw at P733 buildroot]$


Alessio.MASSARO at oxinst.co.uk wrote:

>You understood correctly
>But you'll have to provide more info. At what point does it fail? What does
>it say before the 'error 2'?
>
>
>  
>
>>-----Original Message-----
>>From: uclibc-bounces at uclibc.org 
>>[mailto:uclibc-bounces at uclibc.org] On Behalf Of Bob Wirka
>>Sent: 02 May 2006 17:43
>>To: uclibc at uclibc.org
>>Subject: Stupid Newbie Question?
>>
>>Hello,
>>
>>I'm trying out Buildroot. Have downloaded the snapshot, and 
>>tried to do a 'make' after running through 'make menuconfig'. 
>>I didn't change anything; just left everything as default 
>>because I want to see what it does for a stock setup.
>>
>>The build fails with 'error 2' when it can't find 
>>"i386-linux-uclibc-gcc". Do I have to build the compiler 
>>toolchain first? It was my understanding that Buildroot was 
>>self-contained, and would build the toolchain, kernel, 
>>uClibc, etd.  Is this wrong?
>>
>>Thank you,
>>
>>Bob Wirka
>>Realtime Control Works
>>_______________________________________________
>>uClibc mailing list
>>uClibc at uclibc.org
>>http://busybox.net/cgi-bin/mailman/listinfo/uclibc
>>
>>+++ Virus-scanned by Messagelabs for Oxford Instruments +++
>>
>>    
>>
>
> ###  OXFORD INSTRUMENTS   http://www.oxford-instruments.com/  ### 
>
>Unless stated above to be non-confidential, this E-mail and any 
>attachments are private and confidential and are for the addressee 
>only and may not be used, copied or disclosed save to the addressee.
>If you have received this E-mail in error please notify us upon receipt 
>and delete it from your records. Internet communications are not secure 
>and Oxford Instruments is not responsible for their abuse by third 
>parties nor for any alteration or corruption in transmission. 
>
>_______________________________________________
>uClibc mailing list
>uClibc at uclibc.org
>http://busybox.net/cgi-bin/mailman/listinfo/uclibc
>
>
>
>  
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.busybox.net/pipermail/uclibc/attachments/20060502/9df99b34/attachment-0001.htm 


More information about the uClibc mailing list