summaryrefslogtreecommitdiff
path: root/package/utils/bzip2
diff options
context:
space:
mode:
authorJo-Philipp Wich <jo@mein.io>2017-01-05 15:51:05 +0100
committerJo-Philipp Wich <jo@mein.io>2017-01-10 12:28:32 +0100
commit83b6bfc2357458f219872f97ed9c4894106131a1 (patch)
treec1a97fa91a76f33f2913f4645409954e36e96d7b /package/utils/bzip2
parentfe876e9ac6ae71d1150583b4406a8f50401635da (diff)
downloadmtk-20170518-83b6bfc2357458f219872f97ed9c4894106131a1.zip
mtk-20170518-83b6bfc2357458f219872f97ed9c4894106131a1.tar.gz
mtk-20170518-83b6bfc2357458f219872f97ed9c4894106131a1.tar.bz2
build: fix HOST_CONFIGURE_VARS placement
Instead of passing HOST_CONFIGURE_VARS as arguments to the configure script, pass it as environment variables which brings the logic in line with the behaviour of package-defaults.mk. The change is needed since passing environment variables as configure parameters only works with GNU autoconf which evaluates command line arguments looking like variable assignments. Doing the same with non-autoconf configure scripts is not guaranteed to work since such scripts might terminate due to unknown argument errors. One example case is the cmake configure script which bails out when called as "./configure LDFLAGS=..." but not when called as "LDFLAGS=... ./configure". Also change the SHELL override to CONFIG_SHELL in the default HOST_CONFIGURE_VARS as the former is not properly propagated through the various GNU configure invocations since it gets lost when configure re- executes itself. A prior attempt to change the variable placement had to be reverted due to the missing SHELL -> CONFIG_SHELL change, leading to misgenerated libtool executables in various packages. Signed-off-by: Jo-Philipp Wich <jo@mein.io>
Diffstat (limited to 'package/utils/bzip2')
0 files changed, 0 insertions, 0 deletions