From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lf0-f45.google.com ([209.85.215.45]:35826 "EHLO mail-lf0-f45.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750795AbeC2Hg1 (ORCPT ); Thu, 29 Mar 2018 03:36:27 -0400 Received: by mail-lf0-f45.google.com with SMTP id t132-v6so7057740lfe.2 for ; Thu, 29 Mar 2018 00:36:26 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: <20180221101032.27263-1-riku.voipio@linaro.org> From: Riku Voipio Date: Thu, 29 Mar 2018 10:36:25 +0300 Message-ID: Subject: Re: [PATCH v4] scripts/package/builddeb: split generating packaging and build Content-Type: text/plain; charset="UTF-8" Sender: linux-kbuild-owner@vger.kernel.org List-ID: To: Ben Hutchings Cc: Masahiro Yamada , Linux Kbuild mailing list , debian-kernel On 29 March 2018 at 03:20, Ben Hutchings wrote: > On Wed, 2018-03-28 at 11:58 +0300, Riku Voipio wrote: > [...] >> One option: >> >> +++ b/scripts/package/mkdebian >> cat < 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