Re: [PATCH 1/2] deb-pkg: Add automatic support for armhf architecture

[Hector Oron <hector.oron@gmail.com>]

Hello,

2013/10/13 Ben Hutchings <ben@decadent.org.uk>:
> On Tue, 2013-10-08 at 02:23 +0200, Hector Oron wrote:
>> Hello,
>>
>> 2013/10/6 Ben Hutchings <ben@decadent.org.uk>:
>> > 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.
>>
>> Debian armel userland can be run on any device, so it is suggested to
>> better rely on toolchain configuration rather than kernel config
>> symbols.
>>
>> For arm-gnueabi(hf) toolchain something like:
>>   $ gcc -dumpspecs | grep multilib_defaults -A2 | grep -q soft && echo
>> "This is armel"
>>   $ gcc -dumpspecs | grep multilib_defaults -A2 | grep -q hard && echo
>> "This is armhf"
>> could be checked instead.
> [...]
>
> Is the output of -dumpspecs really so stable that this is going to be
> reliable?

I am not sure about it... but up to date, I have never found a system
that makes it faulty. I would be interesting to check on other
distributions besides Debian.