All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: McClintock Matthew-B29882 <B29882@freescale.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
	"openembedded-core@openembedded.org"
	<openembedded-core@openembedded.org>
Subject: Re: [yocto] [PATCH] Update intltool to set perl shebang correctly for installed tools
Date: Wed, 03 Aug 2011 14:01:47 -0600	[thread overview]
Message-ID: <4E39A92B.5040207@mlbassoc.com> (raw)
In-Reply-To: <CAEsOVNf5eZ6PLkqw_Ya8XEEzr1uQprGXOeqc4aS7BCcja7Bsmw@mail.gmail.com>

On 2011-08-03 13:52, McClintock Matthew-B29882 wrote:
> (Sorry if this get sent twice...)
>
> On Wed, Aug 3, 2011 at 11:44 AM, Gary Thomas<gary@mlbassoc.com>  wrote:
>> On 2011-08-03 10:33, Matthew McClintock wrote:
>>>
>>> Several installed scripts set the perl shebang that is too long
>>> which can cause failures on certian older bash versions.
>>
>> How does the change below correspond to this comment?  It's not
>> clear [at least to me] how changing that environment variable
>> affects shebang constructs.  Can you give a more thorough explanation?
>
> The scripts intltool-{update,etc} installed in sysroot end up having
> *really* long shebangs without this change. On older distros this
> causes the intltool scripts to just fail usually during the configure
> task. intltools recipe itself will
> build and install fine. However, when a package that requires
> intltool's is being configured they will all fail withing invoking
> intltools.

This much was already clear from your explanation - the "what happens and
why it needs fixing" part.

What I don't see is the "why" - why does defining PERL vs PERL_virtclass-native
have this effect?

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------



WARNING: multiple messages have this Message-ID (diff)
From: Gary Thomas <gary@mlbassoc.com>
To: McClintock Matthew-B29882 <B29882@freescale.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
	"openembedded-core@openembedded.org"
	<openembedded-core@openembedded.org>
Subject: Re: [PATCH] Update intltool to set perl shebang correctly for installed tools
Date: Wed, 03 Aug 2011 14:01:47 -0600	[thread overview]
Message-ID: <4E39A92B.5040207@mlbassoc.com> (raw)
In-Reply-To: <CAEsOVNf5eZ6PLkqw_Ya8XEEzr1uQprGXOeqc4aS7BCcja7Bsmw@mail.gmail.com>

On 2011-08-03 13:52, McClintock Matthew-B29882 wrote:
> (Sorry if this get sent twice...)
>
> On Wed, Aug 3, 2011 at 11:44 AM, Gary Thomas<gary@mlbassoc.com>  wrote:
>> On 2011-08-03 10:33, Matthew McClintock wrote:
>>>
>>> Several installed scripts set the perl shebang that is too long
>>> which can cause failures on certian older bash versions.
>>
>> How does the change below correspond to this comment?  It's not
>> clear [at least to me] how changing that environment variable
>> affects shebang constructs.  Can you give a more thorough explanation?
>
> The scripts intltool-{update,etc} installed in sysroot end up having
> *really* long shebangs without this change. On older distros this
> causes the intltool scripts to just fail usually during the configure
> task. intltools recipe itself will
> build and install fine. However, when a package that requires
> intltool's is being configured they will all fail withing invoking
> intltools.

This much was already clear from your explanation - the "what happens and
why it needs fixing" part.

What I don't see is the "why" - why does defining PERL vs PERL_virtclass-native
have this effect?

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


  reply	other threads:[~2011-08-03 20:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-03 16:33 [PATCH] Update intltool to set perl shebang correctly for installed tools Matthew McClintock
2011-08-03 16:44 ` [yocto] " Gary Thomas
2011-08-03 16:44   ` Gary Thomas
2011-08-03 19:52   ` McClintock Matthew-B29882
2011-08-03 20:01     ` Gary Thomas [this message]
2011-08-03 20:01       ` Gary Thomas
2011-08-03 20:08       ` [yocto] " Phil Blundell
2011-08-03 20:25       ` [OE-core] " McClintock Matthew-B29882
2011-08-04  3:38   ` McClintock Matthew-B29882

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=4E39A92B.5040207@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=B29882@freescale.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=openembedded-core@openembedded.org \
    --cc=yocto@yoctoproject.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 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.