From: "H. Peter Anvin" <hpa@zytor.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kbuild: Implicit dependence on the C compiler
Date: Sat, 29 Jan 2005 17:17:11 -0800 [thread overview]
Message-ID: <41FC3597.8090908@zytor.com> (raw)
In-Reply-To: <20050129212602.GA9610@mars.ravnborg.org>
Sam Ravnborg wrote:
>
> make KBUILD_NOCMDDEP=1
> will do what you want - at least I have it in my tree now.
> I could not just ignore 'gcc' - but had to ignore the full commandline.
>
> This is due to more complex commands like:
> rm -f file; $(LD) ...
>
That's probably the right behaviour actually.
> Within the Makefile.lib when I check KBUILD_NOCMDDEP there is no
> knowledge of the actual command being executed. And an implmentation
> that just filtered out $(CC) was too ugly.
> And due to the above mentioned command I could not just skip the first
> word on the command line.
>
>
> I will push my bk tree soon and it will show up in next -mm.
>
> It is not perfect in the sense that the last part of the build will get
> redone (GEN .version and onwards). This is fixable but not worth it
> right now.
>
> So with current implmentation executing:
>
> make
>
> make KBUILD_NOCMDDEP=1 CROSS_COMPILE=i586-pc-linux-gnu-
>
> will result in only a few files being rebuild - and not the whole
> kernel as before.
That's fair. You got what you asked for.
-hpa
next prev parent reply other threads:[~2005-01-30 1:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-17 21:40 kbuild: Implicit dependence on the C compiler H. Peter Anvin
2005-01-17 22:00 ` Sam Ravnborg
2005-01-17 22:03 ` H. Peter Anvin
2005-01-17 22:13 ` Sam Ravnborg
2005-01-17 22:47 ` H. Peter Anvin
2005-01-18 19:05 ` Sam Ravnborg
2005-01-18 19:35 ` H. Peter Anvin
2005-01-19 1:26 ` Matt Mackall
2005-01-19 3:35 ` H. Peter Anvin
2005-01-19 4:42 ` Marcin Dalecki
2005-01-29 21:26 ` Sam Ravnborg
2005-01-30 1:17 ` H. Peter Anvin [this message]
[not found] <fa.e2phu9o.1c30pig@ifi.uio.no>
[not found] ` <fa.gakt9b5.1klcr9h@ifi.uio.no>
2005-01-19 16:09 ` Bodo Eggert
2005-01-19 16:35 ` linux-os
2005-01-19 17:15 ` Sytse Wielinga
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=41FC3597.8090908@zytor.com \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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