From: "Matthew S. McClintock" <mattsm@arlut.utexas.edu>
To: linuxppc-dev@lists.linuxppc.org
Subject: cpu_setup_6xx.S:19:22: ppc_defs.h: No such file or directory
Date: Tue, 13 Jan 2004 14:29:27 -0600 [thread overview]
Message-ID: <1074025766.23751.2.camel@chuck.arlut.utexas.edu> (raw)
I have a problem with the kernel build. It seems completely random in
occurrence, however I'm sure something has to be causing it.The error is
as follows:
cpu_setup_6xx.S:19:22: ppc_defs.h: No such file or directory
And the kernel build can not complete. Sometimes running a make dep and
continuing again with a make uImage will correct the problem but not
always. Does anyone have any idea why sometimes this file does not get
built correctly and other times it does?
--
Matthew S. McClintock <mattsm@arlut.utexas.edu>
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2004-01-13 20:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-13 20:29 Matthew S. McClintock [this message]
2004-01-14 0:16 ` cpu_setup_6xx.S:19:22: ppc_defs.h: No such file or directory Christian
2004-01-14 17:36 ` Matthew S. McClintock
2004-01-15 1:54 ` Benjamin Herrenschmidt
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=1074025766.23751.2.camel@chuck.arlut.utexas.edu \
--to=mattsm@arlut.utexas.edu \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).