From 29ad9e0a0a93a60a1118eb0e8cb6a14df147320f Mon Sep 17 00:00:00 2001 From: Dave Reisner Date: Tue, 6 Sep 2011 09:29:52 -0400 Subject: makepkg: unset variables as per !{make,build}flags Don't just set the flag variables to zero length strings, actually unset them from the environment. This fixes issues with broken gnu Makefies that use ?= for assigment, where the presence of a var is enough to make this condition avoid assignment. Signed-off-by: Dave Reisner Signed-off-by: Dan McGee --- scripts/makepkg.sh.in | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/scripts/makepkg.sh.in b/scripts/makepkg.sh.in index 2f06b9b3..3174b0c7 100644 --- a/scripts/makepkg.sh.in +++ b/scripts/makepkg.sh.in @@ -864,14 +864,12 @@ run_function() { # clear user-specified buildflags if requested if [[ $(check_option buildflags) = "n" ]]; then - CFLAGS="" - CXXFLAGS="" - LDFLAGS="" + unset CFLAGS CXXFLAGS LDFLAGS fi # clear user-specified makeflags if requested if [[ $(check_option makeflags) = "n" ]]; then - MAKEFLAGS="" + unset MAKEFLAGS fi msg "$(gettext "Starting %s()...")" "$pkgfunc" -- cgit v1.2.3-70-g09d2