RE: [avr-gcc-list] Bug? gcc silently assumes mcu model when linking, creating bad executable

[Weddington, Eric]

> -----Original Message-----
> From: Dave N6NZ [mailto:address@hidden 
> Sent: Monday, April 21, 2008 1:38 PM
> To: Weddington, Eric
> Cc: Joerg Wunsch; address@hidden
> Subject: Re: [avr-gcc-list] Bug? gcc silently assumes mcu 
> model when linking, creating bad executable
> 
> 
> Weddington, Eric wrote:
> >  
> >> As Weddington, Eric wrote:
> >>
> >>>> My guess is all this comes from a time when AVR-GCC was created,
> >>>> and there were maybe three or four different AVRs only, so it did
> >>>> make some sense for it to default to one of them (IIRC, it
> >>>> defaults to the AT90S8515).
> >>> I thought it defaults to an architecture, avr2 to be exact.
> >> As the linker has to default to some crt*.o file, it effectively
> >> defaults to a particular device.  But those days, the differences
> >> between an architecture and a particular device were probably
> >> neglicible...
> > 
> > Then a GCC bug report should be filled out and set it to 
> "enhancement"
> > to give an error if -mmcu is not on the compile and link 
> command line.
> > 
> 
> In the short term, wouldn't it be possible to let the default 
> run time 
> library be a bogus crt.o that is guaranteed to throw a linker 
> error? 

Actually it should be fairly easy to do it normally with GCC's parameter
system. I don't think we'll need to do a kludge, even for the
short-term.