arm-elf-eabi-gcc not in PATH

[[Saint]]

For cygwin, the only thing that should need to be in the PATH is "usr/local/bin/" and this is a default PATH of cygwin...so you shouldn't have to edit anything.
This assumes of course that your cygwin install is running/complete and that you ran rockboxdev.sh (quite recently) without changing where the cross-compilers install to.


[St.]

[Jack Sparrow]

Thanks for everyone's help.  It finished after about 5 hours and I am now compiling

[Kalin]

Hi there!

I'm new here in both the dev of rockbox and forums, and I'm feeling a bit lost on some things, but I'm trying to do my best

I'm developing under Mac OS X, and I have the same problem as some of you with the arm-elf-eabi-gcc compiler, that seems to not been install, whatever I try. I've already tried to run rockbox.sh with the "e" parameter in order to install de arm-elf-eabi compiler, but it seems not to work. I'm getting the "is not in your path" error, and navigating to "/usr/local" there is no "bin" directory in there (¿?). I've tried to create it manually and execute the rockboxdev.sh again, but still it seems to not create any arm-elf-whatever file or directory...

Any clue on this?? Those who had the same problem, I don't understand how you finally manage to get the compiler to install. How do you achive it??

Thank you very much!

[Kalin]

Anyone? :'(

I don't know what to do. I've followed all the steps of the quick guide for compilling rockbox and I don't know why the arm-elf-eabi compiler is not installing on my system. Maybe is there some kind of incompatibility with Mac OS X? If I type "which arm-elf-eabi-gcc" I'm getting anything, and if I browse to usr/local/bin there aren't any arm-elf... files anywhere. When I run the "rockboxdev.sh" script, it finishes with some errors, but they aren't specified:

Code: [Select]

make[2]: *** [libgcc.a] Abort trap
make[2]: *** Deleting file `libgcc.a'
make[1]: *** [stmp-multilib] Error 2
make: *** [all-gcc] Error 2


And this is the error I get trying to compile:

Code: [Select]

../tools/configure: line 2837: arm-elf-eabi-gcc: command not found
[WARNING] The compiler you must use (arm-elf-eabi-gcc) is not in your path!
[WARNING] this may cause your build to fail since we cannot do the
[WARNING] checks we want now.
Using arm-elf-eabi-ld ..2842---
Created Makefile

I've also tryed to manually modify the PATH string by adding this:

Code: [Select]

/usr/local/arm-elf/bin:/usr/local/m68mk-elf/bin:/usr/local/sh-elf/bin:/usr/local/arm-elf-eabi:/usr/local/arm-elf-eabi/binBut doesn't change anything

[torne]

Anyone? :'(

I don't know what to do. I've followed all the steps of the quick guide for compilling rockbox and I don't know why the arm-elf-eabi compiler is not installing on my system. Maybe is there some kind of incompatibility with Mac OS X? If I type "which arm-elf-eabi-gcc" I'm getting anything, and if I browse to usr/local/bin there aren't any arm-elf... files anywhere. When I run the "rockboxdev.sh" script, it finishes with some errors, but they aren't specified:

Code: [Select]

make[2]: *** [libgcc.a] Abort trap
make[2]: *** Deleting file `libgcc.a'
make[1]: *** [stmp-multilib] Error 2
make: *** [all-gcc] Error 2


You need to paste more than that; that doesn't include the command it was running at the time, or anything else useful

[Kalin]

Forget de previous lines of error. There were from installing the arm-elf compiller. These are from the arm-eabi-elf installation (via rockboxdev.sh, of course):

Code: [Select]

