Christopher Friedt wrote: > Interesting... I'm using the 'crunch.tar.gz' package that has several > bitbake scripts (.bb files) from the cirrus list as well.
> http://martinwguy.co.uk/martin/FPU/futaris > My plan is to just create my own portage overlay, and root through all > of the patches (one by Mike Frysinger, I might add) to get eabi and > maverick crunch working. > Binutils-2.17 was quite simple to patch (there was only 1 patch file), > but gcc seems to have _lots_ ... > Aside from that, I think that ECONF_EXTRA needs to be set in order to > get crunch support by default on the C compiler. For that, what I'm > using is: > ECONF_EXTRA="--without-x --enable-languages=c,c++ \ > --with-cpu=ep9312 --with-float-abi=softfp --with-fpu=maverick" \ > crossdev -S armv4t-maverick-linux-gnueabi > OK, I gave this a shot, literally; here are the results I get: # ECONF_EXTRA="--without-x --enable-languages=c,c++ \ > --with-cpu=ep9312 --with-float-abi=softfp --with-fpu=maverick" \ > crossdev -S armv4t-maverick-linux-gnueabi ------------------------------------------------------------------------------------ * Host Portage ARCH: amd64 * Target Portage ARCH: arm * Target System: armv4t-maverick-linux-gnueabi * Stage: 4 (C/C++ compiler) * binutils: binutils-[stable] * gcc: gcc-[stable] * headers: linux-headers-[stable] * libc: glibc-[stable] * PORTDIR_OVERLAY: /usr/local/portage * PORT_LOGDIR: /var/log/elog/ * PKGDIR: /usr/portage/packages/cross/armv4t-maverick-linux-gnueabi * PORTAGE_TMPDIR: /var/tmp/cross/armv4t-maverick-linux-gnueabi _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - * Forcing the latest versions of {binutils,gcc}-config/gnuconfig ... [ ok ] * Log: /var/log/elog//cross-armv4t-maverick-linux-gnueabi-binutils.log * Emerging cross-binutils ... [ ok ] * Log: /var/log/elog//cross-armv4t-maverick-linux-gnueabi-gcc-stage1.log * Emerging cross-gcc-stage1 ... [ ok ] * Log: /var/log/elog//cross-armv4t-maverick-linux-gnueabi-linux-headers.log * Emerging cross-linux-headers ... [ ok ] * Log: /var/log/elog//cross-armv4t-maverick-linux-gnueabi-glibc.log * Emerging cross-glibc ... [ ok ] * Log: /var/log/elog//cross-armv4t-maverick-linux-gnueabi-gcc-stage2.log * Emerging cross-gcc-stage2 ... * gcc failed :( * If you file a bug, please attach the following logfiles: * /var/log/elog//cross-armv4t-maverick-linux-gnueabi-info.log * /var/log/elog//cross-armv4t-maverick-linux-gnueabi-gcc-stage2.log > (these options can be passed to the gcc configure script, see > gcc*/INSTALL/index.html -> configure) I'm not sure where exactly how to pass these options. > Sorry, are you having problems creating an i686 -> Same trouble by my workstation is a AMD64 (x86_64-pc-linux-gnu). > arm-softfloat-linux-gnu cross-compiler or cross-compiling gcc for > softfloat? Softfloat should compile cleanly, but I've had to apply two > patches (1 of which should definitely be upstream) > > 1) externalize jar and 2) @progbits patch for arm/sysv.S > > The externalize jar patch is only necessary for libjava / gcj ... and > from what I've seen, it's pretty damn slow on the arm anyway, so I'll > probably forget about it. Can you explain in a little bit more detail how these patches are applied? > I'll let you know if I have any success with my overlay, but sorting > through all of the patches for gcc might take quite a bit of time. > > ~/Chris James -- [email protected] mailing list
