Re: defaulting to GCC-4.7 for kfreebsd and the hurd?
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 believe it is ok to switch to 4.7 in general. Samuel -- To UNSUBSCRIBE, email to debian-hurd-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120427124454.gw19...@type.famille.thibault.fr
Re: defaulting to GCC-4.7 for kfreebsd and the hurd?
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 commited the switch to gcc4.7 for the hurd package. I believe it is ok to switch to 4.7 in general. are you committed to forward and fix issues for all other archs? I can't say that from myself. I'll chat with the ARM porters, but didn't plan to do so for other ports. Matthias -- To UNSUBSCRIBE, email to debian-hurd-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f9a9a00.4060...@debian.org
Re: defaulting to GCC-4.7 for kfreebsd and the hurd?
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 time, or should these stay with 4.6? I have actually already commited the switch to gcc4.7 for the hurd package. I believe it is ok to switch to 4.7 in general. are you committed to forward and fix issues for all other archs? I can't say that from myself. I was just talking for the hurd-i386 port. My general above was just meaning packages in general on hurd-i386. Samuel -- To UNSUBSCRIBE, email to debian-hurd-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120427131044.gx19...@type.famille.thibault.fr
Re: defaulting to GCC-4.7 for kfreebsd and the hurd?
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 enable-gnu-unique-object configure option was enabled (from 4.6.3-2) : Error: symbol type gnu_unique_object is supported only by GNU targets Whereas gcc-4.7 has built okay since that option was disabled on kfreebsd-* and hurd-i386 (from 4.7.0~rc2-1). Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-hurd-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f9a9930.7040...@pyro.eu.org
Re: defaulting to GCC-4.7 for kfreebsd and the hurd?
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: gcc-4.6 has been failing to build on kfreebsd-* since the enable-gnu-unique-object configure option was enabled (from 4.6.3-2) : Error: symbol type gnu_unique_object is supported only by GNU targets Whereas gcc-4.7 has built okay since that option was disabled on kfreebsd-* and hurd-i386 (from 4.7.0~rc2-1). thanks, fixed in the vcs. -- To UNSUBSCRIBE, email to debian-hurd-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f9ab953.7090...@debian.org
