1836 2011-12-14 11:12:25 +0000 In oe-core built SDK, gcc fails if extracted to another place than /usr/local 2012-02-10 12:41:41 +0000 1 1 7 Build System, Metadata & Runtime OE-Core devtools / tool chain unspecified x86 Multiple RESOLVED NOTABUG Medium normal 1.2 1 tasskjapp nitin.a.kamble jessica.zhang meta.mr.watcher meta.watcher tasskjapp --- --- --- oldest_to_newest 17644 0 tasskjapp 2011-12-14 11:12:25 +0000 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 18277 1 nitin.a.kamble 2012-01-19 15:34:00 +0000 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. 18288 2 tasskjapp 2012-01-19 23:11:51 +0000 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. 18297 3 nitin.a.kamble 2012-01-20 10:24:19 +0000 BTW you can also fix the issue by creating a permanent link from /usr/local to the version control system. Nitin 18592 4 nitin.a.kamble 2012-02-10 12:33:17 +0000 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 18593 5 tasskjapp 2012-02-10 12:41:41 +0000 The solution you proposed will work for me. Thanks.