Fixes part of issue #14921.
When $(FPIC) gets added to TARGET_CFLAGS (for instance), we can
count on $(TARGET_CFLAGS) in turn being quoted when it gets
expanded. But there are a few places where $(FPIC) gets
expanded directly into environment variables passed on the
command line, such as when setting lt_cv_* variables as in this
case.
It's wrong to assume that the expansion of $(FPIC) won't require
quoting (such as it containing spaces) if it has multiple compiler
flags.
Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
PKG_NAME:=libredblack
PKG_VERSION:=1.3
-PKG_RELEASE:=3
+PKG_RELEASE:=4
PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.gz
PKG_SOURCE_URL:=@SF/libredblack
endef
CONFIGURE_ARGS += --without-rbgen
-CONFIGURE_VARS += lt_cv_prog_cc_pic=$(FPIC)
+CONFIGURE_VARS += lt_cv_prog_cc_pic="$(FPIC)"
MAKE_FLAGS += CFLAGS="$(TARGET_CFLAGS)"
define Build/InstallDev
PKG_NAME:=madplay
PKG_VERSION:=0.15.2b
-PKG_RELEASE:=9
+PKG_RELEASE:=10
PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.gz
PKG_SOURCE_URL:=@SF/mad \
--with-alsa
CONFIGURE_VARS += \
- lt_prog_compiler_pic=$(FPIC)
+ lt_prog_compiler_pic="$(FPIC)"
MAKE_FLAGS += CFLAGS="$(TARGET_CFLAGS)"