Problem is solved. It was a problem in my configuration of
GCC.
Leif Ekblad
Here is the output from the same compile in the
/usr/src/toolchain/gcc-4.1-20051008/host-i686-pc-linux-gnu/gcc/ directory:
./xgcc -B/usr/src/toolchain/gcc-4.1-20051008/host-i686-pc-linux-gnu/gcc/ -B/
usr/local/rdos/bin/ -B/usr/local/rdos/lib/ -isystem
/usr/local/rdos/include -isystem /usr/local/rd
I rerun the compiler with -v option. This is the output:
./xgcc -B/usr/src/toolchain/gcc-4.2-20060107/host-i686-pc-linux-gnu/gcc/ -B/
usr/local/rdos/bin/ -B/usr/local/rdos/lib/ -isystem
/usr/local/rdos/include -isystem /usr/local/rdos/sys-include -o conftest
conftest.c -v
Reading specs from
/usr/s
On Wed, Jan 11, 2006 at 12:10:32PM +0100, Leif Ekblad wrote:
> In configure script, line 2580, there is a link test which checks if
> an executable can be generated. The config.log file emits the
> following errors:
>
> /usr/local/bin/rdos-ld: unrecognised emulation mode: -o
> Supported emulations
In configure script, line 2580, there is a link test which checks if
an executable can be generated. The config.log file emits the
following errors:
/usr/local/bin/rdos-ld: unrecognised emulation mode: -o
Supported emulations: elf_i386
collect2: ld returned status 1 exit status.
This error later