From: "thilo.cestonaro@ts.fujitsu.com" <thilo.cestonaro@ts.fujitsu.com>
To: "raj.khem@gmail.com" <raj.khem@gmail.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: Building for armv7athf-neon but toolchain is softfp
Date: Thu, 28 Jul 2016 07:11:17 +0000 [thread overview]
Message-ID: <1469689696.6948.1.camel@ts.fujitsu.com> (raw)
In-Reply-To: <0AFF0F4F-BAA0-43F7-ABE3-32ABEC5D924C@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 679 bytes --]
On Mi, 2016-07-27 at 08:18 -0700, Khem Raj wrote:
> >
> > On Jul 27, 2016, at 5:14 AM, thilo.cestonaro@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
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 3847 bytes --]
next prev parent reply other threads:[~2016-07-28 7:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-22 13:39 Building for armv7athf-neon but toolchain is softfp thilo.cestonaro
2016-07-22 14:10 ` Khem Raj
2016-07-25 14:06 ` thilo.cestonaro
2016-07-25 14:14 ` Khem Raj
2016-07-26 9:39 ` thilo.cestonaro
2016-07-27 9:57 ` Khem Raj
2016-07-27 12:06 ` thilo.cestonaro
2016-07-27 12:14 ` thilo.cestonaro
2016-07-27 15:18 ` Khem Raj
2016-07-28 7:11 ` thilo.cestonaro [this message]
2016-07-28 8:18 ` thilo.cestonaro
2016-07-28 13:55 ` 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=1469689696.6948.1.camel@ts.fujitsu.com \
--to=thilo.cestonaro@ts.fujitsu.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/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