Linux kbuild/kconfig development
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: "linux-kbuild@vger.kernel.org" <linux-kbuild@vger.kernel.org>
Subject: Re: Fwd: [tip:x86/x32] x32:  Warn and disable rather than error if binutils too old
Date: Tue, 28 Feb 2012 08:21:15 +0100	[thread overview]
Message-ID: <20120228072115.GA2213@merkur.ravnborg.org> (raw)
In-Reply-To: <4F4C0877.5000804@zytor.com>

On Mon, Feb 27, 2012 at 02:49:27PM -0800, H. Peter Anvin wrote:
> Kbuild people - for the lack of a way to doing toolchain dependencies in
> Kconfig I'm doing this right now for x32 support.  I am a little unclear
> if this is the right thing to do, especially if I should be using := or

Looks good at first look.

":=" is almost always the right choice if this is not part of a rule somewhere.
With ":=" the rhs is only evaluated once and the result stored in the
variable on the lhs.

In this particular case you only use the lhs once - so there is no
real difference.

Another important difference is that with ":=" the rhs is evaluated when
make see it first time.
With "=" make defer it until the lhs is used.

again in you case there is no difference as you use the lhs just after
you have the assignment.

[But I guess you already knew all this...]

	Sam



      parent reply	other threads:[~2012-02-28  7:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <tip-0bf6276392e990dd0da0ccd8e10f42597d503f29@git.kernel.org>
2012-02-27 22:49 ` Fwd: [tip:x86/x32] x32: Warn and disable rather than error if binutils too old H. Peter Anvin
2012-02-27 22:51   ` H. Peter Anvin
2012-02-28  7:21   ` Sam Ravnborg [this message]

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=20120228072115.GA2213@merkur.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=hpa@zytor.com \
    --cc=linux-kbuild@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