Hi,
On 15 Sep 2005, at 10:47, Nick Rout wrote:
On Thu, 2005-09-15 at 10:11 +0100, Andrew Holt wrote:
The example you give is for a 386 target. I presume that I have to
specify CC=<compiler> to configure, and --target ?
If I simply follow the instructions I end up with a 386 executable.
If I add CC=/opt/hardhat/devkit/ppc/8xx/bin/ppc-8xx-gcc then I get:
./build-ppc
checking for gcc... /opt/hardhat/devkit/ppc/8xx/bin/ppc-8xx-gcc
checking for C compiler default output... configure: error: C
compiler cannot create executables
See `config.log' for more details.
No doubt you have consulted config.log and found nothing interesting.
I looked again, and I found a typo, ppc-8xx-gcc should be ppc_8xx-
gcc, so I tried again, and I got somewhat farther
......
checking how to suppress 'unused variable' warnings... __attribute__
((unused))
checking for asm.fs... arch/386/asm.fs
checking for disasm.fs... arch/386/disasm.fs
checking for install-info... /sbin/install-info
checking whether byte ordering is bigendian... (cached) yes
checking if and how we can waste code space... configure: error:
cannot run test program while cross compiling
See `config.log' for more details.
Now, looking through config.log CFLAGS does not appear to be set to
anything, and it's unset in the environment. There is an assignment:
machine='386'
Does this refer to the host or the target ? I suspect I need to put
more in the env line, any hints ?
Regards,
Andrew
I suspect you need to check your CFLAGS env variable, it may have x86
style settings that are inappropriate to ppc.
Regards,
Andrew
--
Nick Rout <[EMAIL PROTECTED]>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
