Feedback from using Crosstool-NG
Sat Jun 7 17:23:00 GMT 2014
At Free Electrons, we regularly use Crosstool-NG, especially in our
embedded Linux trainings. I gave yet another training last week, and I
have a bunch of feedback I'd like to share with the Crosstool-NG
developers (most of it was already reported by Yann privately, but I
thought that sharing it publicly and by writing was probably better).
* The current arm-unknown-linux-uclibcgnueabi sample does not build,
because cloop-ppl 0.15.9 is no longer available online.
* The strategy of Crosstool-NG to try gazillions of download locations
and file extensions is silly, and actually harmful. In certain
corporate environments, trying to download through ftp causes
timeouts. Or even when http is used, when the server is not
responding, it causes timeouts. I have seen cases where I had to
wait more than one minute for a download to start, just because
Crosstool-NG was trying dozens of possible locations before finding
the relevant one. In Buildroot, we use one single URL for each
tarball, and it works just fine.
* The arm-unknown-linux-uclibcgnueabi sample is horribly old: gcc 4.4
(while gcc 4.7 is close to end-of-like), uClibc 0.9.30 (we're at
0.9.33), binutils 2.19 (we're at 2.24), gdb 7.1 (we're at 7.7).
* It would be good to have a arm-unknown-linux-uclibcgnueabihf sample.
Surely, I could contribute patches to implement some of these things,
but I never managed to get around to use Mercurial, and since the
number of projects using it is so small, I don't really see the point
of learning :)
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
For unsubscribe information see http://sourceware.org/lists.html#faq
More information about the crossgcc