Frank Beesley wrote:
"../gcc-4.0.1/configure --prefix=$PREFIX --target=$TARGET --disable-nls
--disable-shared --enable-languages=c --without-headers --with-newlib"
"make"
I get farther then the message you have but it still fails with:
checking for powerpc-motorola-linux-gcc... /rpm/ppc/build/gcc/gcc/xgcc
-B/rpm/ppc/build/gcc/gcc/ -B/opt/ppc/powerpc-motorola-linux/bin/
-B/opt/ppc/powerpc-motorola-linux/lib/ -isystem
/opt/ppc/powerpc-motorola-linux/include -isystem
/opt/ppc/powerpc-motorola-linux/sys-include
checking for C compiler default output file name... configure: error: C
compiler cannot create executables
What do you think being required for "creating executables" ? If you
know this quite basic thing about "C compilers", then you also know why
it cannot create them !
In the GCC world, "creating executables" is very far from "compiling",
but in the Windoze MSVC, BCC etc. cases "compiling" is considered being
just the same thing as "creating executables" !
So, believe me or not, this error message is really misleading or just
a fact in the GCC world: A "C compiler" never creates executables there,
it doesn't even "create objects", one needs an assembler from the GNU
binutils or some "native 'as'" for this task... What kind of tool
creates executables and what kind of components will be required
additionally with the "compiled & assembled" object created from the
"hello world" C source, will be leaved to you as a homework to find
out...
In your case I would try writing :
make install-gcc
and then try "compiling" a Hello World in order to see what happens:
powerpc-motorola-linux-gcc -v -O2 -o hello-test hello.c
Can it create this 'hello-test' executable at all? What very obvious is
still missing
