Rockbox Development > Starting Development and Compiling
arm-elf-eabi-gcc not in PATH
torne:
Once you get it to actually build successfully, note that you don't need to change the path. The arm-whatever directory does not need to be in your path (and shouldn't be). The actual compiler binaries get installed to /usr/local/bin which is already in your path as you said, and that's all that needs to be there.
oldschool83:
Okay, maybe then I am not downloading the right/full gcc component?
Installing the compiler takes about an hour and ends with the error message.. Should I have a folder arm-elf-eabi-gcc somewhere after installing the compiler?
saratoga:
--- Quote from: oldschool83 on June 15, 2010, 04:34:07 PM ---Okay, maybe then I am not downloading the right/full gcc component?
Installing the compiler takes about an hour and ends with the error message.. Should I have a folder arm-elf-eabi-gcc somewhere after installing the compiler?
--- End quote ---
Yeah, but only if you actually get it to install.
FWIW compiling under a VM is about a million times faster then cgywin, so unless you really can't spare a couple GB of disk space or don't have admin access on your box, you might want to use that instead.
torne:
If it installs successfully you will end up with numerous files named arm-elf-eabi-gcc, arm-elf-eabi-ld, and so on in /usr/local/bin, and also a directory /usr/local/arm-elf-eabi.
oldschool83:
Ok, I am not getting the arm-elf-eabi-gcc file in usr\local\bin. What am I doing wrong? Maybe I am missing some cygwin component from the initial setup of the program?
By the way, I ran rockboxdev.sh today on another PC and it has been processing for almost 5 hours now.. the arm-elf-eabi-ld file and the /usr/local/arm-elf-eabi folder were created all within the first hour. But I still don't have an arm-elf-eabi-gcc file...
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version