Re: GCC-4.5 as the default for (at least some) architectures

2011-04-26 Thread Matthias Klose

On 04/17/2011 09:33 PM, Adam D. Barratt wrote:

On Wed, 2011-03-02 at 02:34 +0100, Matthias Klose wrote:

I'll make gcc-4.5 the default for (at least some) architectures within the next
two weeks before more transitions start.  GCC-4.5 is already used as the default
compiler for almost any other distribution, so there shouldn't be many surprises
on at least the common architectures.  About 50% of the build failures exposed
by GCC-4.5 are fixed [1].  I didn't see issues on amd64 and i386, armel
(although optimized for a different processor) and powerpc (some object files
linked into shared libs had to be built as pic).


It looks like kfreebsd-* also made the switch and there's been a request
to switch for mips and mipsel.

Looking through the bug list for src:gcc-4.5, none of the open issues
seem to be specific to the remaining release architectures which haven't
switched yet - i.e. ia64, s390 and sparc.  Are you aware of any issues
which would preclude switching the default on those architectures?  Has
there been any discussion with the port maintainers regarding switching?


At this point, pretty well after the GCC 4.6.0 release, I would like to avoid 
switching more architectures to 4.5, but rather get rid of GCC 4.5 to reduce 
maintenance efforts on the debian-gcc side, even before the multiarch changes go 
into unstable. I'll make GCC 4.6 the default after the release of GCC 4.5.3, 
expected later this week, at least on amd64, armel, i386 and powerpc.  GCC 4.6 
apparently will be used for the next Fedora and OpenSuse releases, and a test 
rebuild of Ubuntu natty doesn't look too bad (mostly adding new easily fixable 
C++ build failures).  A test rebuild of the unstable archive is still 
outstanding, but these build failures will have to be fixed anyway.   From my 
point of view it's important to expose GCC 4.6 early in the release cycle to fix 
issues like #617628 (which are issues in the packages itself) now.


With GCC 4.6 comes one soname change, bumping the libobjc version from 2 to 3, 
which is not easily detachable from the GCC version change. However this change 
only affects GNUstep, which can be dealt with NMU's, or migration to a new 
GNUstep version.


It's unlikely that GCC 4.5 will be released with wheezy, as the Debian Ada and D 
maintainers are already working on GCC 4.6 support.


  Matthias


--
To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4db6dea5.5010...@debian.org



Re: GCC-4.5 as the default for (at least some) architectures

2011-04-26 Thread Konstantinos Margaritis
On 26 April 2011 18:03, Matthias Klose d...@debian.org wrote:
 I'll make GCC 4.6 the default after the release of
 GCC 4.5.3, expected later this week, at least on amd64, armel, i386 and
 powerpc.

Could you include armhf in the list as well?

Thanks

Konstantinos


-- 
To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/BANLkTimddKkTaiy1fyka6zMOj0o1YzBS=a...@mail.gmail.com



Re: GCC-4.5 as the default for (at least some) architectures

2011-04-26 Thread Matthias Klose

On 04/26/2011 05:31 PM, Konstantinos Margaritis wrote:

On 26 April 2011 18:03, Matthias Klosed...@debian.org  wrote:

I'll make GCC 4.6 the default after the release of
GCC 4.5.3, expected later this week, at least on amd64, armel, i386 and
powerpc.


Could you include armhf in the list as well?


yes, forgot about that.  with GCC 4.6, armhf is built again from the 4.6 fsf 
branch, and lets us drop the GCC 4.5 Linaro variant.


  Matthias


--
To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4db6eb11.2080...@debian.org



Re: GCC-4.5 as the default for (at least some) architectures

2011-04-26 Thread Mathieu Malaterre
On Tue, Apr 26, 2011 at 5:31 PM, Konstantinos Margaritis
mar...@genesi-usa.com wrote:
 On 26 April 2011 18:03, Matthias Klose d...@debian.org wrote:
 I'll make GCC 4.6 the default after the release of
 GCC 4.5.3, expected later this week, at least on amd64, armel, i386 and
 powerpc.

 Could you include armhf in the list as well?

I am also getting an ICE with g++ 4.5 on mips too on one of my C++ package:

https://buildd.debian.org/status/package.php?p=vxl

but since there is no log I cannot confirm this is the same ICE as on i386/armel

thanks,
-- 
Mathieu


-- 
To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/banlktimr8sshy4vvasvzoxk4gyj1pb9...@mail.gmail.com



Need Help on RHEL Cluster for System z

2011-04-26 Thread Shrirang Kulkarni
Hi All,

RHEL Cluster supported on system z ?
RHEL Cluster supported on native mode (LPAR Mode) on System z?

Could you please provide me some document links which can help me to
understand the same.


Thanks  Regards
Shrirang Kulkarni


Re: GCC-4.5 as the default for (at least some) architectures

2011-04-26 Thread Aurelien Jarno
On Tue, Apr 26, 2011 at 05:03:01PM +0200, Matthias Klose wrote:
 On 04/17/2011 09:33 PM, Adam D. Barratt wrote:
 On Wed, 2011-03-02 at 02:34 +0100, Matthias Klose wrote:
 I'll make gcc-4.5 the default for (at least some) architectures within the 
 next
 two weeks before more transitions start.  GCC-4.5 is already used as the 
 default
 compiler for almost any other distribution, so there shouldn't be many 
 surprises
 on at least the common architectures.  About 50% of the build failures 
 exposed
 by GCC-4.5 are fixed [1].  I didn't see issues on amd64 and i386, armel
 (although optimized for a different processor) and powerpc (some object 
 files
 linked into shared libs had to be built as pic).
 
 It looks like kfreebsd-* also made the switch and there's been a request
 to switch for mips and mipsel.
 
 Looking through the bug list for src:gcc-4.5, none of the open issues
 seem to be specific to the remaining release architectures which haven't
 switched yet - i.e. ia64, s390 and sparc.  Are you aware of any issues
 which would preclude switching the default on those architectures?  Has
 there been any discussion with the port maintainers regarding switching?
 
 At this point, pretty well after the GCC 4.6.0 release, I would like
 to avoid switching more architectures to 4.5, but rather get rid of
 GCC 4.5 to reduce maintenance efforts on the debian-gcc side, even
 before the multiarch changes go into unstable. I'll make GCC 4.6 the
 default after the release of GCC 4.5.3, expected later this week, at
 least on amd64, armel, i386 and powerpc.  GCC 4.6 apparently will be

If you do the switch, please also add mips and mipsel, that would avoid
you to have to complain in two weeks that these architectures have not
yet been switched.

-- 
Aurelien Jarno  GPG: 1024D/F1BCDB73
aurel...@aurel32.net http://www.aurel32.net


-- 
To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110426185104.gb29...@hall.aurel32.net



Re: GCC-4.5 as the default for (at least some) architectures

2011-04-26 Thread Samuel Thibault
Kurt Roeckx, le Tue 26 Apr 2011 21:28:57 +0200, a écrit :
 Is there a reason not to switch the remaining (release) arches
 (ia64, kfreebsd-*, sparc, s390)?  Maybe hurd-i386 too?

There's no real reason to defer hurd-i386, as it's basically like i386,
and the key packages (glibc/hurd/gnumach) already use a fixed version
and can be handled independently.

Samuel


-- 
To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110426204147.gs4...@const.famille.thibault.fr