-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Rob Landley schreef: > On Sunday 12 August 2007 7:41:47 pm Bernd Schmidt wrote: >> Koen Kooi wrote: >>> -----BEGIN PGP SIGNED MESSAGE----- >>> Hash: SHA1 >>> >>> Rob Landley schreef: >>>> If there are patches against mainline that add blackfin support to the >>>> most recent release version of gcc, I'll happily test them. But >>>> starting from a separate tarball is uninteresting. >>> Mainline gcc already support blackfin (from 4.0.x iirc), but not the >>> extra funky command line options like -mfdpic or -mleaf-shared-id. I just >>> succesfully built (well, OE built it) the uclibc fork with a pretty >>> vanilla gcc 4.2.1 and the elf2flt wrapper. >> I can only repeat my advice that by doing so, you won't actually get >> binaries that work with our uClinux distribution. Please use the >> binaries from our web page. > > But can I get binaries that run on the hardware if I build my own kernel and > C > library? > > I'm interested in getting binaries that work with the hardware and which I > can > reproduce from standard sources. I'm trying to build the same software > across as many different platforms as possible. Platforms that can't do this > because they're "special" remind me of the "special olympics" and "very > special episode" uses of the word special. > > But I'm probably not your target audience. :)
I'm in the same kind of situation as Rob, I want to have my *own* distribution running on the board. I don't care as much about standard sources as Rob, maybe I'm a bit more pragmatic :) The fun starts when you have to build a avr32 gcc and bfin gcc from the same source. An excerpt from the patch that Atmel distributes (for gcc 4.0.2): - -| avr-* \ - -| bfin-* | bs2000-* \ +| avr-* | avr32-* \ +| bs2000-* \ ehm... that's 'special' regards, Koen -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) iD8DBQFGwAtDMkyGM64RGpERAsifAJ9RDweiOA4I2IAKE+t7/FybogR96gCaAgrj K6a/z+nIQxLJH4BbzFmmeZg= =fWCk -----END PGP SIGNATURE----- _______________________________________________ uClibc mailing list [email protected] http://busybox.net/cgi-bin/mailman/listinfo/uclibc
