This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


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

RE: Removal of V2 code


I can't get cygwin to bootstrap, and haven't since early september.  Given
this, it is difficult to confirm that the change to V3 works 

> -----Original Message-----
> From:	Christopher Faylor [SMTP:cgf@redhat.com]
> Sent:	Monday, 20 November 2000 12:24
> To:	Geoff Keating
> Cc:	Mark Mitchell; gcc@gcc.gnu.org
> Subject:	Re: Removal of V2 code
> 
> On Sun, Nov 19, 2000 at 05:10:33PM -0800, Geoff Keating wrote:
> >Mark Mitchell <mark@codesourcery.com> writes:
> >> I plan on doing a `cvs remove' on the V2 sources, and removing the
> >> configury bits for V2 at the end of next week as things seem to be
> >> settling OK with V3.  (There are still some AIX issues with V3, but
> >> they seem to be well on the path to resolution.)
> >> 
> >> If you have objections to this plan (i.e., you need the V2 sources to
> >> continue your work), you should:
> >> 
> >>   - Try hard to get V3 working on your platform.
> >> 
> >>   - Complain to me.  Explain why you can't switch to V3, and what 
> >>     you need in order to make that happen.
> >> 
> >> We can keep V2 in the tree for a bit longer, if we need to, but you'll
> >> have to come up with a good reason... :-)
> >
> >The embedded platforms (*-elf, powerpc-eabi*, *-coff) don't work yet with
> V3; I
> >don't believe anyone, certainly not at Red Hat, will be able to fix
> >this until next month; we don't have time.
> >
> >I don't know what the vxworks status is, but I'd bet it doesn't work
> either.
> >
> >I don't know what the Cygwin status is.  It may work.
> 
> Cygwin should be ok.
> 
> cgf

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