Asfand Yar Qazi kirjoitti:
../gcc-4.1-branch/configure --prefix=/usr/local/gcc --disable-nls
--enable-version-specific-runtime-libs --enable-__cxa_atexit
--enable-languages=c,c++ --build=x86_64-pc-linux-gnu
--host=x86_64-pc-linux-gnu --target=x86_64-pc-linux-gnu
and get this:
checking host system type... x86_64-pc-linux-gnu
checking target system type... x86_64-pc-linux-gnu
checking build system type... x86_64-pc-linux-gnu
<snip>
*** This configuration is not supported in the following subdirectories:
target-libada gnattools target-libgfortran target-libffi target-boehm-gc
Funny but I got :
/data1/home/src/gcc-4.1.0/build # ls -l x86_64-suse-linux9.2
total 44
drwxr-xr-x 11 root root 4096 2006-05-12 13:57 ./
drwxr-xr-x 11 root root 4096 2006-05-12 13:19 ../
drwxr-xr-x 10 root root 4096 2006-05-12 13:59 32/
drwxr-xr-x 4 root root 4096 2006-05-12 14:06 boehm-gc/
drwxr-xr-x 6 root root 4096 2006-05-12 13:56 libffi/
drwxr-xr-x 4 root root 4096 2006-05-12 13:26 libiberty/
drwxr-xr-x 11 root root 4096 2006-05-12 14:03 libjava/
drwxr-xr-x 6 root root 4096 2006-05-12 13:51 libmudflap/
drwxr-xr-x 5 root root 4096 2006-05-12 13:54 libssp/
drwxr-xr-x 9 root root 4096 2006-05-12 13:22 libstdc++-v3/
drwxr-xr-x 3 root root 4096 2006-05-12 14:04 zlib/
when I tried gcc-4.1.0 for the SuSE 9.2/x86_64 target.... The
'target-libffi' and 'target-boehm-gc' seemed to be "supported" here !
Maybe leaving 'java' out from the '--enable-languages=' caused this.
But not completely for cross-building :-(, the build stopped with :
/opt/gcc/x86_64-suse-linux9.2/bin/ld: cannot find /lib64/libpthread.so.0
collect2: ld returned 1 exit status
make[3]: *** [libgcjgc.la] Error 1
make[3]: Leaving directory
`/data1/home/src/gcc-4.1.0/build/x86_64-suse-linux9.2/boehm-gc'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory
`/data1/home/src/gcc-4.1.0/build/x86_64-suse-linux9.2/boehm-gc'
make[1]: *** [all-target-boehm-gc] Error 2
make[1]: Leaving directory `/data1/home/src/gcc-4.1.0/build'
Which simply told that not only the '/usr/lib*/libc.so's, but also the
'/usr/lib*/libpthread.so' scripts were 'one eyed'ly written for only native
use... There of course then was no symlinks for the 'libpthread.so.0's from
'usr/lib*' to '../../lib*' for finding those 'bare libpthread.so.0's
after editing
these scripts. But adding them helped....
checking whether the C compiler works... configure: error: cannot run C
compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details.
What's going on?
You didn't find your eyeglasses and therefore didn't see the "See...
for more
details" suggestion ? "Who else could raise the cat's tail if not the
cat itself".
Whatever went wrong, can be seen in that 'config.log' in the directory where
the configure failed !
Your "gcc-4.1-branch" as the name for the 'gcc-4.1.x' sources of course
sounds
odd. If these sources were experimental prereleases for something, they can
be very badly broken sometimes. I would suggest trying the official releases
first..
