Rockbox Development > Starting Development and Compiling

arm-elf-eabi-gcc not in PATH

<< < (2/11) > >>

funman:
Download it from firefox or something and put it in /tmp/rbdev-dl (or whatever the download folder is named), then re-run the script

sunami88:

--- Quote from: funman on June 13, 2010, 05:29:27 PM ---Download it from firefox or something and put it in /tmp/rbdev-dl (or whatever the download folder is named), then re-run the script

--- End quote ---

Would be a good idea, but the script always baulks at me if tmp/whatever isn't empty. Plus it was always erroring out on different files...

Anyways, I did get the eabi compiler... err, compiled. This took many hours in cygwin... But in the end, I needed;


--- Quote ---Devel - libtool
Devel - libiconv
Web - wget

--- End quote ---

The wiki page won't let me edit it (Access check on Main.CygwinDevelopment failed. Action "CHANGE": access not allowed on web.), so someone's gonna have to do that. Adding a line about running ~/rockbox/tools/rockboxdev.sh and hitting e to install the compiler if you own a Sansa or other affected model might be a good idea too. Could stop someone else from posting. If it were me, I might put an asterisk beside each of the above 3 items just to denote that they might only be required for targets that utilize the eabi compiler.

Oh and at first I was trying to compile with "make -j" to take advantage of my dual core processor, but this seems to cause many errors, to the point of almost crashing the whole OS (seemed to be when it got to the codecs). Might want to add a line that with the eabi compiler, using make -j is not recommended in cygwin.

Update: nls is correct. It builds just fine on my dual core with "make -j2".

But ya, I have successfully built r26840 for the Clip+, and I will try it out on my FuzeV2 just to be sure a little later. Works fine as of right now though.



Some time later:
Yep, builds for the FuzeV2 just fine as well (I'm listening to some tunes on it right now). r26841 this time.

nls:
"make -j" can create *lots* of parallell jobs, it's genreally beter to use "make -jX" where X is number of jobs you want, usually around the number of cores you have.

oldschool83:
I also cannot get it to run, I get the same path error as you about finding eabi-gcc. I even made a lamer's guide on what I am doing:

1.   Get http://www.cygwin.com/
2.   Run again the installer and select packages:
·   curl
·   wget
·   patch
·   svn
·   make
·   Devel → gcc, gdb
·   Devel → libtool, libiconv
4.   run cygwin, go to \cygwin\home\UserName
5.   type “svn co svn://svn.rockbox.org/rockbox/trunk rockbox“
6.   put the patch inside the new rockbox folder (i.e. the root)
7.   type “patch --binary -p0 < patchfilename“, where patchfilename is the name of patch
8.   mkdir build
9.   cd build
10.   run ../tools/rockboxdev.sh script from inside the build folder
11.   select “e” for “arm-elf-eabi-gcc”. Download and install begins.
12.   export PATH= /usr/local/arm-elf-eabi/bin :$PATH
13.   while in build run ../tools/configure
14.   select the appropriate number for the corresponding device and Normal (N) build

And here I get the error. Both paths /usr/local/arm-elf-eabi/bin and /usr/local/arm-elf-eabi are seen when I type $PATH

saratoga:
If you type 'which arm-elf-eabi-gcc' does it give you the path to the compiler?

Navigation

[0] Message Index

[#] Next page

[*] Previous page