Re: [mod-security-users] modsecurity-apache_2.5.9 complie errors
Brought to you by:
victorhora,
zimmerletw
From: Brian R. <Bri...@br...> - 2009-03-17 15:28:47
|
Perhaps you need --with-apu= ? Clayton Dillard wrote: > Thanks for the tip to get around the apr issue Brian. I am having further issues installing ModSec 2.5.9 on Centos 5.2 x64 with Apache 2.0. > > configure: looking for Apache module support via DSO through APXS > configure: found apxs at /usr/local/apache2/bin/apxs > configure: checking httpd version > configure: httpd is recent enough > Use of uninitialized value in concatenation (.) or string at /usr/local/apache2/bin/apxs line 237. > checking for libpcre config script... /usr/bin/pcre-config > configure: using '-lpcre' for pcre Library > checking for libapr config script... /usr/bin/apr-1-config > configure: using ' -lpthread -ldl' for apr Library > checking for libapr-util config script... no > configure: *** apu library not found. > configure: error: apu library is required > > > > ----- Original Message ----- > From: "Brian Rectanus"<Bri...@br...> > To: "Anna Hopkins"<mol...@gm...> > Cc: mod...@li... > Sent: Thursday, March 12, 2009 2:53:35 PM GMT -05:00 US/Canada Eastern > Subject: Re: [mod-security-users] modsecurity-apache_2.5.9 complie errors > > There seems to be a bug in the configure script (variable name clash) > when using --with-apxs and without --with-apr. > > You can specify an empty --with-apr= to get around this without > specifying the full path to the apr config. This worked for me: > > ./configure \ > --with-apxs=/usr/local/apache2/bin/apxs \ > --with-apr= > > -B > > Anna Hopkins wrote: >> That seems to have done it. Thank you. >> >> Michael Caplan wrote: >>> Hi Anna, >>> >>> I ran into a similar problem. I think (still compiling) I got around >>> the problem by specifying full paths to apr and apu config tools: >>> >>> ./configure --with-apxs=/usr/local/apache2/bin/apxs --with-pcre=/usr >>> --with-apr=/usr/local/apache2/bin/apr-1-config >>> --with-apu=/usr/local/apache2/bin/apu-1-config >>> >>> Hope that helps! >>> >>> Mike >>> >>> >>> On Thu, 2009-03-12 at 09:20 -0700, Anna Hopkins wrote: >>> >>>> Have the requirements change for the new version? (error: apr library >>>> is required) >>>> I have had errors trying to compile this version. (see below) >>>> >>>>> ./configure --with-apxs=/usr/local/apache/bin/apxs >>>>> checking for g++... g++ >>>>> checking for C++ compiler default output file name... a.out >>>>> checking whether the C++ compiler works... yes >>>>> checking whether we are cross compiling... no >>>>> checking for suffix of executables... >>>>> 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 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 how to run the C preprocessor... gcc -E >>>>> checking for a BSD-compatible install... /usr/bin/install -c >>>>> checking whether ln -s works... yes >>>>> checking whether make sets $(MAKE)... yes >>>>> checking for ranlib... ranlib >>>>> checking for perl... /usr/local/bin/perl >>>>> checking for grep that handles long lines and -e... /usr/bin/grep >>>>> checking for egrep... /usr/bin/grep -E >>>>> checking for ANSI C header files... yes >>>>> checking for sys/types.h... yes >>>>> checking for sys/stat.h... yes >>>>> checking for stdlib.h... yes >>>>> checking for string.h... yes >>>>> checking for memory.h... yes >>>>> checking for strings.h... yes >>>>> checking for inttypes.h... yes >>>>> checking for stdint.h... yes >>>>> checking for unistd.h... yes >>>>> checking fcntl.h usability... yes >>>>> checking fcntl.h presence... yes >>>>> checking for fcntl.h... yes >>>>> checking limits.h usability... yes >>>>> checking limits.h presence... yes >>>>> checking for limits.h... yes >>>>> checking for stdlib.h... (cached) yes >>>>> checking for string.h... (cached) yes >>>>> checking for unistd.h... (cached) yes >>>>> checking for an ANSI C-conforming const... yes >>>>> checking for inline... inline >>>>> checking for C/C++ restrict keyword... __restrict >>>>> checking for size_t... yes >>>>> checking whether struct tm is in sys/time.h or time.h... time.h >>>>> checking for uint8_t... yes >>>>> checking for stdlib.h... (cached) yes >>>>> checking for GNU libc compatible malloc... yes >>>>> checking for working memcmp... yes >>>>> checking for atexit... yes >>>>> checking for fchmod... yes >>>>> checking for getcwd... yes >>>>> checking for memset... yes >>>>> checking for strcasecmp... yes >>>>> checking for strchr... yes >>>>> checking for strdup... yes >>>>> checking for strerror... yes >>>>> checking for strncasecmp... yes >>>>> checking for strrchr... yes >>>>> checking for strstr... yes >>>>> checking for strtol... yes >>>>> configure: looking for Apache module support via DSO through APXS >>>>> configure: found apxs at /usr/local/apache/bin/apxs >>>>> configure: checking httpd version >>>>> configure: httpd is recent enough >>>>> checking for libpcre config script... /usr/local/bin/pcre-config >>>>> configure: using '-L/usr/local/lib -lpcre' for pcre Library >>>>> checking for libapr config script... /usr/local/apache/bin/apxs >>>>> apxs:Error: Unknown option: -. >>>>> apxs:Error: Unknown option: -. >>>>> apxs:Error: Unknown option: f. >>>>> apxs:Error: Unknown option: -. >>>>> apxs:Error: Unknown option: f. >>>>> Usage: apxs -g [-S<var>=<val>] -n<modname> >>>>> apxs -q [-S<var>=<val>]<query> ... >>>>> apxs -c [-S<var>=<val>] [-o<dsofile>] [-D<name>[=<value>]] >>>>> [-I<incdir>] [-L<libdir>] [-l<libname>] [-Wc,<flags>] >>>>> [-Wl,<flags>] [-p]<files> ... >>>>> apxs -i [-S<var>=<val>] [-a] [-A] [-n<modname>]<dsofile> ... >>>>> apxs -e [-S<var>=<val>] [-a] [-A] [-n<modname>]<dsofile> ... >>>>> apxs:Error: Unknown option: -. >>>>> Usage: apxs -g [-S<var>=<val>] -n<modname> >>>>> apxs -q [-S<var>=<val>]<query> ... >>>>> apxs -c [-S<var>=<val>] [-o<dsofile>] [-D<name>[=<value>]] >>>>> [-I<incdir>] [-L<libdir>] [-l<libname>] [-Wc,<flags>] >>>>> [-Wl,<flags>] [-p]<files> ... >>>>> apxs -i [-S<var>=<val>] [-a] [-A] [-n<modname>]<dsofile> ... >>>>> apxs -e [-S<var>=<val>] [-a] [-A] [-n<modname>]<dsofile> ... >>>>> apxs:Error: Unknown option: -. >>>>> Usage: apxs -g [-S<var>=<val>] -n<modname> >>>>> apxs -q [-S<var>=<val>]<query> ... >>>>> apxs -c [-S<var>=<val>] [-o<dsofile>] [-D<name>[=<value>]] >>>>> [-I<incdir>] [-L<libdir>] [-l<libname>] [-Wc,<flags>] >>>>> [-Wl,<flags>] [-p]<files> ... >>>>> apxs -i [-S<var>=<val>] [-a] [-A] [-n<modname>]<dsofile> ... >>>>> apxs -e [-S<var>=<val>] [-a] [-A] [-n<modname>]<dsofile> ... >>>>> apxs:Error: Unknown option: -. >>>>> Usage: apxs -g [-S<var>=<val>] -n<modname> >>>>> apxs -q [-S<var>=<val>]<query> ... >>>>> apxs -c [-S<var>=<val>] [-o<dsofile>] [-D<name>[=<value>]] >>>>> [-I<incdir>] [-L<libdir>] [-l<libname>] [-Wc,<flags>] >>>>> [-Wl,<flags>] [-p]<files> ... >>>>> apxs -i [-S<var>=<val>] [-a] [-A] [-n<modname>]<dsofile> ... >>>>> apxs -e [-S<var>=<val>] [-a] [-A] [-n<modname>]<dsofile> ... >>>>> configure: *** apr library not found. >>>>> configure: error: apr library is required >>>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are >>>> powering Web 2.0 with engaging, cross-platform capabilities. Quickly and >>>> easily build your RIAs with Flex Builder, the Eclipse(TM)based development >>>> software that enables intelligent coding and step-through debugging. >>>> Download the free 60 day trial.http://p.sf.net/sfu/www-adobe-com >>>> _______________________________________________ >>>> mod-security-users mailing list >>>> mod...@li... >>>> https://lists.sourceforge.net/lists/listinfo/mod-security-users >>>> Commercial ModSecurity Appliances, Rule Sets and Support: >>>> http://www.modsecurity.org/breach/index.html >>>> >>> >>> >>> Please consider the environment before printing this email. >>> >>> >>> E-mail messages may contain viruses, worms, or other malicious code. By reading the message and opening any attachments, the recipient accepts full responsibility for taking protective action against such code. Henry Schein is not liable for any loss or damage arising from this message. >>> >>> The information in this email is confidential and may be legally privileged. It is intended solely for the addressee(s). Access to this e-mail by anyone else is unauthorized. >>> >>> >>> > > -- > Brian Rectanus > Breach Security > > ------------------------------------------------------------------------------ > Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are > powering Web 2.0 with engaging, cross-platform capabilities. Quickly and > easily build your RIAs with Flex Builder, the Eclipse(TM)based development > software that enables intelligent coding and step-through debugging. > Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com > _______________________________________________ > mod-security-users mailing list > mod...@li... > https://lists.sourceforge.net/lists/listinfo/mod-security-users > Commercial ModSecurity Appliances, Rule Sets and Support: > http://www.modsecurity.org/breach/index.html -- Brian Rectanus Breach Security |