From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "Matthew S. McClintock" <mattsm@arlut.utexas.edu>
Cc: Christian <evil@g-house.de>,
linuxppc-dev list <linuxppc-dev@lists.linuxppc.org>
Subject: Re: cpu_setup_6xx.S:19:22: ppc_defs.h: No such file or directory
Date: Thu, 15 Jan 2004 12:54:54 +1100 [thread overview]
Message-ID: <1074131648.5123.48.camel@gaston> (raw)
In-Reply-To: <1074101770.23751.6.camel@chuck.arlut.utexas.edu>
On Thu, 2004-01-15 at 04:36, Matthew S. McClintock wrote:
> The file does not even get created. I can copy it over from another
> linux tree that worked before and put it in the current linux tree and
> everything works. It always craps out on that one file, would that still
> indicate some sort of hardware problem?
That is WRONG
That file has to be created as part of the kernel build process, the
offsets in there are different depending on various things like
kernel version, compiler version, kernel config options, just copying
it from another kernel may result into interesting random kernel
behaviour...
If it's not created for you, then something is wrong in your build
process, or you source tree contains crap or whatever. It definitely
works fine with the upstream sources.
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-01-15 1:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-13 20:29 cpu_setup_6xx.S:19:22: ppc_defs.h: No such file or directory Matthew S. McClintock
2004-01-14 0:16 ` Christian
2004-01-14 17:36 ` Matthew S. McClintock
2004-01-15 1:54 ` Benjamin Herrenschmidt [this message]
2004-01-15 17:16 ` Matthew S. McClintock
2004-01-15 19:25 ` Hollis Blanchard
2004-01-15 19:54 ` linas
2004-01-15 20:20 ` Matthew S. McClintock
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=1074131648.5123.48.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=evil@g-house.de \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=mattsm@arlut.utexas.edu \
/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;
as well as URLs for NNTP newsgroup(s).