19.5.2014 17:53, Ken Mandelberg kirjoitti:
Thanks, I was looking at the wrong log. The right log shows
configure:3374: /big/objdir/./gcc/xgcc -B/big/objdir/./gcc/
-B/usr/local/m68k-elf/bin/ -B/usr/local/m68k-elf/lib/ -isystem
/usr/local/m68k-elf/include -isystem /usr/local/m68k-elf/sys-include
-o conftest -g -O2 conftest.c >&5
/big/objdir/./gcc/as: 87: exec: -mcpu=68020: not found
So two questions
1) Am I missing something about the 68020? Did I need to build
something else first?
The 'm68k-elf-as' for the 'm68k-elf' target should accept switches like :
680X0 options:
-l use 1 word for refs to undefined symbols [default 2]
-m68000 | -m68008 | -m68010 | -m68020 | -m68030 | -m68040 | -m68060
| -m68302 | -m68331 | -m68332 | -m68333 | -m68340 | -m68360 | -mcpu32
| -m5200 | -m5202 | -m5203 | -m5204 | -m5206 | -m5206e | -m5307 | -m5400
specify variant of 680X0 architecture [default
68020]
-m68881 | -m68882 | -mno-68881 | -mno-68882
target has/lacks floating-point coprocessor
[default yes for 68020, 68030, and cpu32]
-m68851 | -mno-68851
target has/lacks memory-management unit coprocessor
[default yes for 68020 and up]
The '-mcpu=68020' looks like a switch given to 'm68k-elf-gcc'...
The earlier logfile seems to tell your newbie-mistake :
configure:11134: checking for as
configure:11167: result: no
configure:11245: checking for m68k-elf-as
configure:11275: result: no
So the answer to your second question is that of course you must first
build GNU
binutils, including 'as', which will understand the m68k architecture,
not only
the host x86_64 CPU architecture!
The configure command for GNU binutils would be like :
../binutils-2.14/configure --target=m68k-elf
if you choose to not define your own install prefix via
'--prefix=$prefix', to use support
for national language error messages, no '--disable-nls' (bare english
messages) etc
The default install $prefix is '/usr/local', I myself use
'--prefix=/opt/cross' for cross GCCs...
