Felipe,
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 += \
        -I$(STAGING_DIR)/usr/include/libxml2 \
        -I$(STAGING_DIR)/usr/share/build/ \
        -I$(STAGING_DIR)/usr/include/apache \
        -I$(STAGING_DIR)/usr/include/apr-1 \
        -I$(STAGING_DIR)/usr/lib/ \
        -I$(TOOLCHAIN_DIR)/include/sys \

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
 #include <signal.h>
                    ^
make[5]: *** [mod_security2_la-acmp.lo] Error 1

Any ideas how to get past this error, I'm not really sure what it means.

Thanks
 Derek

On Fri, Apr 4, 2014 at 12:56 PM, Felipe Costa <FCosta@trustwave.com> wrote:
Hi Derek,

On Apr 4, 2014, at 1:33 PM, Derek Werthmuller <thewerthfam@gmail.com>
 wrote:

Felipe,
That utsname_autotools gave me the "msc_status_engine.c:137:26: error: storage size of 'u' isn't known
make[5]: *** [mod_security2_la-msc_status_engine.lo] Error 1
"
Error again.

Thanks for test.

Can you double check if you are really on the "utsname_autotools" branch? Can you try it in a fresh directory? 

It seems to me that this error is part of "master", as this line 137 is where this structure is used at the branch master. In utsname_autotools, if happens, it should be on line 140 (if i am not mistaken).

Can you double check that? Also, can you check if there is something similar to "#define HAVE_SYS_UTSNAME_H 1" in your config.log ?


Should I try the other fix version you setup?
Lets have this second chance on the branch: "msc_status_engine" first. I want to push this to master, but first i want to make sure that it is working for everybody.

Thanks for helping us to sort this out ;)


Br.,
Felipe "Zimmerle" Costa
Security Researcher, SpiderLabs

Trustwave | SMART SECURITY ON DEMAND





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.

------------------------------------------------------------------------------

_______________________________________________
mod-security-developers mailing list
mod-security-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mod-security-developers
ModSecurity Services from Trustwave's SpiderLabs:
https://www.trustwave.com/spiderLabs.php