Bug 15951 - m68k-*-elf doesn't allow --with-cpu= in the configure script
Summary: m68k-*-elf doesn't allow --with-cpu= in the configure script
Status: RESOLVED FIXED
Alias: None
Product: gcc
Classification: Unclassified
Component: target (show other bugs)
Version: 3.4.0
: P2 enhancement
Target Milestone: 4.3.0
Assignee: Bernardo Innocenti
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-06-12 09:42 UTC by Matthew Dempsky
Modified: 2008-01-25 20:33 UTC (History)
1 user (show)

See Also:
Host: i686-pc-linux-gnu
Target: m68k-unknown-elf
Build: i686-pc-linux-gnu
Known to work:
Known to fail:
Last reconfirmed: 2005-06-20 03:04:31

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Matthew Dempsky 2004-06-12 09:42:48 UTC 
$ ../combined/configure --target=m68k-elf --prefix=`pwd`/../install
--with-newlib --with-gnu-as --with-gnu-ld --enable-languages=c
--disable-multilib --with-cpu=cpu32
  [ omitted ]
$ make
  [ omitted ]
This target does not support --with-cpu.
make: *** [configure-gcc] Error 1

I noticed m68k-*-linux has with-cpu support, would it be difficult to allow it
for m68k-*-elf too?
Comment 1 Andrew Pinski 2004-06-12 12:31:49 UTC 
Confirmed.
Comment 2 Bernardo Innocenti 2004-06-19 01:20:10 UTC 
Perhaps I'll have some time to work on it over the 
next few weeks.  Don't hold your breath, though :)
Comment 3 Ben Elliston 2008-01-22 03:22:54 UTC 
This now works on mailine:

 ./xgcc -B. -v foo.c
Reading specs from ./specs
Target: m68k-elf
Configured with: /home/bje/source/gcc-trunk/configure --target=m68k-elf --enable-languages=c --disable-mutilib --with-cpu=cpu32
[...]
 ./cc1 -quiet -v -iprefix /scratch/bje/m68k/gcc/../lib/gcc/m68k-elf/4.3.0/ -isystem ./include -isystem ./include-fixed foo.c -quiet -dumpbase foo.c -mcpu=cpu32 -auxbase foo -version -o /tmp/cczoPnzM.s

I propose that since it is highly unlikely to ever be fixed in 3.4, that we close this bug.  OK?
Comment 4 Bernie Innocenti 2008-01-22 08:21:35 UTC 
Ok for me.
Comment 5 Richard Biener 2008-01-25 20:33:24 UTC 
Thus, fixed.