From: "Belal, Awais" <Awais_Belal@mentor.com>
To: Alexander Kanavin <alexander.kanavin@linux.intel.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] autogen: fix autoopts script generation to handle shebang
Date: Mon, 15 May 2017 09:01:22 +0000 [thread overview]
Message-ID: <1494838882617.45509@mentor.com> (raw)
In-Reply-To: <b3b3d45f-7209-2ba2-a299-5da723ea5008@linux.intel.com>
> Isn't this backwards? And why is PERL set twice in a row?
Really did not get the first question. Regarding PERL being set twice, I am just trying to manipulate it to the actual host binary, is there a better way? 'which perl' or 'env perl' will only point to the symlink under HOSTTOOLS.
BR,
Awais
________________________________________
From: openembedded-core-bounces@lists.openembedded.org <openembedded-core-bounces@lists.openembedded.org> on behalf of Alexander Kanavin <alexander.kanavin@linux.intel.com>
Sent: Friday, May 12, 2017 7:06 PM
To: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] autogen: fix autoopts script generation to handle shebang
On 05/12/2017 04:59 PM, Awais Belal wrote:
> +- *perl ) echo '#!/usr/bin/env perl'
> ++ *perl ) PERL=`which perl`
> ++ PERL=`readlink -f ${PERL}`
> ++ echo '#!' ${PERL}
Isn't this backwards? And why is PERL set twice in a row?
Alex
--
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
next prev parent reply other threads:[~2017-05-15 9:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-12 13:59 [PATCH] autogen: fix autoopts script generation to handle shebang Awais Belal
2017-05-12 14:06 ` Alexander Kanavin
2017-05-15 9:01 ` Belal, Awais [this message]
2017-05-15 11:53 ` Alexander Kanavin
2017-05-15 15:03 ` Belal, Awais
2017-05-15 15:10 ` Alexander Kanavin
2017-05-16 5:36 ` Belal, Awais
2017-05-16 11:32 ` Alexander Kanavin
2017-05-17 8:50 ` Belal, Awais
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=1494838882617.45509@mentor.com \
--to=awais_belal@mentor.com \
--cc=alexander.kanavin@linux.intel.com \
--cc=openembedded-core@lists.openembedded.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