On 2 April 2015 at 15:01, Arnaud Patard <arnaud.pat...@rtp-net.org> wrote:
> riku.voi...@linaro.org writes:
>> --- a/scripts/package/builddeb
>> +++ b/scripts/package/builddeb
>> @@ -45,7 +45,16 @@ create_package() {
>> arm64)
>> debarch=arm64 ;;
>> arm*)
>> - debarch=arm$(grep -q CONFIG_AEABI=y $KCONFIG_CONFIG && echo el
>> || true) ;;
>> + if grep -q CONFIG_AEABI=y $KCONFIG_CONFIG; then
>> + if $CC -dM -E - < /dev/null|grep -q __ARM_PCS_VFP; then
>
> Actually, I guess there's nothing preventing you building a armhf kernel
> with a compiler not having __ARM_PCS_VFP defined by default, but I'm not sure
> we should take care of this case. One can always use KBUILD_DEBARCH=armhf.
I think the common use cases would be a) native compilers or b)
cross-compiler targeting the same debian architecture as the rootfs.
This patch provides automatic detection for both cases. For corner
cases, one will have to manually specify KBUILD_DEBARCH - which one
already had to do if one was targeting armhf.
Riku
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
https://lists.debian.org/CAAqcGH=iT4-R=D+WWCZ2ibKHnc8dGgHPyC+5WyOT2WM=luj...@mail.gmail.com
