kumquat-buildroot/package/libmodsecurity/Config.in
Fabrice Fontaine 97bdc0616c package/libmodsecurity: needs dynamic library
Commit 9fc652a373 was incomplete as
mbedtls can be pulled in libcurl through libssh2 resulting in the
following build failure:

/home/autobuild/autobuild/instance-4/output-1/host/lib/gcc/powerpc64le-buildroot-linux-musl/11.3.0/../../../../powerpc64le-buildroot-linux-musl/bin/ld: /home/autobuild/autobuild/instance-4/output-1/host/powerpc64le-buildroot-linux-musl/sysroot/usr/lib//libmbedcrypto.a(md5.c.o): in function `mbedtls_md5_init':
md5.c:(.text+0x0): multiple definition of `mbedtls_md5_init'; ../../src/.libs/libmodsecurity.a(libmbedtls_la-md5.o):md5.c:(.text+0x0): first defined here

Fixes:
 - http://autobuild.buildroot.org/results/4c235e46188f23d1a48297f4e5942cec7b25959a

Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2023-02-21 09:30:41 +01:00

25 lines
976 B
Plaintext

config BR2_PACKAGE_LIBMODSECURITY
bool "libmodsecurity"
depends on BR2_INSTALL_LIBSTDCPP
depends on BR2_TOOLCHAIN_HAS_THREADS
# libmodsecurity embeds several mbedtls source files, causing
# various issues when static linking and other dependencies of
# libmodsecurity in turn use mbedtls
depends on !BR2_STATIC_LIBS
select BR2_PACKAGE_PCRE2
help
Libmodsecurity is one component of the ModSecurity
v3 project. The library codebase serves as an
interface to ModSecurity Connectors taking in web
traffic and applying traditional ModSecurity
processing. In general, it provides the capability
to load/interpret rules written in the ModSecurity
SecRules format and apply them to HTTP content
provided by your application via Connectors.
https://github.com/SpiderLabs/ModSecurity
comment "libmodsecurity needs a toolchain w/ C++, threads, dynamic library"
depends on !BR2_INSTALL_LIBSTDCPP || \
!BR2_TOOLCHAIN_HAS_THREADS || BR2_STATIC_LIBS