From: Sam Ravnborg <sam@ravnborg.org>
To: Keith Owens <kaos@ocs.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.15 make fails with multiple targets in parallel
Date: Wed, 11 Jan 2006 17:38:46 +0100 [thread overview]
Message-ID: <20060111163846.GA16112@mars.ravnborg.org> (raw)
In-Reply-To: <13394.1136968751@kao2.melbourne.sgi.com>
On Wed, Jan 11, 2006 at 07:39:11PM +1100, Keith Owens wrote:
> Running make on the kernel tree with multiple targets on the command
> line and in parallel mode gets errors. The prepare targets are run
> several times, once for each target on the command line. Sometimes the
> result is sensible, sometimes the prepare commands overwrite each other
> with either garbage or missing files.
>
> make -j12 compressed modules vmlinux
> Using /foo/linux as source for kernel
> Using /foo/linux as source for kernel
> Using /foo/linux as source for kernel
> GEN /foo/obj/Makefile
I've tested it locally. It happens only when using 'make O=...'
or in your case with KBUILT_OUTPUT set to a value.
I will try to take a look during the weekend but if you have any inputs
that would be appreciated.
> Is this where we mention http://www.google.com/search?q=cache:HwuX7YF2uBIJ:aegis.sourceforge.net/auug97.pdf&hl=en ?
>
The bug you see is due to the way the "make O=..." support is done - not
due to use of recursive makefiles in the kernel.
That being said I hope one day to write a tool that can take all
the kbuild files used as part of the kernel build and create one
big Makefile - sounds familiar?
The current syntax is rather easy to parse up so no syntax changes in
the kbuild (makefile) files needed.
But several other topics are higher on the todo list for now.
Sam
next prev parent reply other threads:[~2006-01-11 16:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-11 8:39 Keith Owens
2006-01-11 16:38 ` Sam Ravnborg [this message]
2006-01-15 17:04 ` Sam Ravnborg
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=20060111163846.GA16112@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome