linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Matthew S. McClintock" <mattsm@arlut.utexas.edu>
To: Christian <evil@g-house.de>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: cpu_setup_6xx.S:19:22: ppc_defs.h: No such file or directory
Date: Wed, 14 Jan 2004 11:36:11 -0600	[thread overview]
Message-ID: <1074101770.23751.6.camel@chuck.arlut.utexas.edu> (raw)
In-Reply-To: <40048A4B.1040400@g-house.de>


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?

Matthew

On Tue, 2004-01-13 at 18:16, Christian wrote:
> Matthew S. McClintock wrote:
> | 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?
>
> filesystem / memory corruption, even slightly overclocking the cpu, too
> old / too new compiler or binutils.
> when the error occurs, can you actually stat ppc_defs.h ?
>
> Christian.
> - --
> BOFH excuse #200:
>
> The monitor needs another box of pixels.
>
--
Matthew S. McClintock <mattsm@arlut.utexas.edu>


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2004-01-14 17:36 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 [this message]
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=1074101770.23751.6.camel@chuck.arlut.utexas.edu \
    --to=mattsm@arlut.utexas.edu \
    --cc=evil@g-house.de \
    --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).