From: Riku Voipio <riku.voipio@linaro.org>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: Masahiro Yamada <yamada.masahiro@socionext.com>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
debian-kernel <debian-kernel@lists.debian.org>
Subject: Re: [PATCH v4] scripts/package/builddeb: split generating packaging and build
Date: Thu, 29 Mar 2018 10:36:25 +0300 [thread overview]
Message-ID: <CAAqcGHnBZnpexospouTdfOq4NNYg4kDDirKg6+HbYsQrKeUf6Q@mail.gmail.com> (raw)
In-Reply-To: <e46ed72fab5dd0a575e22efa360150ae003db939.camel@decadent.org.uk>
On 29 March 2018 at 03:20, Ben Hutchings <ben@decadent.org.uk> wrote:
> On Wed, 2018-03-28 at 11:58 +0300, Riku Voipio wrote:
> [...]
>> One option:
>>
>> +++ b/scripts/package/mkdebian
>> cat <<EOF > debian/rules
>> -#!/usr/bin/make -f
>> #!$(which $MAKE) -f
> [..]
>
> Shebang lines are interpreted by the kernel, not by a shell. So you
> can't do anything clever like that.
Look more closely ;) Shell expands the variables into the herefile. So
if make is picked from a nonstandard location, the debian/rules
shebang becomes #!/home/masahiro/bin/make -f
As I said the price of this hack is that if use make from non-standard
location, the source package won't build anywhere else. Then again,
you probably shouldn't use non-standard tools when building source
packages for others to consume.
Riku
next prev parent reply other threads:[~2018-03-29 7:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-21 10:10 [PATCH v4] scripts/package/builddeb: split generating packaging and build riku.voipio
2018-03-27 9:07 ` Masahiro Yamada
[not found] ` <CAAqcGHkvKssjFmG0ebz5uBeO_PGeov5_C6MutW65ONp5riFwRg@mail.gmail.com>
2018-03-27 13:28 ` Fwd: " Riku Voipio
2018-03-27 15:23 ` Masahiro Yamada
2018-03-28 8:58 ` Riku Voipio
2018-03-29 0:20 ` Ben Hutchings
2018-03-29 7:36 ` Riku Voipio [this message]
2018-04-05 4:37 ` Masahiro Yamada
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=CAAqcGHnBZnpexospouTdfOq4NNYg4kDDirKg6+HbYsQrKeUf6Q@mail.gmail.com \
--to=riku.voipio@linaro.org \
--cc=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 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.