From: Hollis Blanchard <hollisb@us•ibm.com>
To: "Matthew S. McClintock" <mattsm@arlut•utexas.edu>,
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 19:25:23 +0000 [thread overview]
Message-ID: <200401151925.24746.hollisb@us.ibm.com> (raw)
In-Reply-To: <1074186989.23751.9.camel@chuck.arlut.utexas.edu>
On Thursday 15 January 2004 17:16, Matthew S. McClintock wrote:
> On Wed, 2004-01-14 at 19:54, Benjamin Herrenschmidt wrote:
> >
> > 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?
Just a guess, but I don't think 2.4 trees work perfectly with parallel builds
(make -jN). It could be that one build needs ppc_defs.h before the other has
created it yet.
--
Hollis Blanchard
IBM Linux Technology Center
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-01-15 19:25 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
2004-01-15 19:25 ` Hollis Blanchard [this message]
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=200401151925.24746.hollisb@us.ibm.com \
--to=hollisb@us$(echo .)ibm.com \
--cc=benh@kernel$(echo .)crashing.org \
--cc=evil@g-house$(echo .)de \
--cc=linuxppc-dev@lists$(echo .)linuxppc.org \
--cc=mattsm@arlut$(echo .)utexas.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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