Thanks for taking the time to reply. To elaborate, I am looking in to making a package for the LeJOS NXJ Project ( http://lejos.sourceforge.net/ ), its a replacement firmware and api for the Lego Mindstorms NXT microcontroler. I would like this package to be available to normal users, it really needs to be in the main Debian repositories. I have been following the Lejos Developers advice on how to compile the correct toolchain so that the package can compile the custom firmware for the NXT. The toolchain is built for the arm-elf target. I have successfully built the toolchain but I am having problems packaging it. These are described below. On top of this the toolchain needs to be built exactly as upstream build it. Otherwise size problems could emerge and make the firmware unusable. The script upstream use to build the toolchain is attached. Does this change the approach you would suggest? Is there any packages you would recommend looking at for reference as I am a bit lost at the moment? Thanks, Chris On Wed, 2010-09-22 at 08:18 +0100, Neil Williams wrote: > Paul Wise drew my attention to this post, I'm not subscribed to mentors > anymore but please DO NOT CC: me - take the entire thread to > debian-embedded@lists.debian.org instead (where I am subscribed along > with all of those Debian people who are routinely building and using > cross-building toolchains in Debian.) > > > Hello, > > > > I am building packages for the arm elf toolchain. > > By ELF, I'm assuming you mean the ELF binary format but that then > doesn't describe which ABI or even endianness. Please clarify. > > ARM is the Debian name for the old StrongARM port > armel is the Debian name for ARMv5 EABI > armhf is the proposed Debian name for an ARM8 port to run on devices > like the Efika Genesis. > ARM9 chips like OMAP4 will use armel. > > > However I have ran in > > to some problems. The three components binutils, the gcc and newlib are > > in different packages. > > As they should be. > > > To build the toolchain you compile binutils, then > > the make the all-gcc and install-gcc targets of the gcc, then compile > > newlib, then return to the gcc and make the all target. See here > > http://www.gnuarm.com/support.html , at the bottom of the page. > > Try looking at the Emdebian cross-building toolchain stuff which is > likely to be more useful. > > http://www.emdebian.org/ > > > I have done everything so far except run the all target for the gcc. How > > do I build the newlib-arm-elf package in the middle of building the > > gcc-arm-elf package? Or is there another way of approaching the problem? > > http://packages.qa.debian.org/b/buildcross.html > > The correct list for these enquiries is the debian-embedded list: > > http://lists.debian.org/debian-embedded/ >
Attachment:
build_arm_toolchain.sh
Description: application/shellscript
Attachment:
signature.asc
Description: This is a digitally signed message part