From: Dave Jones <davej@codemonkey.org.uk>
To: William Knop <w_knop@hotmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.50-ac1 mpparse -> gcc 3.0.1 segfault
Date: Mon, 9 Dec 2002 11:14:37 +0000 [thread overview]
Message-ID: <20021209111437.GA31468@suse.de> (raw)
In-Reply-To: <F32fiSBtAM9r5h1inen000214bb@hotmail.com>
On Mon, Dec 09, 2002 at 01:55:08AM -0500, William Knop wrote:
> Hello,
> The machine I'm working on has SMP enabled (dual 2GHZ P4 Xeon), although
> I've tried it on a different box with dual P3s and it's still a no go. It
> didn't happen on 2.5.50-vanilla, so far as I can tell (it had other compile
> errors wrt intermezzo, but it got past mpparse). Attached at the bottom is
> the make output. Any info on similar occurrences or a fix would be
> appreciated.
3.0.1 is now quite old, and has a number of issues. Try a more recent gcc,
and if the problem is repeatable, file a bug with the gcc folks, as the
output told you to.
Dave
--
| Dave Jones. http://www.codemonkey.org.uk
next prev parent reply other threads:[~2002-12-09 11:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-09 6:55 2.5.50-ac1 mpparse -> gcc 3.0.1 segfault William Knop
2002-12-09 11:14 ` Dave Jones [this message]
2002-12-09 15:00 ` Alan Cox
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=20021209111437.GA31468@suse.de \
--to=davej@codemonkey.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=w_knop@hotmail.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.