From: Mark Hatle <mark.hatle@windriver.com>
To: "Teresa Gámez" <t.gamez@phytec.de>, yocto@yoctoproject.org
Subject: Re: Compile issue with 1.7 SDK and hf
Date: Tue, 3 Feb 2015 19:30:53 -0600 [thread overview]
Message-ID: <54D1764D.6080708@windriver.com> (raw)
In-Reply-To: <1422524145.4319.25.camel@lws-gamez.phytec.de>
On 1/29/15 3:35 AM, Teresa Gámez wrote:
> Hello,
>
> I have installed a SDK based on yocto 1.7 with
> DEFAULTTUNE ?="cortexa8thf-neon" set.
>
> I have tried to compile the barebox bootloader with this
> SDK like this:
>
> source /opt/poky/1.7/environment-setup-cortexa8t2hf-vfp-neon-poky-linux-gnueabi
> unset LDFLAGS
> make am335x_defconfig
> Also enabled a barebox target tool in menuconfig: BAREBOXENV_TARGET
> make
It looks like the tool you are trying to build is not using the full $CC,
otherwise the necessary ABI and related hardfloat parameters would be passed..
(alternatively if the component is adding it's own soft-float ABI values that
could also result in the failure.)
Generally the hard float toolchain does not have all of the code in place to
produce a soft-float binary as the executables have a different (incompatible) ABI.
> And see following compile error:
>
> ..
> CC scripts/bareboxenv-target
> In file included
> from /opt/poky/1.7/sysroots/cortexa8t2hf-vfp-neon-poky-linux-gnueabi/usr/include/features.h:389:0,
>
> from /opt/poky/1.7/sysroots/cortexa8t2hf-vfp-neon-poky-linux-gnueabi/usr/include/stdio.h:27,
> from scripts/bareboxenv.c:20:
> /opt/poky/1.7/sysroots/cortexa8t2hf-vfp-neon-poky-linux-gnueabi/usr/include/gnu/stubs.h:7:29: fatal error: gnu/stubs-soft.h: No such file or directory
> # include <gnu/stubs-soft.h>
> ^
> compilation terminated.
>
> I have tried the same with other non yocto hf toolchains. Compilation
> worked there. I wonder if this is a toolchain issue or more a barebox
> issue.
I suspect in this case it's barebox. If you turn on more explicit (verbose)
logging you may see the error in the calls.
--Mark
> I also noticed:
>
> arm-poky-linux-gnueabi-gcc -dM -E - < /dev/null | grep ARM_PCS
> #define __ARM_PCS 1
>
>
> arm-poky-linux-gnueabi-gcc -mfloat-abi=hard -dM -E - < /dev/null | grep
> ARM_PCS
> #define __ARM_PCS_VFP 1
>
> Other hf toolchains have __ARM_PCS_VFP 1 regardless if -mfloat-abi
> parameter set or not. I have no clue what the right behaviour should be.
> Can someone explain?
>
> Regards
> Teresa
>
>
>
prev parent reply other threads:[~2015-02-04 1:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-29 9:35 Compile issue with 1.7 SDK and hf Teresa Gámez
2015-02-04 1:30 ` Mark Hatle [this message]
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=54D1764D.6080708@windriver.com \
--to=mark.hatle@windriver.com \
--cc=t.gamez@phytec.de \
--cc=yocto@yoctoproject.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.