Re: GCC 4.2 transition
On Fri, Jul 20, 2007 at 10:16:27AM +0200, Matthias Klose wrote: > The plans for the GCC 4.2 transition were described in > > http://lists.debian.org/debian-devel-announce/2007/06/msg8.html > > Does any port still need to stick with GCC 4.1 for a while? Feedback > from hppa, mips*, s390, powerpc, amd64, i386 porters doesn't show > objections against the transition. According to Bastian Blank, gcc 4.2 currently produces broken sparc kernel images. Another thing which comes to mind: we have recently announced that sparc32 machines are not going to be supported in lenny. Transition to the new gcc version seems like a perfect time to turn on the ultrasparc specific optimizations in gcc by default. Do you think it is feasible? I currently have no idea what breakage such a change might cause. Best regards, -- Jurij Smakov [EMAIL PROTECTED] Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: GCC 4.2 transition
On Fri, Jul 20, 2007 at 11:51:47AM +0200, Mike Hommey wrote:
> On Fri, Jul 20, 2007 at 11:33:01AM +0200, Johannes Berg <[EMAIL PROTECTED]>
> wrote:
> > On Fri, 2007-07-20 at 10:16 +0200, Matthias Klose wrote:
> >
> > > Does any port still need to stick with GCC 4.1 for a while? Feedback
> > > from hppa, mips*, s390, powerpc, amd64, i386 porters doesn't show
> > > objections against the transition.
> >
> > I have objections :)
> > http://bugs.debian.org/433629
> > Yes, it's pretty odd, but recompiling the whole kernel tree with gcc 4.2
> > causes my usbhid to totally not work.
>
> I have another objection. I'd like all mozilla security updates to be built
> before gcc 4.2 becomes the default, because they don't build correctly yet,
> and I am (still) waiting for an upstream comment on how to fix it.
>
On a more general note, I'd like to see xulrunner/nss built and
depending packages[0] built so we can get the fixes into testing easier
before this is started.
Cheers,
Neil
[0] Most of: http://security-tracker.debian.net/tracker/status/dtsa-candidates
--
int getRandomNumber() {
return 4; // chosen by fair dice roll. guaranteed to be random.
}
// http://xkcd.com/c221.html
signature.asc
Description: Digital signature
Re: GCC 4.2 transition
On Fri, Jul 20, 2007 at 11:33:01AM +0200, Johannes Berg <[EMAIL PROTECTED]> wrote: > On Fri, 2007-07-20 at 10:16 +0200, Matthias Klose wrote: > > > Does any port still need to stick with GCC 4.1 for a while? Feedback > > from hppa, mips*, s390, powerpc, amd64, i386 porters doesn't show > > objections against the transition. > > I have objections :) > http://bugs.debian.org/433629 > Yes, it's pretty odd, but recompiling the whole kernel tree with gcc 4.2 > causes my usbhid to totally not work. I have another objection. I'd like all mozilla security updates to be built before gcc 4.2 becomes the default, because they don't build correctly yet, and I am (still) waiting for an upstream comment on how to fix it. Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: GCC 4.2 transition
On Fri, 2007-07-20 at 10:16 +0200, Matthias Klose wrote: > Does any port still need to stick with GCC 4.1 for a while? Feedback > from hppa, mips*, s390, powerpc, amd64, i386 porters doesn't show > objections against the transition. I have objections :) http://bugs.debian.org/433629 Yes, it's pretty odd, but recompiling the whole kernel tree with gcc 4.2 causes my usbhid to totally not work. johannes signature.asc Description: This is a digitally signed message part
GCC 4.2 transition
The plans for the GCC 4.2 transition were described in http://lists.debian.org/debian-devel-announce/2007/06/msg8.html Does any port still need to stick with GCC 4.1 for a while? Feedback from hppa, mips*, s390, powerpc, amd64, i386 porters doesn't show objections against the transition. Matthias -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