libtool: compile:  gcc -no-cpp-precomp -DHAVE_CONFIG_H -I. -I../../binutils-2.20.1/bfd -I. -I../../binutils-
.20.1/bfd -I../../binutils-2.20.1/bfd/../include -I./../intl -DBINDIR=\"/usr/local/bin\" -W -Wall -Wstrict-prototypes
-Wmissing-prototypes -Werror -U_FORTIFY_SOURCE -MT elf32-arm.lo -MD -MP -MF .deps/elf32-arm.Tpo -c ../../binutils-
.20.1/bfd/elf32-arm.c -o elf32-arm.o
cc1: warnings being treated as errors
../../binutils-2.20.1/bfd/elf32-arm.c: In function ‘elf32_arm_print_private_bfd_data’:
../../binutils-2.20.1/bfd/elf32-arm.c:10502: warning: format not a string literal and no format arguments
../../binutils-2.20.1/bfd/elf32-arm.c:10510: warning: format not a string literal and no format arguments
../../binutils-2.20.1/bfd/elf32-arm.c:10512: warning: format not a string literal and no format arguments
../../binutils-2.20.1/bfd/elf32-arm.c:10514: warning: format not a string literal and no format arguments
../../binutils-2.20.1/bfd/elf32-arm.c:10517: warning: format not a string literal and no format arguments
../../binutils-2.20.1/bfd/elf32-arm.c:10520: warning: format not a string literal and no format arguments
../../binutils-2.20.1/bfd/elf32-arm.c:10523: warning: format not a string literal and no format arguments
../../binutils-2.20.1/bfd/elf32-arm.c:10526: warning: format not a string literal and no format arguments
../../binutils-2.20.1/bfd/elf32-arm.c:10529: warning: format not a string literal and no format arguments
../../binutils-2.20.1/bfd/elf32-arm.c:10538: warning: format not a string literal and no format arguments
../../binutils-2.20.1/bfd/elf32-arm.c:10541: warning: format not a string literal and no format arguments
../../binutils-2.20.1/bfd/elf32-arm.c:10543: warning: format not a string literal and no format arguments
../../binutils-2.20.1/bfd/elf32-arm.c:10549: warning: format not a string literal and no format arguments
../../binutils-2.20.1/bfd/elf32-arm.c:10552: warning: format not a string literal and no format arguments
../../binutils-2.20.1/bfd/elf32-arm.c:10554: warning: format not a string literal and no format arguments
../../binutils-2.20.1/bfd/elf32-arm.c:10557: warning: format not a string literal and no format arguments
../../binutils-2.20.1/bfd/elf32-arm.c:10560: warning: format not a string literal and no format arguments
../../binutils-2.20.1/bfd/elf32-arm.c:10567: warning: format not a string literal and no format arguments
../../binutils-2.20.1/bfd/elf32-arm.c:10571: warning: format not a string literal and no format arguments
../../binutils-2.20.1/bfd/elf32-arm.c:10575: warning: format not a string literal and no format arguments
../../binutils-2.20.1/bfd/elf32-arm.c:10578: warning: format not a string literal and no format arguments
../../binutils-2.20.1/bfd/elf32-arm.c:10581: warning: format not a string literal and no format arguments
../../binutils-2.20.1/bfd/elf32-arm.c:10587: warning: format not a string literal and no format arguments
../../binutils-2.20.1/bfd/elf32-arm.c:10594: warning: format not a string literal and no format arguments
../../binutils-2.20.1/bfd/elf32-arm.c:10597: warning: format not a string literal and no format arguments
../../binutils-2.20.1/bfd/elf32-arm.c:10602: warning: format not a string literal and no format arguments
make[4]: *** [elf32-arm.lo] Error 1
make[3]: *** [all-recursive] Error 1
make[2]: *** [all] Error 2
make[1]: *** [all-bfd] Error 2
make: *** [all] Error 2
Hope this piece of code will be enough. If doesn't, just ask for more lines.

Thanks for trying to help, torne

[funman]

I could build all the compilers on 10.5.8 but apparently it's not possible on 10.6; at least without a patch that nobody wrote.

You're a bit on your own because most developers here use linux, and OSX tools frequently have incompatibilities with the original GNU tools

[torne]

Add --disable-werror to the arguments for configure, and it might work.

[Kalin]

Add --disable-werror to the arguments for configure, and it might work.

To which instruction may I add this argument? I've tried with rockboxdev.sh, and when introducing the parameters it asks, but nothing changed...

