public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: linux-ia64@vger.kernel.org
Subject: Re: gcc problems
Date: Fri, 06 Feb 2004 08:43:46 +0000	[thread overview]
Message-ID: <20040206004346.225040c0.akpm@osdl.org> (raw)
In-Reply-To: <20040206000058.7e928d80.akpm@osdl.org>

Ian Wienand <ianw@gelato.unsw.edu.au> wrote:
>
> On Fri, Feb 06, 2004 at 12:00:58AM -0800, Andrew Morton wrote:
> > gcc-3.3.2/ia64 is falling over here with my current tree so I'm trying to
> > build gcc-3.4 from current gcc CVS.
> 
> That probably shouldn't be happening... It's what we use all the time.
> I assume gcc is segfaulting?

I rebuilt and it went away.  It could have been a 2.6 kernel bug ;)

> > Is there some trick to this?  And what is the preferred gcc version for
> > ia64 kernels?
> 
> Well I don't know exactly about that CVS gcc problem, but something
> that may be useful if you use Debian is that there is a little known
> 'gcc-snapshot' package that is usually quite up to date and saves you
> having to build yourself.  See the README.Debian for a sample wrapper.
> 

I would prefer to build gcc direct from the gcc team, really, thanks.


  parent reply	other threads:[~2004-02-06  8:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-06  8:00 gcc problems Andrew Morton
2004-02-06  8:37 ` Ian Wienand
2004-02-06  8:43 ` Andrew Morton [this message]
2004-02-06  9:49 ` Jim Wilson
2004-02-06 11:46 ` Andreas Schwab
2004-02-06 16:30 ` Andrew Morton
2004-02-06 16:50 ` Dan Kegel
2004-02-06 17:34 ` Wichmann, Mats D
2004-02-07  2:05 ` Jim Wilson
2004-02-07  5:49 ` Andrew Morton
2004-02-10  7:37 ` David Mosberger

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=20040206004346.225040c0.akpm@osdl.org \
    --to=akpm@osdl.org \
    --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