rockboxdev.sh woes

[boomselecta]

hi all,

trying to get rockboxdev.sh working on a new Linux build (Debian 10)


using the patch to allow for newer versions of gcc, rockboxdev successfully completed..

But when I run tools/configure, I get the warning "WARNING:. Your cross-compiler arm-elf-eabi-gcc 4.4.4 is not of the recommended version 4.9.4!   This may cause your build to fail since it may be a version that isn't functional or known to not be the best choice.  If you suffer from build problems, you know that this is a likely source for them.."

And sure enough, when I run "make zip" it stops along the way saying "/bin/sh: 1: arm-elf-eabi-gcc-ar: not found".

Appreciate any help that could be thrown my way.   My next idea would be to install an old Linux build so it's more of the era of the last update of rockboxdev.sh but that's not super ideal

[saratoga]

Which patch did you use? 

[amachronic]

On the current master branch rockboxdev.sh builds GCC 4.9.4. You shouldn't need to apply extra patches to 'update' the toolchain.

[boomselecta]

I used this patch: https://gerrit.rockbox.org/r/c/rockbox/+/1297

The reason I used the patch was because rockboxdev.sh was failing, I unfortunately no longer have the error , I think it was Error 2 (and some mention of arm-elf-eabi-gcc or gcc).

I'm not sure where to go from here, I suppose from the above replies I shouldn't have applied that patch?  How does one uninstall all the stuff rockboxdev.sh did to start over?

It still leaves me with the problem that rockboxdev failed without the patch, so unsure what to do.  I used the version of rockboxdev.sh that came with a new git pull.


Thanks again, to be clear I'm not particularly attached to Debian or anything, I am willing to do any OS or virtual box to get this to work, I have an old laptop which I am dedicating to this one purpose.

[saratoga]

If you look at that link it explains that the patch was abandoned because the problem was already fixed back in 2016.

Revert that patch (or just revert your whole got checkout) and rerun rockboxdev.sh. See what fails and go from there. Often it is something simple like a missing library.

[boomselecta]

Thanks, I'll try that.

[ed1]

hi all,

trying to get rockboxdev.sh working on a new Linux build (Debian 10)


using the patch to allow for newer versions of gcc, rockboxdev successfully completed..

But when I run tools/configure, I get the warning "WARNING:. Your cross-compiler arm-elf-eabi-gcc 4.4.4 is not of the recommended version 4.9.4!   This may cause your build to fail since it may be a version that isn't functional or known to not be the best choice.  If you suffer from build problems, you know that this is a likely source for them.." with telelatino pc.


And sure enough, when I run "make zip" it stops along the way saying "/bin/sh: 1: arm-elf-eabi-gcc-ar: not found".

Appreciate any help that could be thrown my way.   My next idea would be to install an old Linux build so it's more of the era of the last update of rockboxdev.sh but that's not super ideal

Hi

You must to execute script with sudo command is very import for to elevate permissions.

 Regards

[bluebrother]

You must to execute script with sudo command is very import for to elevate permissions.

That's not necessary. I'd even recommend against it, unless you want to install the toolchain system-wide.

rockboxdev.sh by default installs the toolchain to /usr/local, which is (usually) not writable by a user. Using sudo is the way to make that work, though I always pass --prefix= to point to a path where I can install. Furthermore, when building Rockbox the toolchain has to be in the PATH -- but that only requires you to modify PATH, and it's only necessary when running configure (thus, I usually run PATH=path/to/my/compiler/bin:$PATH ../tools/configure), then I can forget about it)

But when I run tools/configure, I get the warning "WARNING:. Your cross-compiler arm-elf-eabi-gcc 4.4.4 is not of the recommended version 4.9.4!   This may cause your build to fail since it may be a version that isn't functional or known to not be the best choice.  If you suffer from build problems, you know that this is a likely source for them.."

Sounds to me like you used an outdated version of rockboxdev.sh, which installed an outdated version of the toolchain. You might also have another toolchain installed from your distro that is picked up first.

I usually avoid this by (1) installing the toolchain in a custom path, and (2) putting it at the front of PATH when running configure.