Message

Reply | Reply all

Date Prev | Date Next | Thread Prev | Thread Next Date Index | Thread Index

From: Heiko Panther<heiko.panther@w...>
Date: Tue Jan 20 19:01:06 CET 2004
Subject: [openrisc] making the or1ksim testbench
I've been porting or1ksim to Mac OS X. After I got the simulator through
the compiler (wow! what a bunch of warnings!) I tried to configure the
testbench with --target=or32-elf.

Here's the failing part:
checking for or32-elf-gcc... or32-elf-gcc
checking for or32-elf-ranlib... or32-elf-ranlib
checking for or32-elf-ld... or32-elf-ld
checking for or32-elf-sim... or32-elf-sim
checking for style of include used by make... GNU
checking for gcc... (cached) or32-elf-gcc
checking for C compiler default output... a.out
checking whether the C compiler works... configure: error: cannot run C
compiled programs.

configure:2531: checking for C compiler default output
configure:2534: or32-elf-gcc conftest.c >&5
configure:2537: $? = 0
configure:2583: result: a.out
configure:2588: checking whether the C compiler works
configure:2594: ./a.out
configure: line 1: ./a.out: cannot execute binary file
configure:2597: $? = 126
configure:2606: error: cannot run C compiled programs.


The trouble seems to be that configure does some tests for the or32-gcc,
and sets CC=or32-elf-gcc, according to this line:

AC_CHECK_TOOL(CC, $target-gcc, cc)

Then later, configure tries to run an executable built with or32-elf-gcc
on my host machine, and fails.

Any ideas?

Heiko