public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Distributions using gcc 3.2 or later
Date: Wed, 15 Jan 2003 18:15:43 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590709805684@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709805681@msgid-missing>

>>>>> On Wed, 15 Jan 2003 09:43:39 -0800, Perry Wagle <wagle@wirex.com> said:

  Perry> Intel has graciously short-term-loaned me a IA64.  Before
  Perry> Christmas break, I poked around, and all the Linux
  Perry> distributions for IA64 seemed GCC 2.96 based, except for the
  Perry> Redhat rawhide distribution.  But, testing with alpha-test
  Perry> distributions makes me nervous that I would be testing much
  Perry> more than my changes.  Now that my compiler modification is
  Perry> starting to work, I thought I'd poke my head out and ask what
  Perry> distribution I should use that would expect GCC 3.2 or later?

Debian/unstable also uses gcc-3.2.  As you'd expect, this version
isn't as solid as Debian/stable, but it's definitely usable (I'm
running it on my McKinley workstation at work).  The main thing is
that stuff sometimes breaks temporarily (e.g., it seems the X server
broke a couple of days ago), but usually those can be fixed by
downgrading to the "stable" version of the package.

	--david


  parent reply	other threads:[~2003-01-15 18:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-15 17:43 [Linux-ia64] Distributions using gcc 3.2 or later Perry Wagle
2003-01-15 18:05 ` Martin Schimmer
2003-01-15 18:12 ` Randolph Chung
2003-01-15 18:15 ` David Mosberger [this message]
2003-01-15 18:26 ` Matthew Wilcox
2003-01-15 19:02 ` Gwenole Beauchesne
2003-01-15 19:12 ` n0ano
2003-01-15 19:35 ` Matthew Wilcox
2003-01-15 20:14 ` Wichmann, Mats D
2003-01-15 21:44 ` Grant Grundler

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=marc-linux-ia64-105590709805684@msgid-missing \
    --to=davidm@napali.hpl.hp.com \
    --cc=linux-ia64@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox