From: Riku Voipio <riku.voipio@iki.fi>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: linux-kbuild <linux-kbuild@vger.kernel.org>,
maximilian attems <max@stro.at>, Michal Marek <mmarek@suse.cz>,
Fathi Boudra <fathi.boudra@linaro.org>,
debian-arm@lists.debian.org, Hector Oron <hector.oron@gmail.com>
Subject: Re: [PATCH v2 1/2] deb-pkg: Add automatic support for armhf architecture
Date: Tue, 10 Jun 2014 16:06:39 +0300 [thread overview]
Message-ID: <20140610130639.GA25366@afflict.kos.to> (raw)
In-Reply-To: <1402273294.23860.59.camel@deadeye.wl.decadent.org.uk>
On Mon, Jun 09, 2014 at 01:21:34AM +0100, Ben Hutchings wrote:
> The Debian armhf architecture uses the ARM EABI hard-float variant,
> whereas armel uses the soft-float variant. Although the kernel
> doesn't use FP itself, CONFIG_VFP must be enabled to support
> hard-float userland and will probably be disabled when supporting a
> soft-float userland. So set the architecture to armhf by default when
> CONFIG_AEABI and CONFIG_VFP are both enabled.
>
> Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
> ---
> v2: rebased
>
> After discussion with Hector, we agreed this would be a worthwhile
> change. Hector may later improve this by using gcc specs.
That should be easy:
-if grep -q CONFIG_VFP=y $KCONFIG_CONFIG; then
+if $CC -dM -E - < /dev/null|grep -q __ARM_PCS_VFP; then
It worked at least for my cross-compile test a minute ago.
Riku
> Ben.
>
> scripts/package/builddeb | 11 ++++++++++-
> 1 file changed, 10 insertions(+), 1 deletion(-)
>
> diff --git a/scripts/package/builddeb b/scripts/package/builddeb
> index f46e4dd..6756ed6 100644
> --- a/scripts/package/builddeb
> +++ b/scripts/package/builddeb
> @@ -43,7 +43,16 @@ create_package() {
> mips*)
> debarch=mips$(grep -q CPU_LITTLE_ENDIAN=y $KCONFIG_CONFIG && echo el || true) ;;
> arm*)
> - debarch=arm$(grep -q CONFIG_AEABI=y $KCONFIG_CONFIG && echo el || true) ;;
> + if grep -q CONFIG_AEABI=y $KCONFIG_CONFIG; then
> + if grep -q CONFIG_VFP=y $KCONFIG_CONFIG; then
> + debarch=armhf
> + else
> + debarch=armel
> + fi
> + else
> + debarch=arm
> + fi
> + ;;
> *)
> echo "" >&2
> echo "** ** ** WARNING ** ** **" >&2
>
>
> --
> Ben Hutchings
> One of the nice things about standards is that there are so many of them.
next prev parent reply other threads:[~2014-06-10 13:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-09 0:21 [PATCH v2 1/2] deb-pkg: Add automatic support for armhf architecture Ben Hutchings
2014-06-09 7:04 ` Ian Campbell
2014-06-10 21:42 ` Ben Hutchings
2014-06-11 6:33 ` Ian Campbell
2014-06-10 8:10 ` Fathi Boudra
2014-06-10 13:06 ` Riku Voipio [this message]
2014-07-14 14:14 ` Riku Voipio
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=20140610130639.GA25366@afflict.kos.to \
--to=riku.voipio@iki.fi \
--cc=ben@decadent.org.uk \
--cc=debian-arm@lists.debian.org \
--cc=fathi.boudra@linaro.org \
--cc=hector.oron@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=max@stro.at \
--cc=mmarek@suse.cz \
/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