From: David Woodhouse <dwmw2@infradead.org>
To: Jeff Galloway <jeff.galloway@rundog.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.3 Compile Errors - Power Mac
Date: Fri, 20 Apr 2001 08:57:18 +0100 [thread overview]
Message-ID: <13993.987753438@redhat.com> (raw)
In-Reply-To: <B7054D66.424B%jeff.galloway@rundog.com>
In-Reply-To: <B7054D66.424B%jeff.galloway@rundog.com>
jeff.galloway@rundog.com said:
> However, I don't think that wishing the world would avoid these
> dominant (and very useful) formats is a realistic expectation. It is
> certainly not "common sense" to assume as such.
Of course it's not a realistic expectation. There are times when it's a pain
to have to be safe - people will always break the rules when they're in a
hurry and the document to be sent is already in an unsafe format. But taking
plain text with absolutely no formatting, in fact text which is
_degenerated_ by word wrapping &c, and gratuitously putting it in a Word
document is just _so_ unnecessary that I assumed it had to be a troll.
> fork.c: In function copy_mm¹:
Given what this output's been through - I'll assume it's corrupted in
transit, shall I?
The kind of error you're seeing is often caused by a mismatch between
compiler and kernel. As Alan suggests, you should make sure you're using a
PPC-specific tree because it's not up to date in the stock 2.4.3. And make
sure you're using the recommended versions of compiler and binutils. Other
than that, I'm afraid I don't know.
--
dwmw2
next prev parent reply other threads:[~2001-04-20 7:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <B703E416.421B%jeff.galloway@rundog.com>
2001-04-19 20:19 ` FW: Linux 2.4.3 Compile Errors - Power Mac Jeff Galloway
2001-04-19 21:15 ` tom_gall
2001-04-20 6:24 ` Jeff Galloway
2001-04-20 10:21 ` Paul Mackerras
2001-04-20 13:34 ` tom_gall
2001-04-19 21:34 ` FW: " David Woodhouse
2001-04-20 6:20 ` Jeff Galloway
2001-04-20 7:57 ` David Woodhouse [this message]
2001-04-20 11:38 ` Jeff Galloway
2001-04-19 21:37 ` FW: " Alan Cox
2001-04-20 7:18 ` Paul Mackerras
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=13993.987753438@redhat.com \
--to=dwmw2@infradead.org \
--cc=jeff.galloway@rundog.com \
--cc=linux-kernel@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 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.