All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Matt Mackall <mpm@selenic.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kbuild: Implicit dependence on the C compiler
Date: Tue, 18 Jan 2005 19:35:32 -0800	[thread overview]
Message-ID: <41EDD584.8080307@zytor.com> (raw)
In-Reply-To: <20050119012612.GD3867@waste.org>

Matt Mackall wrote:
>>
>>I would argue that "name of gcc has changed" is possibly a condition
>>that does more harm than good.  It is just as frequently used to have
>>wrappers, like distcc, as it is to have different versions.
> 
> Disagree. I switch compilers all the time and kbuild does the right
> thing for me.
> 
> I do occassionally feel your 'make install' pain and some sort of
> 'make __install' might be called for.
> 

As I said, I don't mind the default being there, it's certainly 
consistent with the default being safe.  However, not being able to 
override it is bad.

	-hpa

  reply	other threads:[~2005-01-19  3:35 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 [this message]
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=41EDD584.8080307@zytor.com \
    --to=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpm@selenic.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 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.