arm-elf-gcc path...

[Jon_]

hello i would like to know how would i go about editing the path to get rid of the arm error at the beginning of compiling.

Would i have to open the profile file from the etc folder in notepad and edit an area inside?

[bluebrother]

unless you reveal a bit more of information -- especially what system are you using, cygwin, vmware or something else? answering that question isn't easy.

If you are on cygwin you need to edit /etc/profile with an editor different to notepad. Notepad can't handle the line endings correctly.

[GodEater]

I still don't recommend changing the path in the /etc/profile file.

This is a core file that's part of the cygwin distribution. Any changes you make to this file will be lost the next time you upgrade cygwin.

It's far preferably to create a .profile file in your home directory, and add the PATH statement in that.

[dandin1]

http://www.rockbox.org/twiki/bin/view/Main/CygwinDevelopment#Step_4_Add_the_cross_compiler_di

Or perhaps you havn't installed the ARM C compiler?  Then you just need to scroll up in that very same link.

[TMBordelon]

I initially had the same after a fresh Cygwin install.  You need to edit your (home directory specified during install)/.bash_profile file.

Add the following line anywhere within:

PATH=/opt/arm/bin:${PATH}

Todd

[Mikerman]

So, in reinstalling a clean build of Cygwin, I got the path error,  as the instructions warned.  Problems ever since.  Help?

I tried modifying the PATH line in the /etc/profile file, as the "Setting up a cygwin Rockbox development environment" instructions recommend.   However, I only have Windows WordPad and NotePad as editors--which then led to multiple Cygwin errors later.  (I assume the errors were due to my having used WordPad.)

I tried the alternate method, of typing in "export PATH=/usr/local/arm-elf/bin:$PATH" (without the quotes) after navigating to the build directory.  Again a no-go.

Then I found this thread, and tried adding the path line "PATH=/opt/arm/bin:${PATH}" (without quotes) to my (home directory specified during install)/.bash_profile file; again, I got multiple Cygwin errors.  However, I had used WordPad again.

I assume/hope the errors I am receiving are WordPad caused.  Can anyone lead me to a simple, compiled and acceptable editor that I simply could download and use (or offer another suggestion--perhaps a way to use WordPad for the editing (please note that I am not saving the files under WordPad as text files, but simply am using the save icon in the WordPad toolbar))?  

Thanks, as always--

[saratoga]

I use textpad.  Anything that allows you to select unix line endings would be fine.

I tried the alternate method, of typing in "export PATH=/usr/local/arm-elf/bin:$PATH" (without the quotes) after navigating to the build directory.  Again a no-go.

Is your copy of arm-elf-gcc in "/usr/local/arm-elf/bin"?  That should be all you need to do.

[Mikerman]

Thanks and funny but, I don't have a "/usr/local/arm-elf/bin"--there's no arm-elf folder there.

I located Notepad++ to use as an editor on the .bash_profile, but am afraid from a first try that my original use of WordPad bulloxed my .bash_profile file with crud.  Will have to get some sleep and think on in the morning how best to generate a new and clean one--perhaps just starting all over.

[saratoga]

Thanks and funny but, I don't have a "/usr/local/arm-elf/bin"--there's no arm-elf folder there.

You're probably supposed to change the path to whatever folder you put your arm-elf-gcc into.

I located Notepad++ to use as an editor on the .bash_profile, but am afraid from a first try that my original use of WordPad bulloxed my .bash_profile file with crud.  Will have to get some sleep and think on in the morning how best to generate a new and clean one--perhaps just starting all over.

Can't you just open it in Windows line return mode (which should look fine since you saved it in that mode) and then save it back out into unix mode?  I've done that before and never had a problem.  Haven't used that editor, but the "open" dialog window probably lets you pick the line ending mode.

[Mikerman]

Notepad++ has worked out just great; recommended to others including based on ease of use (just put the name into a search engine to find).

And many thanks to those above noting the need to personalize the paths--as I wasn't sure what was happening, I was being literal to all the instructions/suggestions--a night's sleep let me see my need to vary things and personalize.