Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Chin Huat Ang <chin.huat.ang@intel.com>,
	openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v3] toolchain-scripts: preserve host path in environment setup script
Date: Fri, 04 May 2018 16:04:38 +0100	[thread overview]
Message-ID: <1525446278.3857.13.camel@linuxfoundation.org> (raw)
In-Reply-To: <1524643213-5505-1-git-send-email-chin.huat.ang@intel.com>

On Wed, 2018-04-25 at 16:00 +0800, Chin Huat Ang wrote:
> The environment setup script generated in the build directory sets
> the PATH
> variable by expanding ${PATH} which would have host paths filtered.
> Sourcing
> this script to run runqemu will not work as it complains host stty
> (/bin/stty)
> cannot be found.
> 
> To resolve this, the script no longer expands ${PATH} during
> generation time,
> instead it will now source oe-init-build-env to initialize the build
> environment so that all host paths will be preserved. Also be sure to
> prepend
> STAGING_BINDIR_TOOLCHAIN to the PATH variable so that the toolchain
> from the
> build directory can be found.
> 
> [YOCTO #12695]
> 
> Signed-off-by: Chin Huat Ang <chin.huat.ang@intel.com>
> ---
>  meta/classes/toolchain-scripts.bbclass | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)

This didn't work as expected on machines which have /bin/sh pointing to
dash, the oe-selftests showed failures.

I've added a followup patch which addresses that problem which allowed
me to merge the patches.

Cheers,

Richard


      reply	other threads:[~2018-05-04 15:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-25  8:00 [PATCH v3] toolchain-scripts: preserve host path in environment setup script Chin Huat Ang
2018-05-04 15:04 ` Richard Purdie [this message]

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=1525446278.3857.13.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=chin.huat.ang@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