Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: GCC fails when SDK is not extracted to /usr/local
Date: Thu, 8 Dec 2011 13:11:57 -0600	[thread overview]
Message-ID: <4EE10BFD.9000405@windriver.com> (raw)
In-Reply-To: <79A60C08-1C6C-48A6-8CAF-F40C6562B755@gmail.com>

On 12/8/11 1:04 PM, Tasslehoff Kjappfot wrote:
>
> On Dec 8, 2011, at 3:56 PM, Tom Rini wrote:
>
>> On Wed, Dec 7, 2011 at 12:16 AM, Tasslehoff Kjappfot
>> <tasskjapp@gmail.com>  wrote:
>>> gcc fails when I extract my SDK to another place than /usr/local.
>>>
>>> Output when it fails:
>>>
>>> $ ./arm-angstrom-linux-gnueabi-gcc
>>> bash: ./arm-angstrom-linux-gnueabi-gcc: No such file or directory
>>>
>>> Readelf output:
>>>
>>> $ readelf -d arm-angstrom-linux-gnueabi-gcc
>>>
>>> Dynamic section at offset 0x34394 contains 21 entries:
>>>   Tag        Type                         Name/Value
>>>   0x00000001 (NEEDED)                     Shared library: [libc.so.6]
>>>   0x0000000f (RPATH)                      Library rpath:
>>> [/usr/local/angstrom-eglibc-i686-armv7a/sysroots/i686-angstromsdk-linux/usr/lib/armv7a-angstrom-linux-gnueabi:/usr/local/angstrom-eglibc-i686-armv7a/sysroots/i686-angstromsdk-linux/lib]
>>>
>>> Is it the RPATH here that's making trouble for me?
>>
>> Not exactly.  And RPATH is needed to find some of the shared libraries
>> that are needed.  I thought we had been running chrpath over these to
>> make them relocatable, however.
>>
>> --
>> Tom
>>
>
> Does this RPATH indicate that its not relocatable? Anything else I can check?

It should be using RUN_PATH  $ORIGIN to relocate itself based on the initial 
run-time location.

It sounds like something is not being run as it should for the SDK component(s).

--Mark

> - Tasslehoff
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core




  reply	other threads:[~2011-12-08 19:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-07  7:16 GCC fails when SDK is not extracted to /usr/local Tasslehoff Kjappfot
2011-12-08 14:56 ` Tom Rini
2011-12-08 19:04   ` Tasslehoff Kjappfot
2011-12-08 19:11     ` Mark Hatle [this message]
2011-12-08 20:33       ` Khem Raj

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=4EE10BFD.9000405@windriver.com \
    --to=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