This is the mail archive of the crossgcc@sourceware.org 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] |
And please don't email us directly. ALWAYS email the mailing list. Otherwise the question might not get answered, and the answer won't be indexed by google to help the next person.
On 10/11/06, Z. M. <zed6641@hotmail.com> wrote: > But after modify the Makfile for target arm, > > ARCH :=arm > CROSS_COMPILE :=arm-linux- > > There was errors: /bin/sh: arm-linux-gcc:command not found !
You can test whether your CROSS_COMPILE is right by doing ls $CROSS_COMPILE-gcc If you don't see that file, you got it wrong.
Look at the file testlinux.sh in crosstool, which crosstool uses to compile the linux kernel as a test of the compiler. (It doesn't modify the kernel's Makefile. Instead, it modifies the ARCH and CROSS_COMPILE variables on the commandline, but it's the same as editing the Makefile.) It sets ARCH to arm, but it sets CROSS_COMPILE to $PREFIX/bin/$TARGET- where $PREFIX is where crosstool was installed, and $TARGET is the same value as in the .dat file you built crosstool with, e.g. arm-unknown-linux-gnu. So CROSS_COMPILE should be something like /usr/crosstool/gcc-4.1.0-glibc-2.2.2/arm-unknown-linux-gnu/bin/arm-unknown-linux-gnu-
Hope that helps. - Dan
-- Wine for Windows ISVs: http://kegel.com/wine/isv
-- For unsubscribe information see http://sourceware.org/lists.html#faq
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |