From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Laurentiu Palcu <laurentiu.palcu@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v2 5/6] SDK: relocate symlinks too
Date: Fri, 21 Sep 2012 11:22:50 +0100 [thread overview]
Message-ID: <1348222970.10108.48.camel@ted> (raw)
In-Reply-To: <a10d0e1b4dc0667b04f1cfa906378ce9094449ae.1348148406.git.laurentiu.palcu@intel.com>
On Thu, 2012-09-20 at 16:48 +0300, Laurentiu Palcu wrote:
> The directory usr/libexec/ in the SDK sysroot contains the default
> symlinks to the toolchain binaries and these, too, need to point to the
> correct toolchain path.
>
> [YOCTO #3090]
>
> Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com>
> ---
> meta/classes/populate_sdk_base.bbclass | 5 +++++
> .../adt-installer/scripts/adt_installer_internal | 5 +++++
> 2 files changed, 10 insertions(+)
I've merged this since it definitely improves the situation but I am
left wondering if we shouldn't generate relative symlinks in the first
place for the toolchain...
Cheers,
Richard
next prev parent reply other threads:[~2012-09-21 10:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-20 13:47 [PATCH v2 0/6] SDK and adt_installer fixes Laurentiu Palcu
2012-09-20 13:47 ` [PATCH v2 1/6] adt-installer: fix package installation issue Laurentiu Palcu
2012-09-20 13:47 ` [PATCH v2 2/6] SDK: fix installation into symlinked directories Laurentiu Palcu
2012-09-20 13:48 ` [PATCH v2 3/6] adt-installer: ensure directory exists before copying/removing Laurentiu Palcu
2012-09-20 13:48 ` [PATCH v2 4/6] SDK: remove references to Poky distro from tarball installer Laurentiu Palcu
2012-09-20 13:48 ` [PATCH v2 5/6] SDK: relocate symlinks too Laurentiu Palcu
2012-09-21 10:22 ` Richard Purdie [this message]
2012-09-21 10:31 ` Laurentiu Palcu
2012-09-20 13:48 ` [PATCH v2 6/6] SDK: allow toolchain installation from another directory Laurentiu Palcu
2012-09-21 22:22 ` [PATCH v2 0/6] SDK and adt_installer fixes Saul Wold
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=1348222970.10108.48.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=laurentiu.palcu@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