All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Matthew S. McClintock" <mattsm@arlut.utexas.edu>
To: Hollis Blanchard <hollisb@us.ibm.com>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	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 14:20:37 -0600	[thread overview]
Message-ID: <1074198036.23751.17.camel@chuck.arlut.utexas.edu> (raw)
In-Reply-To: <200401151925.24746.hollisb@us.ibm.com>


On Thu, 2004-01-15 at 13:25, Hollis Blanchard wrote:
> 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.

This appears to be the problem. I am compiling this kernel on a dual cpu
machine and I suppose make takes the liberty of running in -j2 mode.
Running make with the -j1 option fixes the problem.

Thanks everyone for the help

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


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

      parent reply	other threads:[~2004-01-15 20:20 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
2004-01-15 19:54           ` linas
2004-01-15 20:20           ` Matthew S. McClintock [this message]

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=1074198036.23751.17.camel@chuck.arlut.utexas.edu \
    --to=mattsm@arlut.utexas.edu \
    --cc=benh@kernel.crashing.org \
    --cc=evil@g-house.de \
    --cc=hollisb@us.ibm.com \
    --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.