Bug 1836 - In oe-core built SDK, gcc fails if extracted to another place than /usr/local
Summary: In oe-core built SDK, gcc fails if extracted to another place than /usr/local
Status: RESOLVED NOTABUG
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: devtools / tool chain (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium normal
Target Milestone: 1.2
Assignee: Nitin Kamble
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2011-12-14 11:12 UTC by Tasskjapp
Modified: 2012-02-10 12:41 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Tasskjapp 2011-12-14 11:12:25 UTC 
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]

Discussion about it on the oe-core ML: http://lists.linuxtogo.org/pipermail/openembedded-core/2011-December/013913.html
Comment 1 Nitin Kamble 2012-01-19 15:34:00 UTC 
I am not sure what value is there to allow sdk installing at other places than /usr/local

I think the SDK is to be installed at a fixed /usr/local path.
Comment 2 Tasskjapp 2012-01-19 23:11:51 UTC 
For us the value has been the opportunity to have the sdk in our version control system, making it easier to reproduce earlier builds and making sure sdk and rootfs are in sync.
Comment 3 Nitin Kamble 2012-01-20 10:24:19 UTC 
BTW you can also fix the issue by creating a permanent link from /usr/local to the version control system.

Nitin
Comment 4 Nitin Kamble 2012-02-10 12:33:17 UTC 
Tasskjapp,
  Closing this bug, as it is not a bug. As I mentioned in the comment 3 you should be able to do what you want. If you still need this feature, then reopen this bug.

Thanks,
Nitin
Comment 5 Tasskjapp 2012-02-10 12:41:41 UTC 
The solution you proposed will work for me. Thanks.