This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]

Re: arm-aout vs arm-elf

To: Quality Quorum <qqi at world dot std dot com>
Subject: Re: arm-aout vs arm-elf
From: Richard Earnshaw <rearnsha at arm dot com>
Date: Mon, 15 Oct 2001 17:10:04 +0100
cc: Richard dot Earnshaw at arm dot com, Philip Blundell <pb at nexus dot co dot uk>, crossgcc at sources dot redhat dot com
Organization: ARM Ltd.
Reply-To: Richard dot Earnshaw at arm dot com


> > It would be far less acceptable to a user of, say, gcc-2.8 who upgraded to
> > gcc-2.95 if he found that the same configuration started targetting a
> > different processor.
> 
> I still do think that there are better ways to address the issue, at
> least there should be a statement in arm/README.

No, it should be (though currently isn't) in install.texi, which describes 
all the relevant ports.

R.


------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com

References:
- Re: arm-aout vs arm-elf
  - From: Quality Quorum

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]