From: Laurentiu Palcu <laurentiu.palcu@intel.com>
To: Tasslehoff Kjappfot <tasskjapp@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: SDK relocation issues
Date: Tue, 11 Jun 2013 16:24:17 +0300 [thread overview]
Message-ID: <20130611132417.GE7181@lpalcu-linux> (raw)
In-Reply-To: <51B7219D.7070703@gmail.com>
On Tue, Jun 11, 2013 at 03:09:49PM +0200, Tasslehoff Kjappfot wrote:
>
> I have time for one more :)
>
> What does it mean that the SDK is relocatable? That I can choose
> when I run the .sh where I want to install it? Is it then "bound" to
> that directory, so that every dev that wants to use the SDK have to
> run the installer on their machine?
That's correct. Each developer can install the SDK wherever he/she wants
to.
> Maybe my "I can copy it wherever
> I want" interpretation of relocatable is the problem :)
Indeed, that's causing the issue. :)
>
> The DL is shipped with the toolchain, but is looked for in the path
> I installed to when I run the .sh. If I move the entire folder, I
> get the problems.
When the relocation process takes place, it changes the path to the
dynamic loader in all binaries. Moving the SDK to another location would
imply re-running the installer again and choose the new location as
destination.
Thanks,
Laurentiu
>
> Regards,
> Tasslehoff
>
>
>
>
next prev parent reply other threads:[~2013-06-11 13:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-11 9:35 SDK relocation issues Tasslehoff Kjappfot
2013-06-11 12:43 ` Laurentiu Palcu
2013-06-11 12:58 ` Tasslehoff Kjappfot
2013-06-11 13:09 ` Tasslehoff Kjappfot
2013-06-11 13:24 ` Laurentiu Palcu [this message]
2013-06-12 6:12 ` Tasslehoff Kjappfot
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=20130611132417.GE7181@lpalcu-linux \
--to=laurentiu.palcu@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=tasskjapp@gmail.com \
/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