On Thu, Jul 28, 2016 at 1:18 AM, thilo.ceston...@ts.fujitsu.com <thilo.ceston...@ts.fujitsu.com> wrote: > Hey Khem! > > Thanks for your help!! We used to have an extra ld-script which once worked. > It was injected into the sdk in our sdk-install script by moving the > toolchain ld to ld.real and creating a script which > calls the ld.real with the ldscript as parameter. I didn't introduce this in > the sdk install, so I thought it is from oe-core. But just found out that we > create that ld script usage and removed it. >
avoid such hacks in future. Or mention them when you describe the problem. > That fix the executables. I guess, as we did the step from gcc 4 to 5, it was > for gcc 4 and broke gcc 5. > > Anyway thanks for your patience and time! > > Cheers, > Thilo > > On Do, 2016-07-28 at 07:11 +0000, thilo.ceston...@ts.fujitsu.com wrote: >> On Mi, 2016-07-27 at 08:18 -0700, Khem Raj wrote: >> > >> > > >> > > >> > > On Jul 27, 2016, at 5:14 AM, thilo.ceston...@ts.fujitsu.com wrote: >> > > >> > > Hey Khem, >> > > >> > > I figured, when I do the compile in 2 steps, so compile then link and >> > > change the link command to use the ubuntu arm-linux-gnueabihf-gcc >> > > instead of the gcc from the sdk, the binary is useable. >> > this could be a gnu_hash issue then. Can you add -Wl,--hash-style=gnu to >> > compiler cmd when linking using OE SDK >> > >> No success :( ... I tested it, altough it was already included in LDFLAGS >> from sdk env. Added it the the compile command and the link command. Doesn't >> change anything :(. >> Any other idea? >> >> Cheers, >> Thilo >> -- >> _______________________________________________ >> Openembedded-core mailing list >> Openembedded-core@lists.openembedded.org >> http://lists.openembedded.org/mailman/listinfo/openembedded-core -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
