From: Tasslehoff Kjappfot <tasskjapp@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: Generating a movable SDK
Date: Wed, 04 Jul 2012 08:43:18 +0200 [thread overview]
Message-ID: <4FF3E606.7000001@gmail.com> (raw)
In-Reply-To: <4FE167B4.3020802@gmail.com>
On 06/20/2012 08:03 AM, Tasslehoff Kjappfot wrote:
> On 06/19/2012 10:33 PM, Khem Raj wrote:
>>
>>
>> On Tuesday, June 19, 2012, Steve English <steve.english@navetas.com
>> <mailto:steve.english@navetas.com>> wrote:
>> > Hi,
>> > I've generated a cross compiling ARM SDK
>> (angstrom-eglibc-x86_64-armv7a-v2012.05-toolchain.tar.bz2) that works
>> great if installed in /usr/local/oecore-x86_64. I would like to move
>> these binaries and run them from under my home directory (on this and
>> other host machines).
>> >
>> > I can tweak the PATH and use --sysroot where appropriate, but the ELF
>> binaries themselves specify a loader of
>> /usr/local/oecore-x86_64/sysroots/x86_64-angstromsdk-linux/lib/ld-linux-x86-64.so.2
>>
>> in their .interp header. Is it possible to generate an SDK that uses the
>> standard host loader, or at least uses a relative path for the built
>> loader?
>>
>>
>> Sdk is not install time relocatable yet there is a feature enhancement
>> request in yo to bugzilla for the same
>>
> That request is mine, I think. I have gotten around this by making
> /usr/local/oecore-i686 a symlink to where I want to keep the toolchain
> (in a vcs). Works like a charm.
>
> - Tasslehoff
But now I wish the sdk was relocatable again.
As I said we have the sdk in our vcs, and a symlink in /usr/local to
make the toolchain binaries happy. We have a build server that does
continous builds, and she has multiple trees checked out, so the
symlink-approach is not ideal.
Any clever workaround for this (or even better, a fix to make the sdk
relocatable)?
- Tasslehoff
next prev parent reply other threads:[~2012-07-04 6:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-19 17:03 Generating a movable SDK Steve English
2012-06-19 20:33 ` Khem Raj
2012-06-20 6:03 ` Tasslehoff Kjappfot
2012-06-20 11:02 ` Steve English
2012-07-04 6:43 ` Tasslehoff Kjappfot [this message]
2012-07-05 18:02 ` McClintock Matthew-B29882
2012-07-05 19:21 ` Richard Purdie
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=4FF3E606.7000001@gmail.com \
--to=tasskjapp@gmail.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