You are able to compile a previous version (in a *fresh* directory), lets say version 2.7.7?
I am asking that cause this "nested too deeply" is usually consequence of a circular dependency.
Not sure what is happening, but it seems to be a cross compiling issue, if it was the case, disable the status engine you will not help you.
Can you share your config.log ?
Are you using this:
After run the ./autogen and ./configure there should be a file named: "apache2/modsecurity_config_auto.h" inside this file, there is a definition: HAVE_SYS_UTSNAME_H. Set this definition to "0" and it should act like sys/utsname.h does not exist in your
Felipe "Zimmerle" Costa
Security Researcher, SpiderLabs
Trustwave | SMART SECURITY ON DEMAND
Is there a configure option to disable the status engine? so its not built? My compile process is stuck on that right now and I'd like to disable it so I can get things working then go back and add things in.
On 04/09/2014 08:10 AM, Derek Werthmuller wrote:
I Setup a clean build directory and now utsname.sys is found along with the signal.h and errno.h. But now I'm getting this "include nested too deeply" message.
Now I added the path to the path to utsname.sys to my makefile by using the TARGET_CPPFLAGS, its found in toolchain/include/sys
TARGET_CPPFLAGS += \
development/openwrt/staging_dir/toolchain-arm_arm1176jzf-s+vfp_gcc-4.8-linaro_uClibc-0.9.33.2_eabi/include/sys/signal.h:1:20: error: #include nested too deeply
make: *** [mod_security2_la-acmp.lo] Error 1
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate Build, Test & Deployment
Start a new project now. Try Jenkins in the cloud.
mod-security-developers mailing list
ModSecurity Services from Trustwave's SpiderLabs:
This transmission may contain information that is privileged, confidential, and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information
contained herein (including any reliance thereon) is strictly prohibited. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format.