The compile process should be pretty straight forward, but I made a few stuffup’s along the way.<\/p>\n
- \n
- I had originally wanted to keep it neat and install to a new directory, then the PATH annoyance thing hit me.\u00a0 Setting the path under my user shell didn’t carry over when using sudo which is required to make install.\u00a0 Solved using sudo -s<\/em>, but then in the end i just redid it all and installed to \/usr\/local\/<\/em>.<\/li>\n
- Realised (should have known) that you need ‘GMP’ and ‘MPFR’ to compile GCC.\u00a0 Available as packages libgmp3-dev<\/em> and libmpfr-dev<\/em> in Ubuntu.<\/li>\n
- Did my usual of forgetting to set up the prefix install location when configuring…minor boo boo<\/li>\n<\/ul>\n
Setting it all up<\/h2>\n
Install any packages you need… build-essential<\/em> is probably essential… GMP and MPFR could be got by using<\/p>\n
sudo apt-get install libgmp3-dev libmpfr-dev<\/p><\/blockquote>\n
Set-up some directories…I opted to use create an ‘arm-elf’ directory in my home to hold both the source and build directories…<\/p>\n
cd ~
\nmkdir arm-elf arm-elf\/src
\ncd ~\/arm-elf\/src<\/p><\/blockquote>\nGet the latest sources…<\/h3>\n
Get the latest sources for binutils<\/a>, gcc<\/a>, newlib<\/a>, insight<\/a> (click the links if you need).\u00a0 The versions I used should be obvious from the filenames below.\u00a0 Just be wary that the insight front page is not kept up to date but you’ll find the latest if you follow any of the release links anyway.<\/p>\n
wget http:\/\/ftp.gnu.org\/gnu\/binutils\/binutils-2.19.tar.bz2
\nwget http:\/\/gcc.releasenotes.org\/releases\/gcc-4.3.2\/gcc-4.3.2.tar.bz2
\nwget ftp:\/\/sources.redhat.com\/pub\/newlib\/newlib-1.16.0.tar.gz
\nwget ftp:\/\/sourceware.org\/pub\/insight\/releases\/insight-6.8.tar.bz2<\/p><\/blockquote>\nUnpack the sources…<\/h3>\n
tar -xvjf binutils-2.19.tar.bz2
\ntar -xvjf gcc-4.3.2.tar.bz2
\ntar -xvzf newlib-1.16.0.tar.gz
\ntar -xvjf insight-6.8.tar.bz2<\/p><\/blockquote>\nTweak the gcc source config…<\/h3>\n
Make a minor config tweak to the gcc source.\u00a0 Edit gcc-4.3.2\/gcc\/config\/arm\/t-arm-elf and append mno-thumb-interwork\/mthumb-interwork<\/em> after MULTILIB_OPTIONS and normal interwork<\/em> after MULTILIB_DIRNAMES.\u00a0 I used nano, see the screenshot below if I haven’t been too clear \ud83d\ude42<\/p>\n
![\"\"](\"http:\/\/www.madox.net\/blog\/wp-content\/uploads\/2008\/11\/screenshot-madoxmadox-laptop-armelf-src-gcc-432-gcc-config-arm.png\" "\\"src-gcc-432-gcc-config-arm\\"")
<\/a><\/p>\nnano ~\/arm-elf\/src\/gcc-4.3.2\/gcc\/config\/arm\/t-arm-elf<\/p><\/blockquote>\n
Start building with fingers crossed…<\/h3>\n
Now we can start building the toolchain.\u00a0 Note my prefix is \/usr\/local<\/em>.\u00a0 First off binutils!<\/p>\n
cd ~\/arm-elf\/
\nmkdir build build\/binutils-2.19 build\/insight-6.8 build\/gcc-4.3.2 build\/newlib-1.16.0<\/p>\ncd ~\/arm-elf\/build\/binutils-2.19
\n~\/arm-elf\/src\/binutils-2.19\/configure –target=arm-elf –prefix=\/usr\/local –enable-interwork –enable-multilib –with-float=soft –disable-werror
\nsudo make all install<\/p><\/blockquote>\nNext just the gcc part of gcc…note we configure the newlib src headers here…<\/p>\n
cd ~\/arm-elf\/build\/gcc-4.3.2
\n~\/arm-elf\/src\/gcc-4.3.2\/configure –target=arm-elf –prefix=\/usr\/local –enable-interwork –enable-multilib –with-float=soft –disable-werror –enable-languages=”c,c++” –with-newlib\u00a0 –with-headers=~\/arm-elf\/src\/newlib-1.16.0\/newlib\/libc\/include
\nsudo make all-gcc install-gcc<\/p><\/blockquote>\nNow newlib…<\/p>\n
cd ~\/arm-elf\/build\/newlib-1.16.0
\n~\/arm-elf\/src\/newlib-1.16.0\/configure –target=arm-elf –prefix=\/usr\/local –enable-interwork –enable-multilib –with-float=soft –disable-werror
\nsudo make all install<\/p><\/blockquote>\nComing back for the rest off gcc (needed newlib)<\/p>\n
cd ~\/arm-elf\/build\/gcc-4.3.2
\nsudo make all install<\/p><\/blockquote>\n…and finally insight gdb<\/p>\n
cd ~\/arm-elf\/build\/insight-6.8
\n~\/arm-elf\/src\/insight-6.8\/configure –target=arm-elf –prefix=\/usr\/local –enable-interwork –enable-multilib –with-float=soft –disable-werror
\nsudo make all install<\/p><\/blockquote>\nVoila done!\u00a0 I should now have all my arm-elf tools!\u00a0 Just a check…<\/p>\n
\n
madox@madox-laptop:\/usr\/local\/bin$ ls arm*\r\narm-elf-addr2line arm-elf-gcc arm-elf-insight arm-elf-run\r\narm-elf-ar arm-elf-gcc-4.3.2 arm-elf-ld arm-elf-size\r\narm-elf-as arm-elf-gccbug arm-elf-nm arm-elf-strings\r\narm-elf-c++ arm-elf-gcov arm-elf-objcopy arm-elf-strip\r\narm-elf-c++filt arm-elf-gdb arm-elf-objdump\r\narm-elf-cpp arm-elf-gdbtui arm-elf-ranlib\r\narm-elf-g++ arm-elf-gprof arm-elf-readelf<\/pre>\n<\/blockquote>\n
Yup all there and runs \ud83d\ude42\u00a0 Now the search for the LPC header files… argh<\/p>\n
PS : If you copy and paste my commands, be wary of line breaks… I didn’t put \\’s anywhere…<\/p>\n","protected":false},"excerpt":{"rendered":"
Well this chronicles my first attempt at compiling a toolchain for programming ARM’s in ELF code. Why do I need a toolchain for programming ARMs? I found a LPC2378-STK development board in my room I want to give ARM programming a try (PS WinAVR is great for programming AVRs) I found I have some spare … Continue reading “Compiling a toolchain for ARM7 under Ubuntu”<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[22,17,16],"tags":[24,23,55,14],"class_list":["post-54","post","type-post","status-publish","format-standard","hentry","category-microcontrollers","category-software","category-software-tips-tricks","tag-arm","tag-crosscompiling","tag-microcontrollers","tag-ubuntu"],"_links":{"self":[{"href":"http:\/\/www.madox.net\/blog\/wp-json\/wp\/v2\/posts\/54","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/www.madox.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.madox.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.madox.net\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/www.madox.net\/blog\/wp-json\/wp\/v2\/comments?post=54"}],"version-history":[{"count":6,"href":"http:\/\/www.madox.net\/blog\/wp-json\/wp\/v2\/posts\/54\/revisions"}],"predecessor-version":[{"id":57,"href":"http:\/\/www.madox.net\/blog\/wp-json\/wp\/v2\/posts\/54\/revisions\/57"}],"wp:attachment":[{"href":"http:\/\/www.madox.net\/blog\/wp-json\/wp\/v2\/media?parent=54"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.madox.net\/blog\/wp-json\/wp\/v2\/categories?post=54"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.madox.net\/blog\/wp-json\/wp\/v2\/tags?post=54"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
- Realised (should have known) that you need ‘GMP’ and ‘MPFR’ to compile GCC.\u00a0 Available as packages libgmp3-dev<\/em> and libmpfr-dev<\/em> in Ubuntu.<\/li>\n