This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] c/s 14420 (gcc 3.4+ required)

To: "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>
Subject: [Xen-devel] c/s 14420 (gcc 3.4+ required)
From: "Jan Beulich" <jbeulich@xxxxxxxxxx>
Date: Mon, 19 Mar 2007 09:35:24 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 19 Mar 2007 02:34:02 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

what are the exact issues that required this change? SLES9 being based on
gcc 3.3.3 makes it pretty undesirable for me/us to have this kind of a
requirement. Despite me certainly being able to compile newer gcc-s (I
actually have these around all the time), the mere fact to remember to pass
a CC= each time I want to build Xen is going to make this cumbersome.

Hence I'd like to understand the underlying issue(s), see whether they apply
to the 3.3.x versions we have in use (aside of SLES9 I also continue to have
one 9.0 system around that I use for regular building and testing).

Thanks, Jan

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>