-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Disabling mlogc breaks standalone build #900
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Disabling mlogc while enabling standalone comes directly from the mod security wiki on building with nginx: |
Hi @quanah, Are you able to compile ModSecurity without disable the mlogc? It seems ModSecurity is trying to find apr.h which is needed even without the mlogc. |
@zimmerle I already noted that w/o disabling mlogc, the build succeeds. It's the last line in my original comment. |
Do you mind to share your config.log ? You can use gist for that: |
Sorry for the delay, I had an upcoming vacation to prepare for and then take. ;) |
Playing with the options to configure, if --disable-mlogc is added, then configure is unable to find apr & apr-util. With --disable-mlogc specified: checking for libcurl config script... /opt/zimbra/common/bin/curl-config Without specifying --disable-mlogc: checking for libcurl config script... /opt/zimbra/common/bin/curl-config |
ok, tracked this down to disabling apache2 and mlogc. Although it appears that apache2 is required for building this out with nginx? doc is not clear on that. |
Hence https://github.com/SpiderLabs/ModSecurity/tree/libmodsecurity for an agnostic webserver library. |
@uxbod I'm not exactly sure what that comment means. The directions for building on nginx are to build standalone. Standalone should be without apache2 and without mlogc. However, if you specify such a thing, building modsecurity breaks. That seems to be a quite valid bug. |
@uxbod ah, after reading through the description, I see your point. However, given that it's not advised to use libmodsecurity at this time, it doesn't help much. ;) It would be nice to see this fixed in the 2.9 branch until 3.x is ready. |
@quanah - were you able to get past this issue? |
@gchorny I no longer work for Zimbra, so it's not on my radar to address. I've no idea if it remains pertinent to Zimbra's plans for the future. |
Standalone build depends on Apache. Disabling mlogc also disables Apache therefore breaks the build. For complete Apache independence please check on libModSecurity. Check #661 for further information. nginx connector that no longer needs the Standalone versions - |
If --disable-mlogc and --enable-standalone-module are passed to configure, the result is not buildable, with the following error:
If I remove the --disable-mlogc option, it compiles just fine.
The text was updated successfully, but these errors were encountered: