From: Laurentiu Palcu <laurentiu.palcu@intel.com>
To: openembedded-core@lists.openembedded.org
Cc: openembedded-core@lists.linuxtogo.org
Subject: Re: classes: populate_sdk_base: Refine search for SDK env setup file
Date: Mon, 13 Aug 2012 09:50:19 +0300 [thread overview]
Message-ID: <5028A3AB.703@intel.com> (raw)
In-Reply-To: <1344761322-10816-1-git-send-email-marc@cpdesign.com.au>
On 08/12/2012 11:48 AM, Marc Reilly wrote:
> This fixes a relocation failure when installing SDKs built with
> meta-toolchain-qte.
> SDKs build with meta-toolchain-qte have a file named "environment-setup"
> in them as well as the environment-setup-MACH-WHATEVER-BLAH file.
> This patch changes the find name pattern so that only the appropriate
> file is matched.
>
> Signed-off-by: Marc Reilly <marc@cpdesign.com.au>
> ---
> meta/classes/populate_sdk_base.bbclass | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/meta/classes/populate_sdk_base.bbclass b/meta/classes/populate_sdk_base.bbclass
> index 0d19741..60c67bd 100644
> --- a/meta/classes/populate_sdk_base.bbclass
> +++ b/meta/classes/populate_sdk_base.bbclass
> @@ -154,7 +154,7 @@ echo "done"
>
> echo -n "Setting it up..."
> # fix environment paths
> -env_setup_script=$(find $target_sdk_dir -name "environment-setup*")
> +env_setup_script=$(find $target_sdk_dir -name "environment-setup-*")
Good catch! Wouldn't be even better if we used
${REAL_MULTIMACH_TARGET_SYS} instead of *? This way we would match the
exact environment setup script and avoid matching with other scripts.
Thanks,
Laurentiu
> sed -e "s:$DEFAULT_INSTALL_DIR:$target_sdk_dir:g" -i $env_setup_script
>
> # fix dynamic loader paths in all ELF SDK binaries
>
prev parent reply other threads:[~2012-08-13 7:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-12 8:48 classes: populate_sdk_base: Refine search for SDK env setup file Marc Reilly
2012-08-13 6:50 ` Laurentiu Palcu [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=5028A3AB.703@intel.com \
--to=laurentiu.palcu@intel.com \
--cc=openembedded-core@lists.linuxtogo.org \
--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