public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Ben Hutchings <ben@decadent.org.uk>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
	debian-kernel <debian-kernel@lists.debian.org>
Subject: Re: [PATCH] kbuild: Do not use hyphen in exported variable name
Date: Sun, 23 Apr 2017 08:23:03 +0100	[thread overview]
Message-ID: <1492932183.31767.64.camel@decadent.org.uk> (raw)
In-Reply-To: <CAK7LNASG59wc7Ed24HFiGn0CFUxjDtMgKwy8dhz2PfvRDw1Y1w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1511 bytes --]

On Sun, 2017-04-23 at 15:47 +0900, Masahiro Yamada wrote:
[...]
> I tested dtbs_install once again by myself, but
> dtbinst-root is exported to the sub make
> and the vendor directories are created correctly.
> 
> 
> I checked the debian's forum you gave
> > References: https://bugs.debian.org/833561
> 
> In there, you mentioned:
> "This looks like a bug in make, but we can at least work around it by
> using a non-hyphenated variable name."
> 
> 
> Does this issue happen on a specific Make version?
> 
> I tested GNU make 3.81, 3.82, 4.0, 4.1, 4.2,
> but I was not hit by the problem.

I don't think this is make version dependent.  I can't reproduce the
issue today with make 4.1.  But I would have been using the same
version in August when I wrote that.

What more can I say?  Clearly the hyphenated variable gets passed to
the sub-make in most cases.  But it's not totally reliable because last
year it wasn't working for us.

> In the last post in the thread, you concluded:
> "We believe that the bug you reported is fixed in the latest version of
> linux, which is due to be installed in the Debian FTP archive."

I didn't write that, it's a standard message generated for bugs marked
as closed in a package changelog. :-)

> If so, why is this patch here?
> How is the dtbs_install procedure different in the Debian package?

This is the patch I applied to the package.

Ben.

-- 
Ben Hutchings
I haven't lost my mind; it's backed up on tape somewhere.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2017-04-23  7:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-18  1:00 [PATCH] kbuild: Do not use hyphen in exported variable name Ben Hutchings
2017-04-18  4:44 ` Sam Ravnborg
2017-04-23  6:47 ` Masahiro Yamada
2017-04-23  7:23   ` Ben Hutchings [this message]
2017-04-30 14:14     ` Masahiro Yamada
2017-04-30 14:49       ` Ben Hutchings
2017-05-03  4:47         ` Masahiro Yamada
2017-08-19  1:13         ` Ben Hutchings
2017-08-19 17:37           ` Masahiro Yamada
2017-08-19 20:14             ` Ben Hutchings

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=1492932183.31767.64.camel@decadent.org.uk \
    --to=ben@decadent.org.uk \
    --cc=debian-kernel@lists.debian.org \
    --cc=linux-kbuild@vger.kernel.org \
    --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