Bug 887135 – dev-libs/modsecurity-3.0.12 fails to compile (DASH-SYSTEM): configure: error: YAJL was explicitly referenced but it was not found

• Status: CONFIRMED
• Product: Gentoo Linux

[Description Agostino Sarubbo 2022-12-19 09:16:19 UTC]

https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/

Issue: dev-libs/modsecurity-3.0.8 fails to compile (DASH-SYSTEM).
Discovered on: amd64 (internal ref: dash_tinderbox)

NOTE:
(DASH-SYSTEM) in the summary means that the bug was found on a machine that runs /bin/sh as dash but this bug MAY or MAY NOT BE related to dash.

[Comment 1 Agostino Sarubbo 2022-12-19 09:16:21 UTC]

Created attachment 843635 [details]
build.log

build log and emerge --info

[Comment 2 Agostino Sarubbo 2022-12-19 09:16:22 UTC]

Created attachment 843637 [details]
1-config.log

1-config.log

[Comment 3 Agostino Sarubbo 2022-12-19 09:16:23 UTC]

Error(s) that match a know pattern in addition to what has been reported in the summary:


configure: error: YAJL was explicitly referenced but it was not found
configure: error: YAJL was explicitly referenced but it was not found

[Comment 4 Agostino Sarubbo 2024-02-14 08:20:58 UTC]

dash_tinderbox has reproduced this issue with version 3.0.12 - Updating summary.

[Comment 5 zurabid2016 2025-04-14 13:38:00 UTC]

Can reproduce. modsecurity uses a *lot* of Bash == operators in build/*.m4 files. CONFIG_SHELL must therefore be set to "${BROOT}/bin/bash" as a workaround.

[Comment 6 zurabid2016 2025-04-15 17:34:17 UTC]

See also https://github.com/owasp-modsecurity/ModSecurity/pull/3359.

It removes Bashisms from M4 macros and should enable building ModSecurity on non-Bash systems.