|
From: Derek & V. <the...@gm...> - 2014-04-13 20:12:43
|
Well I got it working for the 2.7.7 version, it turns out that the path I used to utsname.h was just a header file that referenced other locations. So I searched for other copies of the utsname.h and made sure that they were complete files. Then it finished compiling. I don't know if the image works yet but I know it builds. Going to try the 2.8.0 RC-1 and if that builds I'll try that image on the openwrt powered Pi. Thanks for your help Felipe. I'll be sending a note to get advice on what CRS rules make the most sense on a forward prox y. Derek On 04/11/2014 08:43 AM, Felipe Costa wrote: > Hi Derek, > > 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: > http://wiki.openwrt.org/doc/howto/build ? > > 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 platform. > > Br., > *Felipe "Zimmerle" Costa* > Security Researcher, SpiderLabs > > *Trustwave* | SMART SECURITY ON DEMAND > www.trustwave.com <http://www.trustwave.com/> > > > On Apr 10, 2014, at 11:24 PM, Derek & Vicky <the...@gm... > <mailto:the...@gm...>> > wrote: > >> 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. >> >> Thanks >> Derek >> >> On 04/09/2014 08:10 AM, Derek Werthmuller wrote: >>> 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 <FC...@tr... >>> <mailto:FC...@tr...>> wrote: >>> >>> Hi Derek, >>> >>> On Apr 4, 2014, at 1:33 PM, Derek Werthmuller >>> <the...@gm... <mailto:the...@gm...>> >>> 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 >>> www.trustwave.com <http://www.trustwave.com/> >>> >>> >>> >>> ------------------------------------------------------------------------ >>> >>> 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...@li... >>> <mailto:mod...@li...> >>> https://lists.sourceforge.net/lists/listinfo/mod-security-developers >>> ModSecurity Services from Trustwave's SpiderLabs: >>> https://www.trustwave.com/spiderLabs.php >>> >>> >> >> ------------------------------------------------------------------------------ >> 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. >> http://p.sf.net/sfu/13600_Cloudbees_______________________________________________ >> mod-security-developers mailing list >> mod...@li... >> https://lists.sourceforge.net/lists/listinfo/mod-security-developers >> ModSecurity Services from Trustwave's SpiderLabs: >> https://www.trustwave.com/spiderLabs.php > > > ------------------------------------------------------------------------ > > 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. > > > ------------------------------------------------------------------------------ > 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. > http://p.sf.net/sfu/13600_Cloudbees > > > _______________________________________________ > mod-security-developers mailing list > mod...@li... > https://lists.sourceforge.net/lists/listinfo/mod-security-developers > ModSecurity Services from Trustwave's SpiderLabs: > https://www.trustwave.com/spiderLabs.php |
