Re: defaulting to GCC-4.7 for kfreebsd

2012-05-05 Thread Petr Salinger
As long as amd64 and i386 switch too, then I think it would be okay for us to do the same?  But I really want to hear confirmation from Robert and/or Christoph.  I don't think I am really qualified/knowledged to make an informed decision here -- the people with the real knowledge in kfreebsd int

Re: defaulting to GCC-4.7 for kfreebsd

2012-05-05 Thread Robert Millan
2012/5/5 Christoph Egger : >> I tried anyway with gcc-4.7, and src:kfreebsd-9 successfully built a >> kfreebsd-i386 kernel that seems stable for a few days now.  Also the >> freebsd-utils (essential stuff for kfreebsd-* arches) were okay. > >  This is, however good to know. Good thing to have the p

Re: defaulting to GCC-4.7 for kfreebsd

2012-05-05 Thread Robert Millan
2012/5/5 Christoph Egger : >> As long as amd64 and i386 switch too, then I think it would be okay for >> us to do the same?  But I really want to hear confirmation from Robert >> and/or Christoph. > >  I don't think I am really qualified/knowledged to make an informed > decision here -- the people

Re: defaulting to GCC-4.7 for kfreebsd

2012-05-05 Thread Christoph Egger
Hi all! Steven Chamberlain writes: > On 27/04/12 13:31, Matthias Klose wrote: >> I'm now planning to default to GCC 4.7 for amd64 and i386. Should kfreebsd >> and >> the hurd do change at the same time, or should these stay with 4.6? > > As long as amd64 and i386 switch too, then I think it wou

Re: defaulting to GCC-4.7 for kfreebsd

2012-05-05 Thread Steven Chamberlain
On 27/04/12 13:31, Matthias Klose wrote: > I'm now planning to default to GCC 4.7 for amd64 and i386. Should kfreebsd > and > the hurd do change at the same time, or should these stay with 4.6? Hi Matthias, As long as amd64 and i386 switch too, then I think it would be okay for us to do the sam

Re: defaulting to GCC-4.7 for kfreebsd and the hurd?

2012-04-27 Thread Matthias Klose
On 27.04.2012 15:03, Steven Chamberlain wrote: > On 27/04/12 13:31, Matthias Klose wrote: >> I'm now planning to default to GCC 4.7 for amd64 and i386. Should kfreebsd >> and >> the hurd do change at the same time, or should these stay with 4.6? > > In case it is relevant to this decision: > >

Re: defaulting to GCC-4.7 for kfreebsd and the hurd?

2012-04-27 Thread Samuel Thibault
Matthias Klose, le Fri 27 Apr 2012 15:07:12 +0200, a écrit : > On 27.04.2012 14:44, Samuel Thibault wrote: > > Matthias Klose, le Fri 27 Apr 2012 14:31:16 +0200, a écrit : > >> I'm now planning to default to GCC 4.7 for amd64 and i386. Should > >> kfreebsd and > >> the hurd do change at the same

Re: defaulting to GCC-4.7 for kfreebsd and the hurd?

2012-04-27 Thread Matthias Klose
On 27.04.2012 14:44, Samuel Thibault wrote: > Matthias Klose, le Fri 27 Apr 2012 14:31:16 +0200, a écrit : >> I'm now planning to default to GCC 4.7 for amd64 and i386. Should kfreebsd >> and >> the hurd do change at the same time, or should these stay with 4.6? > > I have actually already commi

Re: defaulting to GCC-4.7 for kfreebsd and the hurd?

2012-04-27 Thread Steven Chamberlain
On 27/04/12 13:31, Matthias Klose wrote: > I'm now planning to default to GCC 4.7 for amd64 and i386. Should kfreebsd > and > the hurd do change at the same time, or should these stay with 4.6? In case it is relevant to this decision: gcc-4.6 has been failing to build on kfreebsd-* since the en

Re: defaulting to GCC-4.7 for kfreebsd and the hurd?

2012-04-27 Thread Samuel Thibault
Matthias Klose, le Fri 27 Apr 2012 14:31:16 +0200, a écrit : > I'm now planning to default to GCC 4.7 for amd64 and i386. Should kfreebsd > and > the hurd do change at the same time, or should these stay with 4.6? I have actually already commited the switch to gcc4.7 for the hurd package. I bel

defaulting to GCC-4.7 for kfreebsd and the hurd?

2012-04-27 Thread Matthias Klose
Hi, I'm now planning to default to GCC 4.7 for amd64 and i386. Should kfreebsd and the hurd do change at the same time, or should these stay with 4.6? Matthias -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.