Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: Mark Hatle <mark.hatle@windriver.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: meta-toolchain doesn't compile working binaries
Date: Tue, 06 May 2014 17:49:15 -0400	[thread overview]
Message-ID: <20140506214915.GH11339@denix.org> (raw)
In-Reply-To: <536957A8.90300@windriver.com>

On Tue, May 06, 2014 at 04:44:08PM -0500, Mark Hatle wrote:
> On 5/6/14, 4:40 PM, Khem Raj wrote:
> >
> >On May 6, 2014 2:25 PM, "Mark Hatle" <mark.hatle@windriver.com
> ><mailto:mark.hatle@windriver.com>> wrote:
> > >
> > > On 5/6/14, 3:56 PM, Khem Raj wrote:
> > >>
> > >> On Tue, May 6, 2014 at 1:55 PM, Denys Dmytriyenko <denis@denix.org
> ><mailto:denis@denix.org>> wrote:
> > >>>
> > >>> Do you know that OE toolchain is not relocatable?
> > >>
> > >>
> > >> is that true ?
> > >>
> > >
> > > It's the load path of the executables, they use the libc-nativesdk, so they
> >need a hard path to the correct ld.so to get started.
> >
> >isnt this fixed by the installer when it is run
> 
> Yes, it sounds like either he moved the files after the the
> installer ran, or didn't use the installer at all and just tried to
> execute them out of the build system.

Exactly what I said earlier about using relocate_sdk.py in the installer, 
which Khem conveniently ignored and removed when replying... :) Just kidding.


> (If the installer -was- used, then it's definitely a bug.)

There's no bug as far as I know, as SDK/toolchain is a major part of our 
product and we test it actively with every release.

-- 
Denys


  reply	other threads:[~2014-05-06 21:49 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-06  8:14 meta-toolchain doesn't compile working binaries Björn Krombholz
2014-05-06 17:01 ` Khem Raj
2014-05-06 20:55 ` Denys Dmytriyenko
2014-05-06 20:56   ` Khem Raj
2014-05-06 20:59     ` Denys Dmytriyenko
2014-05-06 21:25     ` Mark Hatle
2014-05-06 21:40       ` Khem Raj
2014-05-06 21:44         ` Mark Hatle
2014-05-06 21:49           ` Denys Dmytriyenko [this message]
2014-05-07 12:54           ` Björn Krombholz
2014-05-07 14:37             ` Mark Hatle
2014-05-07 14:58             ` Björn Krombholz
2014-05-07 17:13               ` Björn Krombholz
2014-05-06 21:44       ` Denys Dmytriyenko
2014-05-06 21:49         ` Mark Hatle
2014-05-06 21:59           ` Denys Dmytriyenko
2014-05-07 15:27             ` 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=20140506214915.GH11339@denix.org \
    --to=denis@denix.org \
    --cc=mark.hatle@windriver.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