It really depends on what you want to get out of your system. I really wanted
to get the much (10 times !) faster EABI, and that turned out to be a
challenge. Note that Codesourcery claims EABI, but it is all soft-math (i.e.
you are NOT using the Maverick Crunch FPU!).
There are some guides on how to build cross-tools for gcc 4.2.1 (oabi) and
gcc4.3.4 (patched eabi, crunch enabled) at
http://nuclear.unh.edu/wiki/index.php?title=TS-72xx_Guides
For the eabi you also need to patch "gas" the assembler. I used the one from
binutils-2.20. The result is a very nice 2.6 kernel EABI Debian running on the
TS-7390 with Qt/embedded running eabi as well. So far so good, no segfaults or
kernel issues.
--- In Peter Gammie <> wrote:
>
> On 27/01/2010, at 3:23 AM, Blair wrote:
>
> > Quite simply, so I can work in XCode on my Mac. I do most of my work and
> > business on OSX and only use Windows when I have no other choice e.g.
> > Quickbooks for Manufacturing. I don't want to go down the road of trying to
> > get a desktop version of Linux up and running in a virtual machine. That's
> > one big unknown I should be able to eliminate.
>
> Ah, in that case I wish you luck. I use a Linux VM under VMWare Fusion 3, I
> guess partly because I never made friends with XCode. Also I find a trusty
> Debian installation, even under VMWare, a lot less of an unknown that OS X.
> :-)
>
> > I have successfully used crosstool-NG to build a toolchain that works for
> > 2.4 but apparently some component versions won't let me build a 2.6.29
> > kernel. The toolchain is made up of binutils, GCC, the C library, and the
> > kernel. So, the question is what versions are people using to build the
> > kernel?
>
> Well, as I said, the Codesourcery package uses GCC 4.4.1, binutils
> 2.19.51.20090709 and from
>
> http://www.codesourcery.com/sgpp/lite/arm/portal/kbentry22
>
> glibc 2.6.14. I used it to build 2.6.29.6 and 2.6.32.3, with the hrtimers
> stuff I talked about in another thread.
>
> The reason I ended up using Codesourcery was that after a week or so of
> trying to build cross-compiling tools, I found that almost all advice has
> bitrotten, was for obsolete versions, etc. and the scripts had ceased to be
> updated for a year or more.
>
> BTW for building kernels I would hope and expect that glibc is unnecessary,
> i.e. you could build a GCC using uC or newlib. I recall getting a
> newlib-bootstrapped GCC to compile something-or-other, but not busybox.
> Apparently this worked (under Linux), using binutils-2.18.50:
>
> tar xf gcc-4.2.3.tar.bz2
> tar xf newlib-1.18.0.tar.gz
> cd gcc-4.2.3
> ln -s ../newlib-1.18.0/newlib .
> ln -s ../newlib-1.18.0/libgloss .
> cd ..
>
> mkdir build-gcc
> cd build-gcc
> ../gcc-4.2.3/configure --target=arm-eabi --prefix=/usr/local/crossgcc/
> --with-newlib --with-gnu-as --with-gnu-ld --enable-languages=c,c++
> --enable-c99 --disable-nls --enable-threads=posix --enable-long-long
> make -j3
>
> I wonder if one could start with the Codesourcery source bundle and recompile
> it under OS X.
>
> cheers
> peter
>
> --
> http://peteg.org/
>
------------------------------------
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/ts-7000/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/ts-7000/join
(Yahoo! ID required)
<*> To change settings via email:
<*> To unsubscribe from this group, send an email to:
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
|