This is the mail archive of the
mailing list for the binutils project.
Re: current binutils trunk failures on cygwin
- From: "H. J. Lu" <hjl at lucon dot org>
- To: Dave Korn <dave dot korn at artimi dot com>
- Cc: 'Nick Clifton' <nickc at redhat dot com>, 'Christian Joensson' <christian dot joensson at gmail dot com>, 'binutils' <binutils at sources dot redhat dot com>
- Date: Wed, 3 May 2006 09:51:49 -0700
- Subject: Re: current binutils trunk failures on cygwin
- References: <4458C5CD.firstname.lastname@example.org> <001c01c66eca$f2fe7790$a501a8c0@CAM.ARTIMI.COM>
On Wed, May 03, 2006 at 05:02:16PM +0100, Dave Korn wrote:
> On 03 May 2006 16:02, Nick Clifton wrote:
> >> Does COFF have the same issue?
> > No - it is only PE that has the issue.
> >> Here is a patch.
> >> +#not-target: *-*-*pe* *-*-*coff i*86-*-cygwin* i*86-*-mingw32*
> > You do not need the *-*-coff here. In fact it should not be there.
> Say, isn't that first pattern going to inadvertently match *-*-openbsd,
> *-*-mpeix, *-*-openedition, *-*-openstep, *-*-superux? (This based on a
> quick grepping through top-level config rather than detailed knowledge of
> which platforms are supported by binutils).
> Should it perhaps be just "*-*-pe*", which matches the test in config.sub?
> I can't see any PE-coff targets that have anything prefixing 'pe' in the third
> part of the triplet.
It should be "*-*-pe".