[email protected] writes: > From: Ben Hutchings <[email protected]> > > The Debian armhf architecture uses the ARM EABI hard-float variant, > whereas armel uses the soft-float variant. If the compiler used > to compile the kernel uses the __ARM_PCS_VFP ABI, the compiler > targets armhf architecture. > > v3 by Riku: Use gcc define instead of CONFIG_VFP > > Cc: [email protected] > Signed-off-by: Ben Hutchings <[email protected]> > Signed-off-by: Riku Voipio <[email protected]> > --- > scripts/package/builddeb | 11 ++++++++++- > 1 file changed, 10 insertions(+), 1 deletion(-) > > diff --git a/scripts/package/builddeb b/scripts/package/builddeb > index 88dbf23..146b74f 100755 > --- 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. Arnaud -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: https://lists.debian.org/[email protected]
