All easy - see <http://www.scratchbox.org/wiki/ForeignToolchains> http://www.scratchbox.org/wiki/ForeignToolchains
and <http://qemu-arm-eabi.wiki.sourceforge.net/> http://qemu-arm-eabi.wiki.sourceforge.net/ Post problems to this list and I will (eventually ;-) ) reply Regards Peter _____ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeffrey L. Franks Sent: 09 September 2008 15:58 To: scratchbox-users@lists.scratchbox.org Subject: [Scratchbox-users] New user asks for guidance Hi, My goal is to use my working TimeSys toolchain, (based on Code Sourcery ARM9 gcc-4.2 eabi) as a foreign toolchain under Scratchbox. This has tools like armv5l-linux-gcc, full complement of binutils, etc. I have armv5l glibc root file system. All of this is already installed as per TimeSys instructions and ends up at /opt/timesys/ . . . . My host machine is Debian Lenny (beta2). I also have a target from Atmel at91sam9263-ek board that has Linux running on it and is network capable. Regarding Scratchbox, Ive downloaded and setup Scratchbox Apophis and successfully completed an ARM cross-compile and emulation using Qemu with out-of-the-box tool chains. This was a good start to understanding how powerful this environment really is. These toolchains are not matched up for my particular ARM target and that is where the TimeSys toolchain comes into the picture. My concern is whether Im on the right path using Scratchbox Apophis, and whether I can make the TimeSys toolchain work w/ Scratchbox plus be able to emulate eabi code using Qemu. Anyone have some opinions regarding this approach and how to make it work, what to watch out for? How hard is this going to be? --Jeff Franks
_______________________________________________ Scratchbox-users mailing list Scratchbox-users@lists.scratchbox.org http://lists.scratchbox.org/cgi-bin/mailman/listinfo/scratchbox-users
