can you provide some info on the following params for the sheeva plug?
 
your bootstrap has the following for the hardfp project.
 
            --with-cpu=cortex-a8
            --with-tune=cortex-a8
            --with-arch=armv7-a
            --with-float=hard
            --with-fpu=vfpv3-d16
 
ill take a jab....
 
            --with-cpu=arm9e
            --with-tune=arm9e
            --with-arch=armv5te
            --with-float=softfp
#            --with-fpu=vfpv3-d16

<no fpu in sheevaplug>
 
-mcpu=name
This specifies the name of the target ARM processor. GCC uses this name to determine what kind of instructions it can emit when generating assembly code. Permissible names are: `arm2', `arm250', `arm3', `arm6', `arm60', `arm600', `arm610', `arm620', `arm7', `arm7m', `arm7d', `arm7dm', `arm7di', `arm7dmi', `arm70', `arm700', `arm700i', `arm710', `arm710c', `arm7100', `arm720', `arm7500', `arm7500fe', `arm7tdmi', `arm7tdmi-s', `arm710t', `arm720t', `arm740t', `strongarm', `strongarm110', `strongarm1100', `strongarm1110', `arm8', `arm810', `arm9', `arm9e', `arm920', `arm920t', `arm922t', `arm946e-s', `arm966e-s', `arm968e-s', `arm926ej-s', `arm940t', `arm9tdmi', `arm10tdmi', `arm1020t', `arm1026ej-s', `arm10e', `arm1020e', `arm1022e', `arm1136j-s', `arm1136jf-s', `mpcore', `mpcorenovfp', `arm1156t2-s', `arm1156t2f-s', `arm1176jz-s', `arm1176jzf-s', `cortex-a5', `cortex-a8', `cortex-a9', `cortex-a15', `cortex-r4', `cortex-r4f', `cortex-r5', `cortex-m4', `cortex-m3', `cortex-m1', `cortex-m0', `xscale', `iwmmxt', `iwmmxt2', `ep9312', `fa526', `fa626', `fa606te', `fa626te', `fmp626', `fa726te'.
-mtune=name
This option is very similar to the -mcpu= option, except that instead of specifying the actual target processor type, and hence restricting which instructions can be used, it specifies that GCC should tune the performance of the code as if the target were of the type specified in this option, but still choosing the instructions that it will generate based on the CPU specified by a -mcpu= option. For some ARM implementations better performance can be obtained by using this option.
-march=name
This specifies the name of the target ARM architecture. GCC uses this name to determine what kind of instructions it can emit when generating assembly code. This option can be used in conjunction with or instead of the -mcpu= option. Permissible names are: `armv2', `armv2a', `armv3', `armv3m', `armv4', `armv4t', `armv5', `armv5t', `armv5e', `armv5te', `armv6', `armv6j', `armv6t2', `armv6z', `armv6zk', `armv6-m', `armv7', `armv7-a', `armv7-r', `armv7-m', `iwmmxt', `iwmmxt2', `ep9312'. 
 
 
-------- Original Message --------
Subject: RE: [fedora-arm] ppl cross compile
From: <webwillow@thewebwillow.com>
Date: Fri, August 19, 2011 4:13 am
To: "DJ Delorie" <dj@redhat.com>
Cc: arm@lists.fedoraproject.org

already using it and made adjustments for armv5tel and soft float.
 
when i get to the ppl part of the script i get the failure...you scripts have got me this far with only tiny adjustments needed
 
i than try to reproduce the exact same thing manually and adjust from there..
 
although i did notice the prefix of /usr instead of $PREFIX...ill redo gmp/mpfr/ppl again tonight and see if that makes it through.
 
sometimes you make those little mistakes when frustrated and just plain tired in the middle of the night.
 
../../rpmbuild/BUILD/ppl-0.11.2/configure --prefix=/usr --build=i686-redhat-linux --host=arm-unknown-linux-gnueabi --with-float=softfp --with-abi=aapcs-linux --with-sysroot=/home/mockbuild/stage2/rootfs --enable-threads=posix --disable-libssp --enable-cxx=yes --enable-werror=no 
 
-------- Original Message --------
Subject: Re: [fedora-arm] ppl cross compile
From: DJ Delorie <dj@redhat.com>
Date: Thu, August 18, 2011 9:02 pm
To: <webwillow@thewebwillow.com>
Cc: arm@lists.fedoraproject.org


Try my bootstrap scripts at:

http://djdelorie.fedorapeople.org/