package/openocd: fix fallout after no-C++ fixups
Commit 4cd1ab158
(core: alternate solution to disable C++) made use of a
non-existent 'no' binary when C++ is not available in the toolchain.
However, some packages, like jimtcl as bundled in opeocd, really want to
find the binary that $CXX contains.
Revert openocd to use 'false' instead of 'no'.
Fixes:
http://autobuild.buildroot.org/results/cbd/cbd5ab97fb0659968ff628461130627cf1745955/
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
This commit is contained in:
parent
9feb6d982d
commit
5966e2dc54
|
@ -11,7 +11,12 @@ OPENOCD_LICENSE = GPL-2.0+
|
|||
OPENOCD_LICENSE_FILES = COPYING
|
||||
# 0002-configure-enable-build-on-uclinux.patch patches configure.ac
|
||||
OPENOCD_AUTORECONF = YES
|
||||
OPENOCD_CONF_ENV = CFLAGS="$(TARGET_CFLAGS) -std=gnu99"
|
||||
|
||||
# The bundled jimtcl really wants to find a existing $CXX, so feed it
|
||||
# false when we do not have one.
|
||||
OPENOCD_CONF_ENV = \
|
||||
$(if $(BR2_INSTALL_LIBSTDCPP),,CXX=false) \
|
||||
CFLAGS="$(TARGET_CFLAGS) -std=gnu99"
|
||||
|
||||
OPENOCD_CONF_OPTS = \
|
||||
--oldincludedir=$(STAGING_DIR)/usr/include \
|
||||
|
|
Loading…
Reference in a new issue