boot/arm-trusted-firmware: don't pass TARGET_CONFIGURE_OPTS when building
authorThomas Petazzoni <thomas.petazzoni@bootlin.com>
Fri, 14 Sep 2018 15:33:24 +0000 (17:33 +0200)
committerThomas Petazzoni <thomas.petazzoni@bootlin.com>
Thu, 11 Oct 2018 07:28:54 +0000 (09:28 +0200)
commitbaa450e0365e9a1c45d7b9197987853e1affcff9
treeba06127ac5d0b14cad1a310a09b3a17e0761ba95
parent58e9d24952253a12dbb2b25e7470b3397b0eface
boot/arm-trusted-firmware: don't pass TARGET_CONFIGURE_OPTS when building

Passing CFLAGS/CPPFLAGS in the environment confuses the ATF version
provided by Marvell, and we in fact only need to pass CROSS_COMPILE,
which is already in ARM_TRUSTED_FIRMWARE_MAKE_OPTS.

We however keep TARGET_MAKE_ENV so that the PATH with $(HOST_DIR) is
kept.

This change has been tested with all current defconfigs that build
ATF:

 - arm_juno
 - bananapi_m64
 - freescale_imx8mqevk
 - friendlyarm_nanopi_a64
 - friendlyarm_nanopi_neo2
 - nitrogen8m
 - olimex_a64_olinuxino
 - orangepi_pc2
 - orangepi_prime
 - orangepi_win
 - orangepi_zero_plus2
 - pine64
 - pine64_sopine
 - solidrun_macchiatobin_mainline
 - solidrun_macchiatobin_marvell
 - zynqmp_zcu106

Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
boot/arm-trusted-firmware/arm-trusted-firmware.mk