[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#260309: marked as done (gcc-defaults: Please make gcc-3.4 the default on amd64)



Your message dated Sun, 22 May 2005 13:43:02 +0200
with message-id <874qcvo5a1.fsf@informatik.uni-tuebingen.de>
and subject line sarge will be gcc-3.3
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--------------------------------------
Received: (at submit) by bugs.debian.org; 19 Jul 2004 21:00:41 +0000
>From aj@andaco.de Mon Jul 19 14:00:41 2004
Return-path: <aj@andaco.de>
Received: from c158090.adsl.hansenet.de (localhost) [213.39.158.90] 
	by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
	id 1BmfFY-0002Ku-00; Mon, 19 Jul 2004 14:00:41 -0700
Received: from aj by localhost with local (Exim 4.34)
	id 1BmfFS-0004E8-EZ; Mon, 19 Jul 2004 23:00:34 +0200
To: Debian Bug Tracking System <submit@bugs.debian.org>
Cc: debian-amd64@lists.debian.org
From: Andreas Jochens <aj@andaco.de>
Subject: gcc-defaults: Please make gcc-3.4 the default on amd64
Message-Id: <E1BmfFS-0004E8-EZ@localhost>
Date: Mon, 19 Jul 2004 23:00:34 +0200
Delivered-To: submit@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 
	(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
	autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 

Package: gcc-defaults
Severity: wishlist

Please make gcc-3.4 the default on amd64. It has much better support for
the amd64 architecture and also much better performance on amd64 
than gcc-3.3. 

Moreover, some packages cannot be compiled on amd64 at all 
with gcc-3.3 (e.g. gnustep-base, boost, etc.) and other packages
just segfault amd64 when compiled with gcc-3.3 (e.g. mozilla).

I recompiled the whole archive (~8500 packages including 
main, contrib, non-free and experimental) with gcc-3.4 as the default
on amd64 to check for possible problems. This took about 9 days on
a Dual-2GHz-Opteron machine.

There are a few packages which need minor patches because gcc-3.4 
is somewhat stricter than gcc-3.3.
gcc-3.4 refuses to compile some constructs which do not conform to the 
C or C++-standards but which were tolerated by earlier gcc versions.

I filed more than 150 bug reports with patches for packages which did not 
compile with gcc-3.4 and I will file some more in the next few days.
Many of those patches have already been applied by the respective 
maintainers (thanks!). Those issues will have to be sorted out anyway
because sooner or later the other architectures will switch to gcc-3.4
(or to a later version).

I used the gcc-3.4.1 package from http://people.debian.org/~doko/gcc-3.4
and something like the attached patch to 'gcc-defaults' for my tests.
However, I am not sure if this patch is entirely correct.

Please note the following lines of the patch:

-ifeq ($(DEB_HOST_GNU_TYPE),amd64-linux)
+ifeq ($(DEB_HOST_GNU_TYPE),x86_64-linux)

i.e. 'amd64-linux' has to be replaced with 'x86_64-linux'. Otherwise
the condition will always be false and the amd64 specific settings
(like excluding 'chill' from packages) will be ignored. This is a bug in
the current version of 'gcc-defaults'.

Thank you for your help with the amd64 port.

Regards
Andreas Jochens

diff -urN ../tmp-orig/gcc-defaults-1.17/debian/rules ./debian/rules
--- ../tmp-orig/gcc-defaults-1.17/debian/rules	2004-07-13 07:43:06.000000000 +0200
+++ ./debian/rules	2004-07-18 10:48:36.606020682 +0200
@@ -31,6 +31,8 @@
 REL_NO_333	:= $(shell expr $(REL_NO) - 12)
 # gcc-defaults 1.16 is the first version with 3.3.4 support.
 REL_NO_334	:= $(shell expr $(REL_NO) - 15)
+# gcc-defaults 1.17 is the first version with 3.4 support.
+REL_NO_34	:= $(shell expr $(REL_NO) - 16)
 
 #
 GPC_DATE	:= 20040516
@@ -42,7 +44,9 @@
 REQV_30		:= (>= 1:3.0.4-12)
 REQV_32		:= (>= 1:3.2.3-1)
 REQV_33		:= (>= 1:3.3.4-1)
+REQV_34		:= (>= 3.4.1-1)
 REQV_GPC_33	:= (>= 1:3.3.4.$(GPC_DATE)-1)
+REQV_GPC_34	:= (>= 3.4.1.$(GPC_DATE)-1)
 
 # architecture dependent variables
 DEB_HOST_ARCH		:= $(shell dpkg-architecture -qDEB_HOST_ARCH)
@@ -81,8 +85,29 @@
 ifeq ($(DEB_HOST_GNU_TYPE),alpha-linux)
 endif
 
-ifeq ($(DEB_HOST_GNU_TYPE),amd64-linux)
+ifeq ($(DEB_HOST_GNU_TYPE),x86_64-linux)
     packages	:= c++ fortran java objc pascal
+
+    CV_GPC	:= 3.4.1-$(REL_NO_34)
+
+    CV_CPP	:= 3.4.1-$(REL_NO_34)
+    CV_GCC	:= 3.4.1-$(REL_NO_34)
+    CV_GPP	:= 3.4.1-$(REL_NO_34)
+    CV_GOBJC	:= 3.4.1-$(REL_NO_34)
+    CV_G77	:= 3.4.1-$(REL_NO_34)
+    CV_GCJ	:= 3.4.1-$(REL_NO_34)
+    CV_GIJ	:= 3.4.1-$(REL_NO_34)
+
+    REQV_GPC	= $(REQV_34)
+
+    REQV_CPP	= $(REQV_34)
+    REQV_GCC	= $(REQV_34)
+    REQV_GPP	= $(REQV_34)
+    REQV_GOBJC	= $(REQV_34)
+    REQV_G77	= $(REQV_34)
+    REQV_GCJ	= $(REQV_34)
+    REQV_GIJ	= $(REQV_34)
+    REQV_GPC	= $(REQV_GPC_34)
 endif
 
 ifeq ($(DEB_HOST_GNU_TYPE),arm-linux)

---------------------------------------
Received: (at 260309-done) by bugs.debian.org; 22 May 2005 11:43:40 +0000
>From brederlo@informatik.uni-tuebingen.de Sun May 22 04:43:40 2005
Return-path: <brederlo@informatik.uni-tuebingen.de>
Received: from mx4.informatik.uni-tuebingen.de [134.2.12.29] 
	by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
	id 1DZors-00062W-00; Sun, 22 May 2005 04:43:40 -0700
Received: from localhost (loopback [127.0.0.1])
	by mx4.informatik.uni-tuebingen.de (Postfix) with ESMTP id 2F74314C0
	for <260309-done@bugs.debian.org>; Sun, 22 May 2005 13:43:09 +0200 (DFT)
Received: from mx4.informatik.uni-tuebingen.de ([127.0.0.1])
 by localhost (mx4 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
 id 19628-05 for <260309-done@bugs.debian.org>;
 Sun, 22 May 2005 13:43:08 +0200 (DFT)
Received: from localhost.localdomain (semeai.Informatik.Uni-Tuebingen.De [134.2.15.66])
	by mx4.informatik.uni-tuebingen.de (Postfix) with ESMTP id 98EB414CB
	for <260309-done@bugs.debian.org>; Sun, 22 May 2005 13:43:08 +0200 (DFT)
Received: from mrvn by localhost.localdomain with local (Exim 4.50)
	id 1DZorG-0005DR-Kp
	for 260309-done@bugs.debian.org; Sun, 22 May 2005 13:43:02 +0200
To: 260309-done@bugs.debian.org
Subject: sarge will be gcc-3.3
From: Goswin von Brederlow <brederlo@informatik.uni-tuebingen.de>
Date: Sun, 22 May 2005 13:43:02 +0200
Message-ID: <874qcvo5a1.fsf@informatik.uni-tuebingen.de>
User-Agent: Gnus/5.1006 (Gnus v5.10.6) XEmacs/21.4 (Jumbo Shrimp, linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Delivered-To: 260309-done@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
	(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-3.0 required=4.0 tests=BAYES_00 autolearn=no 
	version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 

Since sarge will be releasing with gcc-3.3 and that works nicely I'm
closing this bug.

MfG
        Goswin



Reply to: