Message-ID: From: "Andris Pavenis" To: DJ Delorie , djgpp-workers AT delorie DOT com Date: Wed, 3 Mar 1999 13:51:48 +0200 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: egcs-1.1.X (Was: Re: Problems with collect2 in egcs-1.1.1 and 1.1.2preX) In-reply-to: <199903022023.PAA24968@envy.delorie.com> References: <199903022019 DOT UAA71690 AT out5 DOT ibm DOT net> (snowball3 AT usa DOT net) X-mailer: Pegasus Mail for Win32 (v3.02b14) Reply-To: djgpp-workers AT delorie DOT com On 2 Mar 99, at 15:23, DJ Delorie wrote: > > > Looking at the configure.in in egcs, I noticed just above *-pc- > > msdosdjgpp is *-msdos-go32. Would it be OK to delete the entries for > > *-msdos-go32 since *-pc-msdosdjgpp is the preferred triplet? > > No. You may issue a warning for those cases, though. > > The current official triplet is i586-pc-msdosdjgpp - it's the only one > that works right for both gcc and binutils. > > But, others may still be using other variants in specific cases. > I don't need target i[34567]-pc-go32. For me i[34567]-pc-msdosdjgpp is enough. config-guess detects DJGPP as i386-pc-msdosdjgpp for all i[3456]86. I override target (--target=i586-pc-msdosdjgpp) when I built egcs. One posible problem is that then compiler options defaults to -march=pentium -mcpu=pentium. It may seem to be dangerous but: - as I have tested at least some Linux distributions does the same (for example Slackware-3.5 and 3.6). So it there would be related problems with 386 or 486 I'm sure they would be fixed. - I have done some tests with my binaries on 386 and haven't found related problems (compiler was built with such compiler so if we would have problems with binaries on 386 it is likely that gcc should crash) - Also djdev202 is built for such target when cross-compiling and seems that also we don't have related problems So it looks that it's still safe to use target i586-pc-msdosdjgpp. But of course additional testing should be appreciated. Andris