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" <[email protected] > ><mailto:[email protected]>> wrote: > > > > > > On 5/6/14, 3:56 PM, Khem Raj wrote: > > >> > > >> On Tue, May 6, 2014 at 1:55 PM, Denys Dmytriyenko <[email protected] > ><mailto:[email protected]>> 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 -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
