All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Matthew S. McClintock" <mattsm@arlut.utexas.edu>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
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 11:16:29 -0600	[thread overview]
Message-ID: <1074186989.23751.9.camel@chuck.arlut.utexas.edu> (raw)
In-Reply-To: <1074131648.5123.48.camel@gaston>


On Wed, 2004-01-14 at 19:54, Benjamin Herrenschmidt wrote:

> 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.
>

Well it is from the same kernel tree and same config, I just copy it
because sometimes the current tree does not make that file correctly. I
don't know what else to do, does anyone have any idea why my tree is not
building this file every time correctly in the first place?

Thanks,
Matthew

--
Matthew S. McClintock <mattsm@arlut.utexas.edu>


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

  reply	other threads:[~2004-01-15 17:16 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
2004-01-15 17:16       ` Matthew S. McClintock [this message]
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=1074186989.23751.9.camel@chuck.arlut.utexas.edu \
    --to=mattsm@arlut.utexas.edu \
    --cc=benh@kernel.crashing.org \
    --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 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.