cross compiler install via rockboxdev.sh on mac

[lenny]

I'm trying to build m68k cross compiler with rockboxdev.sh on a mac.

The first time I tried this it went through the whole process but quit when it couldn't make a directory to install the files in. So started over and executed it with a sudo. It finished successfully, but I didn't end up with a m68k-elf-gcc file! When I try to make it complains it can't find it. Here's what I ended up with I think:

m68k-elf-addr2line
m68k-elf-ar
m68k-elf-as
m68k-elf-c++filt
m68k-elf-gccbug
m68k-elf-gcov
m68k-elf-ld
m68k-elf-nm
m68k-elf-objcopy
m68k-elf-objdump
m68k-elf-ranlib
m68k-elf-readelf
m68k-elf-size
m68k-elf-strings
m68k-elf-strip

any ideas?

[Bagder]

those are all tools from the binutils installation

[lenny]

then where should the m68k-elf-gcc file have come from?

[rasher]

then where should the m68k-elf-gcc file have come from?

The GCC installation, if all went well. Which it apparently didn't. Something is probably not jibing correctly with the Apple-branded unix environment. Try running rockboxdev.sh like this:

Code: [Select]

rockboxdev.sh |tee rockboxdev.log 2>&1

And attach rockboxdev.log to this thread.

[lenny]

Thanks for you help rasher

I did as you said and have posted the log file here:

http://guitardating.com/lenny/rockboxdev.log

It won't be there forever.

On a side note, why the strict attachment restrictions here on the forums? The file extensions don't make sense (why doc and no log?) and 128KB just seems way too small. The log file here is 776KB and would be a perfectly legitmate use of the space (IMHO). No big deal though.

[Llorean]

We only have 20mb of total space for attachment on the forums. Period. So, a 3/4mb attachment is actually a fairly large portion of our total space.

As well, you could rename the .log to .txt and it would've worked. I can't possibly put in EVERY extension for a text file. Extensions don't really mean anything regarding the format anyway. Doc is allowed  because presumable it's a Microsoft Word document. If anyone asks me to, I'll add in the extension for Open Office's default equivalent as well. But for anything that can be read as a text file, simply rename it to .txt, assuming it's small enough.

[lenny]

Thanks Llorean. I had no idea there were only 20mb for attachments on the fourms. I know about renaming to txt, I tried that but then realized that my file is too big. And none of this, size or extensions, is really a big deal at all. I'm just glad I had a place to host the log file.

now back on topic... ?

[Bagder]

I can't say that I understand what happens but I can't see any gcc being installed, just a few other gcc-related tools... ?

[rasher]

I can't say that I understand what happens but I can't see any gcc being installed, just a few other gcc-related tools... ?

It's a bit hard to follow the output. Would be easier to tell what went wrong, if rockboxdev.sh told us what it was doing.

I also just realised I made a mistake. You'll want to run

Code: [Select]

./rockboxdev.sh 2>&1 |tee rockboxdev.log

Instead (we were missing all the errors!). It would also be nice if you could add an echo of some sort before line 185,186,187 and 194,195,196.

[lenny]

Thank you! I'd be happy to run it again, but by this:

add an echo of some sort before line 185,186,187 and 194,195,196.

do you mean in the script? If so, how would I do that (I'm not a shell scripting guru, yet)

Also, do I need to be concerned about deleting existing files before running the script again?

[Bagder]

I've updated the script with additional echo lines telling what it does to ease this kind of debugging. Committed just now.

do I need to be concerned about deleting existing files before running the script again?

The script will not run a second time until you remove the build directory so you better just remove that first and then re-run it. It'll use the same tool file names this time so it'll just overwrite the ones you made in your previous attempt (in the install path I mean).

[lenny]

allright, here's the new log

http://guitardating.com/lenny/rockboxdev2.log

looks like there's some ugly stuff at the very end, but I don't really know what it's saying.

[Bagder]

Thanks, my new output does indeed help.

I'm quite sure you need this patch applied to get this to work:
http://www.rockbox.org/twiki/bin/viewfile/Main/CrossCompiler?rev=1.1;filename=gcc-3.4.4.patch

This is not applied by the script. Can you do a manual build with this patch or should I try to blindly fix the script and let you test it?

[Bagder]

Ok, I wrote up a patch for rockboxdev.sh:

[cut out old URL]

If you could try applying this first, then run it just like before and we'll see if it helps or not! ;-)

[edited]
Of course I messed up, I should go to sleep instead. Here's a version that should work better:

http://daniel.haxx.se/rockbox/rockboxdev-2.patch

[barrywardell]

That patch almost works but not quite. Here's one that should work:
http://www.rockbox.org/twiki/pub/Main/CrossCompiler/rockboxdev-3.patch