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]
Other format: [Raw text]

Re: GCC 3.3 release criteria


Ghazi,

> > From: Matthias Klose <doko at cs dot tu-berlin dot de>
> > 
> > Kaveh R. Ghazi writes:
> > >  > From: Matthias Klose <doko at cs dot tu-berlin dot de>
> > >  > 
> > >  > yes, then I will "test" it on Debian unstable as well.
> > > 
> > > Great, thanks.  Though be aware that being the "tester" will mean
> > > Debian specific bugs will be pointed your way, and the responsibility
> > > to fix them prior to the release being made is yours not that of the
> > > Release Manager.
> > 
> > Well, then please leave this field blank. I cannot commit on this.
> 
> Sorry to hear that.  Is there anyone else who will commit to ensuring
> that GCC 3.3 works on some version of x86 Debian?

I think that your asking a bit too much of the testors in trying to
make them resposible for fixing "Debian" specific bugs.  It's a valuable
contribution just to setup and run the debian build using 3.3.

We are trying to do a debian build on parisc-linux.  The main hicup
so far relates to the switch to dwarf2 EH as the default exception
handling in 3.3.  Because libstdc++ and libgcc_s are still at the same
versioning as 3.2, debian can't switch to dwarf2 until the versioning
changes, or they do a complete new release.  This is a PA specific
issue but possibly other ports have other reasons to bump the versions
of libstdc++ and libgcc_s.

Dave
-- 
J. David Anglin                                  dave dot anglin at nrc-cnrc dot gc dot ca
National Research Council of Canada              (613) 990-0752 (FAX: 952-6605)


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