public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Jim Davis <jim.epost@gmail.com>,
	Randy Dunlap <rdunlap@infradead.org>,
	Thomas Meyer <thomas@m3y3r.de>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	linux-kbuild <linux-kbuild@vger.kernel.org>
Subject: Re: make clean all broken with -j? + question regarding modpost
Date: Sat, 12 Aug 2017 10:06:55 +0200	[thread overview]
Message-ID: <20170812080655.GA19083@ravnborg.org> (raw)
In-Reply-To: <CAK7LNAS3anskx8+9aWQrg+PKkr4L4AdsdWaha=_uMU5VjKpg5A@mail.gmail.com>

Hi Masahiro
> 
> Kbuild does not cater to the mixture of clean targets and build targets,
> but I do not know why.

The details has long escaped me but in general we do not want to
have a job deleting all .o files running in parallel with a job that
creates .o files.

So we wanted the following to work:

	$make mrproper defconfig

make would in the standard configuration execute "mrproper" and "defconfig"
in parallel which would result in a broken build.

This is the background for some of the ugly hacks in the
top-level makefile.

	Sam


  reply	other threads:[~2017-08-12  8:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20170810154251.GA23083@localhost.localdomain>
2017-08-10 18:28 ` make clean all broken with -j? + question regarding modpost Randy Dunlap
2017-08-10 22:11   ` Jim Davis
2017-08-12  3:11     ` Masahiro Yamada
2017-08-12  8:06       ` Sam Ravnborg [this message]
2017-08-12 11:13       ` Thomas Meyer
2017-08-12  3:15   ` Masahiro Yamada
2017-08-12 11:21     ` Thomas Meyer
2017-08-10 22:58 ` valdis.kletnieks

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=20170812080655.GA19083@ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=jim.epost@gmail.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=thomas@m3y3r.de \
    --cc=yamada.masahiro@socionext.com \
    /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