Well, it seems I'd have to try in an Ubuntu OS that I have in another PC...

Thank you both for the tips!

[torne]

Edit rockboxdev.sh and add it to the end of the line that says:

Code: [Select]

CFLAGS=-U_FORTIFY_SOURCE ../$toolname-$version/configure --target=$target --prefix=$prefix --enable-languages=c --disable-libssp --disable-docs $configure_params
binutils treats all warnings as errors by default, but it's being built by your host compiler and your host compiler is not guaranteed to be entirely happy with it. --disable-werror tells it to let warnings slide

[Kalin]

Edit rockboxdev.sh and add it to the end of the line that says:

Code: [Select]

CFLAGS=-U_FORTIFY_SOURCE ../$toolname-$version/configure --target=$target --prefix=$prefix --enable-languages=c --disable-libssp --disable-docs $configure_params
binutils treats all warnings as errors by default, but it's being built by your host compiler and your host compiler is not guaranteed to be entirely happy with it. --disable-werror tells it to let warnings slide

Thank you! I'll try in the future. No problems compiling in Ubuntu 10.04!

By the meantime I'd develope in Ubuntu, since it seems to be full compatible and I don't have to be playing with any work-arround for compiling. Thank you very much for the help, and sorry for my english...

Cheers!

[chileboy]

I need to resurrect this thread...

I have followed the wiki carefully (I think).  After getting Cygwin installed, when I first ran rockboxdev.sh, I got some complaint about not finding libiconv, so I re-ran Setup and installed that (although not referenced in the wiki).  After that, rockboxdev.sh seemed to run ok except for the following warnings (I piped the output to a text file just to be sure I wasn't missing anything) - not sure if these are significant or not:

Code: [Select]

../../binutils-2.20.1/libiberty/choose-temp.c: In function `choose_temp_base':
../../binutils-2.20.1/libiberty/choose-temp.c:68: warning: call to `mktemp' decl
ared with attribute warning: the use of `mktemp' is dangerous; use `mkstemp' ins
tead
libtool: link: warning: undefined symbols not allowed in i686-pc-cygwin shared l
ibraries
libtool: link: warning: undefined symbols not allowed in i686-pc-cygwin shared l
ibraries
syslex.c:1272: warning: `yyunput' defined but not used
syslex.c:1315: warning: `input' defined but not used
arlex.c:1397: warning: `yyunput' defined but not used
arlex.c:1440: warning: `input' defined but not used
/Users/gingold/Repositories/fsf/binutils-2_20/ld/ldlex.c:3362: warning: `yyunput
' defined but not used
rm: cannot remove `/tmp/rbdev-build/build-binutils': Device or resource busy
Yet no matter what I have tried, I cannot get arm-elf-eabi-gcc to show up in my usr/local/bin, and of course running configure triggers the "not in PATH" error.

I ran Cygwin setup multiple times, checked my package selection each time to be sure, deleted the tmp directory between installs, etc.

I was getting a bit frustrated, so I thought maybe someone could give me a clue as to what I'm missing.

Thanks.

[saratoga]

I was getting a bit frustrated, so I thought maybe someone could give me a clue as to what I'm missing.

No idea, but IMO cygwin is way more trouble then its worth.  Using a VM is much easier. 

[torne]

This is a bug in rockboxdev.sh on Cygwin machines; your build is being stopped once binutils has compiled, before gcc compilation starts, because it failed to remove the temporary directory for the binutils build.

I worked this one out the other day but predictably I forgot about it; I'm going to fix it now. I'll report back when I've sorted the issue

Edit: It should be fine now; update to at least svn r28314 and try again.

[[Saint]]

Just a quick note,

If anyone reads this thread...just so they know, it is *not* necessary (as of the eabi changeover) to edit the $PATH variable to include the toolchain in CygWin any more.

By default, the toolchain is built and placed in a $PATH that is one of CygWins defaults...so, there should be no need to edit the path to include the toolchain in a default installation.

I hope this clears up some confusion.



[St.]