public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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: Mon, 17 Jan 2005 14:47:44 -0800	[thread overview]
Message-ID: <41EC4090.60709@zytor.com> (raw)
In-Reply-To: <20050117221331.GC17132@mars.ravnborg.org>

Sam Ravnborg wrote:
> On Mon, Jan 17, 2005 at 02:03:41PM -0800, H. Peter Anvin wrote:
> 
>>I don't mind the current default, but saying I shouldn't be able to 
>>override it is asinine.
> 
> No-one asked for it until now.

That's of course perfectly fair, and I'm not flaming you for saying that 
noone had asked for it.  Saying that it *shouldn't* be done is another 
matter, that's all.

> Any preferred syntax to disable this dependency check?

How about "make CCDEP=0"?

> 
>>It also means "make install" is largely unusable.
> 
> Maybe we should not let install be dependent on vmlinux then?

Maybe not.  I don't think "modules_install" have any explicit 
dependencies, it's up to the user to make sure things are already built, 
so we might as well do the same thing with "make install".

	-hpa


  reply	other threads:[~2005-01-17 22:59 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 [this message]
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
     [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=41EC4090.60709@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