Hi James,
It is as I suspected according to your log file -
--disable-libgcj
--enable-languages=c,c++,fortran
Fortran has been a bit problematic with crossdev - I usually have to
build my toolchains without fortran support, and that requires:
USE="-fortran"
ECONF_EXTRA="--with-languages=c,c++"
When compiling GCC, the fortran component of gcc looks for libgmp and
also libmfpr (or one of them at least), both in the "rpath".
The "rpath" is usually /lib or /usr/lib (not ${SYSROOT}/lib or any other
default compiler search path).
Obviously, when cross-compiling, the libgmp / libmfpr that it finds is a
.so file for i686 or whatever your build architecture is, and they are
definitely not compatible with arm object code.
I would only suggest trying to add a fortran compiler when you're
compiling gcc _natively_ on your board, although that can be quite a
tedious process and you'll likely need some swap in the form of an SD
card or USB memory stick.
By the way, I still haven't done any hardware floating point
acceleration testing because I haven't had all that much spare time
lately. So if you are up for it, try it out.
Martin Guy has a few benchmarks and the average speedups with LAME are
OABI -> EABI: ~11
EABI/softfp -> EABI/hardfp: 2
That means OABI -> EABI/hardfp: ~22.
~/Chris
--
[email protected] mailing list
