This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: crosstool-0.27: builduserland fails: arm-linux-gcc not found;I have arm-arm9-linux-gnu-gcc


Ken Wolcott wrote:
TARBALLS_DIR=~/downloads
RESULT_TOP=~/crosstool
KERNELCONFIG=$PWD/arm.config
TARGET=arm-arm9-linux-gnu
TARGET_CFLAGS="-O"
BINUTILS_DIR=binutils-2.14.90.0.7
BINUTILS_URL=http://www.kernel.org/pub/linux/devel/binutils
GCC_DIR=gcc-3.2.1
GLIBC_DIR=glibc-2.3.1
GLIBCTHREADS_FILENAME=glibc-linuxthreads-2.3.1
LINUX_DIR=linux-2.4.21

export TARBALLS_DIR RESULT_TOP SRC_DIR KERNELCONFIG TARGET TARGET_CFLAGS \ BINUTILS_DIR BINUTILS_URL GCC_DIR GLIBC_DIR LINUX_DIR GLIBCTHREADS_FILENAME

/bin/sh all.sh --notest --builduserland

(Just curious, why are you using --builduserland? Do you really need crosstool to build busybox etc. for you? I usually only do that if I'm going to be running the regression tests, and need a minimal environment.)

> ...
-----------------------
target: busybox.prepare
-----------------------

touch /tuba_local/pristine_crosstool/pristine_crosstool27/patched-crosstool-0.27/build/arm-arm9-linux-gnu/gcc-3.2.1-glibc-2.3.1-binutils-2.14.90.0.7-linux-2
.4.21/ptxdist-testing-20031113/build/busybox-1.00-pre3/busybox.links
PATH="/home/msa3530/crosstool/arm-arm9-linux-gnu/gcc-3.2.1-glibc-2.3.1-binutils-2.14.90.0.7-linux-2.4.21"/bin:$PATH make -C /tuba_local/pristine_crosstool/pristine_crosstool27/patched-crosstool-0.27/build/arm-arm9-linux-gnu/gcc-3.2.1-glibc-2.3.1-binutils-2.14.90.0.7-linux-2.4.21/ptxdist-testing-20031113/build/b
usybox-1.00-pre3 distclean CROSS="arm-linux"- HOSTCC=gcc EXTRA_CFLAGS='-O -mcpu=405'
/bin/sh: line 1: arm-linux-gcc: command not found

Ah, I never got around to adding arm to my ptxdist patch.


The problem lies in ptxdist*/rules/target.in.  Here's a patch I just
whipped up that shows you what the fix probably looks like:

--- ptxdist-testing-20031113/rules/target.in.old        2004-02-02 14:45:26.000000000 -0800
+++ ptxdist-testing-20031113/rules/target.in    2004-02-02 14:45:50.000000000 -0800
@@ -241,7 +241,7 @@

 config GNU_TARGET
        string
-       default "arm-linux"                     if ARM_ARCH_LE          && GLIBC
+       default "arm-unknown-linux-gnu"         if ARM_ARCH_LE          && GLIBC
        default "armb-unknown-linux-gnu"        if ARM_ARCH_BE          && GLIBC
        default "arm-elf"                       if ARCH_ARM_NOMMU       && GLIBC
        default "i386-linux"                    if OPT_I386             && GLIBC

(That's online as http://kegel.com/crosstool/ptx-arm.patch and could be dropped
straight into the patches/ptxdist-testing-20031113 directory.)

However, since you're using a nonstandard target (arm-arm9-linux-gnu)
you might need to adjust that a bit.  It's a shame that ptxdist treats
the gnu target tuple as an *output* rather than an input, but
that's the joy of using 'make menuconfig' to construct the target string, I guess.
- Dan

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]