Rockbox Development > Starting Development and Compiling

arm-elf-eabi-gcc not in PATH

<< < (3/11) > >>

oldschool83:
Hm, no..

sunami88:
I always ran ./rockboxdev.sh from within tools. It should take a really long time (and only have to complete successfully once!). By "a really long time", I mean a good 7 hours or so on my 1.60Ghz CoreDuo laptop (my 2.66Ghz QuadCore monster desktop being indisposed at the moment). I set it going and walked away for the day...

Also, which arm-elf-eabi-gcc returns "/usr/local/bin/arm-elf-eabi-gcc" as it should... are you sure it finished downloading/compiling? Did you happen to copy what it last said before you tried to compile the latest rev?

gevaerts:
Did you take into account that the default installation paths recently changed?
Is /usr/local/bin in your PATH?

oldschool83:
After running rockboxdev.sh it processes for about an hour or more. Then I get this message:
http://img412.imageshack.us/img412/5681/52905234.jpg

I have no path to arm-elf-eabi, which goes in usr/local after running rockboxdev.

I have no directory called arm-elf-eabi-gcc, which is what I get in the error prompt.

When I type echo $PATH I see /usr/local/bin but no arm-elf-eabi/bin

How can I add it there? I am not exactly sure how to work with export and PATH commands.. Or maybe I am completely missing arm-elf-eabi-gcc. When I run rockboxdev I hit "e" for it and the Clip v2, but I get no such directory in usr/local

saratoga:
I wouldn't worry about setting the path to your compiler until you manage to get the compiler installed.  Try clearing out all the files downloaded by cygwin and starting the build over.  It also wouldn't hurt to scroll up through that log and make sure thats the first error message generated.

Navigation

[0] Message Index

[#] Next page

[*] Previous page