All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jan Beulich" <jbeulich@novell.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com
Subject: c/s 14420 (gcc 3.4+ required)
Date: Mon, 19 Mar 2007 09:35:24 +0000	[thread overview]
Message-ID: <45FE676C.76E4.0078.0@novell.com> (raw)

Keir,

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

             reply	other threads:[~2007-03-19  9:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-19  9:35 Jan Beulich [this message]
2007-03-19  9:51 ` c/s 14420 (gcc 3.4+ required) Keir Fraser
2007-03-19 12:36   ` Jan Beulich
2007-03-19 12:44     ` Jan Beulich
2007-03-19 13:22       ` Keir Fraser

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=45FE676C.76E4.0078.0@novell.com \
    --to=jbeulich@novell.com \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.