https://gcc.gnu.org/bugzilla/show_bug.cgi?id=18385
Jeffrey A. Law changed:
What|Removed |Added
Status|SUSPENDED |RESOLVED
CC|
--- Additional Comments From bernhard dot walle at gmx dot de 2004-12-13
10:55 ---
I don't understand. Why should it search in 68040 directory? There is probably
m68040 code, but if I compile with -m68000 I *don't* want 68040 code but plain
68000 code.
--
--- Additional Comments From bernhard dot walle at gmx dot de 2004-12-14
11:21 ---
It's
m68k-elf-gcc -o test.out test.o -lm -m68000 -Wl,-Tmvme162.ld -Wl,-v
collect2-Version 3.4.3 (68k, Motorola syntax)
/opt/m68k/lib/gcc/m68k-elf/3.4.3/../../../../m68k-elf/bin/ld -o test.out
--- Additional Comments From bernie at develer dot com 2004-12-13 09:49
---
The top-level multilib directory is compiled for the
default target, which is in some cases m68000, and
in some cases m68020.
m68k-elf defaults to m68000. Perhaps your linker
script doesn't look into the
--- Additional Comments From bernie at develer dot com 2004-12-14 01:23
---
Sorry, I've read your report vice-versa, because that's
the most likely thing that could have happened (there were
so many bogus uClinux reports that I finally decided to
remove m68000 libraries from the
--
What|Removed |Added
Component|bootstrap |target
Summary|Bootstrap code contains |code contains 68040
|68040
