This update solves two issues:
1) Incompatibility with the combination of using Target mpc85xx and uclibc at the same time[1].
- For now, Boost is disabled when the respective combination is detected.
2) The selection of Boost.Locale was not activating the build with full language support.
[1] - https://github.com/openwrt/packages/issues/1621
Signed-off-by: Carlos Ferreira <carlosmf.pt@gmail.com>
Adds YAJL (Yet Another JSON Library), a C library for parsing JSON.
Includes patches for uClibc support.
Improved from version used internally at Who's On My WiFi since Feb 2014.
Adds myself as maintainer.
Signed-off-by: Charles Southerland <charlie@stuphlabs.com>
When sys/poll.h gets included it results in a warning, to include
poll.h. All warnings are treated as errors by liblo.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Let `./configure` assume C99 compliant `snprintf()` and `vsnprintf()` functions
by passing the required cache variables via `CONFIGURE_VARS`.
Fixes fortify-source related undeclared function errors when compiling the
`tests/` directory.
Signed-off-by: Jo-Philipp Wich <jow@openwrt.org>
When only boost is selected without any specific boost library no *.so
file will be build and the InstallDev part is failing. Instead of
checking if there is a lib directory just try to copy the libs and do
not fail in case of an error.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
This commit addresses two issues encountered while building pthsem for
x86_64/musl:
1) Autoconf incorrectly assumes a broken Glibc and thus falls back
to Linux compatibility code which runs into an unsupported
platform error with musl libc. Since musl provides a proper
implementation of `sigaltstack(2)`, force configure to use the
POSIX compliant code when musl libc is used.
2) The `pth_syscall.c` file undefines various libc function names
which breaks the indirection set up by fortify-source headers,
therefore forcibly disable fortify source in the OpenWrt Makefile.
Signed-off-by: Jo-Philipp Wich <jow@openwrt.org>
Depending on both, GnuTLS and OpenSSL doesn't make sense, we should
use either TLS implementation but not both. Use GnuTLS for now and
get rid of OpenSSL dependency by explicitely telling the package's
build-system to do so using CONFIGURE_ARGS.
If future uses of libmicrohttpd require OpenSSL, it probably makes
most sense to build several variants of the package, i.e.
libmicrohttpd-openssl as well as libmicrohttpd-gnutls. As with most
packages making use of any TLS implementation, these are build-time
decissions resulting in conflicting variants of the same package
which cannot be installed simultanously.
Signed-off-by: Daniel Golle <daniel@makrotopia.org>
When fortify source is enabled, the c-ares configure script will abort with:
configure: CFLAGS error: CFLAGS may only be used to specify C compiler flags, not macro definitions. Use CPPFLAGS for: -D_FORTIFY_SOURCE=1
Change the OpenWrt Makefile to move any -D flags from TARGET_CFLAGS to
TARGET_CPPFLAGS in order to satisfy `configure`.
Signed-off-by: Jo-Philipp Wich <jow@openwrt.org>
