Re: [mod-security-users] ModSecurity was not compiled with JSON support
Brought to you by:
victorhora,
zimmerletw
Menu
▾
▴
Re: [mod-security-users] ModSecurity was not compiled with JSON support
|
From: Eero V. <eer...@ik...> - 2020-01-20 13:46:51
|
Install libyajl2 package also. Anyway. I don't think that is installed that path. remove prefix from configure parameter. Eero On Mon, Jan 20, 2020 at 3:41 PM Dino Edwards via mod-security-users < mod...@li...> wrote: > The think that’s strange to me is the fact that it finds YAJL library at > /usr/local/lib/libyajl.so but the next message says that YAJL was > explicitly referenced but it was not found: > > > > configure: YAJL library found at: /usr/local/lib//libyajl.so > configure: error: YAJL was explicitly referenced but it was not found > > > > *From:* Eero Volotinen <eer...@ik...> > *Sent:* Monday, January 20, 2020 7:22 AM > *To:* mod...@li... > *Subject:* Re: [mod-security-users] ModSecurity was not compiled with > JSON support > > > > I think that package name is libyajl-dev in ubuntu and location is > standard, not /usr/local. > > > > Eero > > > > On Mon, Jan 20, 2020 at 2:20 PM Felipe Zimmerle <fe...@zi...> > wrote: > > Hi Dino, > > libyajl-dev was installed on "/usr/local" or "/usr" ? > > You may want to use github instead of the mailing list -- it seems > that we have more popularity there. > > Br., > F. > > > On Mon, Jan 20, 2020 at 7:45 AM Dino Edwards via mod-security-users > <mod...@li...> wrote: > > > > Hi, > > > > > > > > I’m getting the following error in my security audit log: > > > > > > > > "error":"ModSecurity was not compiled with JSON support. > > > > > > > > I’m using Ubuntu 18.04 and Modsecurity 3.0.3. I’ve installed the > libyajl-dev library. When trying to compile Modsecurity I get the following > output: > > > > > > > > ./configure --with-yajl="/usr/local/lib" > > > > checking for a BSD-compatible install... /usr/bin/install -c > > > > checking whether build environment is sane... yes > > > > checking for a thread-safe mkdir -p... /bin/mkdir -p > > > > checking for gawk... gawk > > > > checking whether make sets $(MAKE)... yes > > > > checking whether make supports nested variables... yes > > > > checking for g++... g++ > > > > checking whether the C++ compiler works... yes > > > > checking for C++ compiler default output file name... a.out > > > > checking for suffix of executables... > > > > checking whether we are cross compiling... no > > > > checking for suffix of object files... o > > > > checking whether we are using the GNU C++ compiler... yes > > > > checking whether g++ accepts -g... yes > > > > checking for style of include used by make... GNU > > > > checking dependency style of g++... gcc3 > > > > checking for gcc... gcc > > > > checking whether we are using the GNU C compiler... yes > > > > checking whether gcc accepts -g... yes > > > > checking for gcc option to accept ISO C89... none needed > > > > checking whether gcc understands -c and -o together... yes > > > > checking dependency style of gcc... gcc3 > > > > checking for ar... ar > > > > checking the archiver (ar) interface... ar > > > > checking whether make sets $(MAKE)... (cached) yes > > > > checking for pkg-config... /usr/bin/pkg-config > > > > checking pkg-config is at least version 0.9.0... yes > > > > configure: YAJL library found at: /usr/local/lib//libyajl.so > > > > configure: error: YAJL was explicitly referenced but it was not found > > > > root@aegis-waf-ovh:/opt/ModSecurity# ./configure > --with-yajl="/usr/local/lib /usr/local" > > > > checking for a BSD-compatible install... /usr/bin/install -c > > > > checking whether build environment is sane... yes > > > > checking for a thread-safe mkdir -p... /bin/mkdir -p > > > > checking for gawk... gawk > > > > checking whether make sets $(MAKE)... yes > > > > checking whether make supports nested variables... yes > > > > checking for g++... g++ > > > > checking whether the C++ compiler works... yes > > > > checking for C++ compiler default output file name... a.out > > > > checking for suffix of executables... > > > > checking whether we are cross compiling... no > > > > checking for suffix of object files... o > > > > checking whether we are using the GNU C++ compiler... yes > > > > checking whether g++ accepts -g... yes > > > > checking for style of include used by make... GNU > > > > checking dependency style of g++... gcc3 > > > > checking for gcc... gcc > > > > checking whether we are using the GNU C compiler... yes > > > > checking whether gcc accepts -g... yes > > > > checking for gcc option to accept ISO C89... none needed > > > > checking whether gcc understands -c and -o together... yes > > > > checking dependency style of gcc... gcc3 > > > > checking for ar... ar > > > > checking the archiver (ar) interface... ar > > > > checking whether make sets $(MAKE)... (cached) yes > > > > checking for pkg-config... /usr/bin/pkg-config > > > > checking pkg-config is at least version 0.9.0... yes > > > > configure: error: YAJL was explicitly referenced but it was not found > > > > root@aegis-waf-ovh:/opt/ModSecurity# ./configure > --with-yajl="/usr/local/lib" > > > > checking for a BSD-compatible install... /usr/bin/install -c > > > > checking whether build environment is sane... yes > > > > checking for a thread-safe mkdir -p... /bin/mkdir -p > > > > checking for gawk... gawk > > > > checking whether make sets $(MAKE)... yes > > > > checking whether make supports nested variables... yes > > > > checking for g++... g++ > > > > checking whether the C++ compiler works... yes > > > > checking for C++ compiler default output file name... a.out > > > > checking for suffix of executables... > > > > checking whether we are cross compiling... no > > > > checking for suffix of object files... o > > > > checking whether we are using the GNU C++ compiler... yes > > > > checking whether g++ accepts -g... yes > > > > checking for style of include used by make... GNU > > > > checking dependency style of g++... gcc3 > > > > checking for gcc... gcc > > > > checking whether we are using the GNU C compiler... yes > > > > checking whether gcc accepts -g... yes > > > > checking for gcc option to accept ISO C89... none needed > > > > checking whether gcc understands -c and -o together... yes > > > > checking dependency style of gcc... gcc3 > > > > checking for ar... ar > > > > checking the archiver (ar) interface... ar > > > > checking whether make sets $(MAKE)... (cached) yes > > > > checking for pkg-config... /usr/bin/pkg-config > > > > checking pkg-config is at least version 0.9.0... yes > > > > configure: YAJL library found at: /usr/local/lib//libyajl.so > > > > configure: error: YAJL was explicitly referenced but it was not found > > > > > > > > I would appreciate some help > > > > > > > > Thanks! > > > > _______________________________________________ > > mod-security-users mailing list > > mod...@li... > > https://lists.sourceforge.net/lists/listinfo/mod-security-users > > Commercial ModSecurity Rules and Support from Trustwave's SpiderLabs: > > http://www.modsecurity.org/projects/commercial/rules/ > > http://www.modsecurity.org/projects/commercial/support/ > > > > -- > Br., > Felipe Zimmerle > > > _______________________________________________ > mod-security-users mailing list > mod...@li... > https://lists.sourceforge.net/lists/listinfo/mod-security-users > Commercial ModSecurity Rules and Support from Trustwave's SpiderLabs: > http://www.modsecurity.org/projects/commercial/rules/ > http://www.modsecurity.org/projects/commercial/support/ > > _______________________________________________ > mod-security-users mailing list > mod...@li... > https://lists.sourceforge.net/lists/listinfo/mod-security-users > Commercial ModSecurity Rules and Support from Trustwave's SpiderLabs: > http://www.modsecurity.org/projects/commercial/rules/ > http://www.modsecurity.org/projects/commercial/support/ > |
