Note that I have used Bingo's scripts to build avr-ggc before.
Through no fault of Bingo or his scripts, the first time was a true horror.
Some of it was played out on this forum.
The horror turned out to be a file system bug.
Eventually the horror went away when I updated my distro.
Subsequent efforts were successful, but still rather difficult.
I truly hate the poke it and see what it does method
of discovering what something is supposed to do.
Also, building compilers is not noted for being easy.
Clearly erroneous instructions increases the fear,
even if the corrections are obvious.
I am enclosing the scripts i use (credits of A. Erasmus) , if they could be of any useThe steps are these:
Read Readme.txt
Then install the packages listed in pre-reqs.txt.
Note !!
Don't try to call the scripts from another directory location , always execute from same directory where the scripts are located.
The current scripts uses recursive deletes , that could erase the harddisk if the above isn't honored.
Do not do this as root.
Do not do this in a directory that is not expendable.
Only do this in a directory all whose ancestors are
either expendable or invulnrable.
Then....1: Make sure you are root (blushing) , or use sudo
2: Make a working directory , where you extract the files from the archive.
They extract into a directory each.
Are we supposed to merge them into one?
3: If desired edit the buildavr-no-insight.sh file , to change the prefix .. default is : prefix=/usr/local/avr
4: Make sure that the prefix dir is empty or nonexisting
5: Run : chmod +x *.sh
6: Run : ./getfiles.sh
7: Run : ./get-patches.sh
8: Run : ./buildinsight.sh
9: Run: ./buildavr-no-insight.shYou just answer yes to the existing directory question in step 9.
When building is done , you might want to free around 500MB of diskspace by removing the sources and binaries used to make avr-gcc.
To do so Run: ./buildavr-cleanup.shNote this little script expects the "build prefix" to be /usr/local/avr/ .
My expectations are that I should
get the stuff in both pre-reqs.txt's,
read both ?eadme.txt's,
keep the directories separate,
make all the *.sh files executable, regardless of location,
run all the get-files.sh's and all the get-patches.sh's in their own directories,
run buildinsight.sh and buildavr-no-insight.sh from their own directories.