On Jul 7, 2011, at 4:54 PM, Yadin Flammer wrote:

> *resend as original seems to have failed...*
> Hello,
> 
> I have encountered lots of issues working with cosign as the installation 
> doesn’t seem to be documented anywhere.  3rd party sites have managed to get 
> me muddled through on IIS 7 and Ubuntu 11, but now I’m stuck on CentOS 5.  
> 
> In both Ubutu and CentOS there was need of flags on the ./configure to make 
> it work, otherwise it would fail as it was unable to find apache2 for some 
> reason.
> Ubuntu 11:  ./configure --enable-apache2=/usr/bin/apxs2
> CentOS 5:  ./configure --enable-apache2=/usr/sbin/apachectl

The apachectl utility is, as I'm sure you're aware, used to control the httpd 
process itself. The apxs utility is used to configure and build apache modules. 
Try replacing the CentOS command with:

./configure --enable-apache2=/usr/sbin/apxs

and see if you get any farther.

andrew



> 
> After this, make and make install worked fine on Ubuntu and I was off and 
> running.  On CentOS however, make fails:
> 
> $ make
> cd filters/apache2; make  all
> make[1]: Entering directory `/home/yxf4/cosign-3.1.2/filters/apache2'
> /usr/sbin/apachectl -c  -I../../common  -I/usr/include -I../../libsnet  
> -I../common  -L/usr/lib  -lnsl  -lssl -lcrypto   mod_cosign.c 
> ../common/connect.c ../common/cookiefs.c ../common/sparse.c 
> ../../common/argcargv.c ../../common/fbase64.c ../../common/mkcookie.c 
> ../../common/rate.c ../../version.c ../../libsnet/snet.c
> httpd: illegal option -- I
> Usage: /usr/sbin/httpd [-D name] [-d directory] [-f file]
>                        [-C "directive"] [-c "directive"]
>                        [-k start|restart|graceful|graceful-stop|stop]
>                        [-v] [-V] [-h] [-l] [-L] [-t] [-S]
> Options:
>   -D name            : define a name for use in <IfDefine name> directives
>   -d directory       : specify an alternate initial ServerRoot
>   -f file            : specify an alternate ServerConfigFile
>   -C "directive"     : process directive before reading config files
>   -c "directive"     : process directive after reading config files
>   -e level           : show startup errors of level (see LogLevel)
>   -E file            : log startup errors to file
>   -v                 : show version number
>   -V                 : show compile settings
>   -h                 : list available command line options (this page)
>   -l                 : list compiled in modules
>   -L                 : list available configuration directives
>   -t -D DUMP_VHOSTS  : show parsed settings (currently only vhost settings)
>   -S                 : a synonym for -t -D DUMP_VHOSTS
>   -t -D DUMP_MODULES : show all loaded modules 
>   -M                 : a synonym for -t -D DUMP_MODULES
>   -t                 : run syntax check for config files
> make[1]: *** [mod_cosign.la] Error 1
> make[1]: Leaving directory `/home/yxf4/cosign-3.1.2/filters/apache2'
> make: *** [filters/apache2] Error 2
>  
> >From the look of that, the make script is trying to use an illegal 
> >parameter, but I can’t understand why this would be the case when it worked 
> >fine on Ubuntu and apache is apache AFAIK.  I’m sure someone has managed to 
> >install cosign on CentOS/Red Hat, so I’d appreciate if such a person could 
> >share the magic sauce needed.  I only found once reference to this on the 
> >web that suggested additional flags for the configure, but they don’t work 
> >either:
> 
> $ ./configure --enable-apache2=/usr/sbin/apxs CFLAGS=`apr-1-config --cflags` 
> CPPFLAGS="`apr-1-config --cppflags` -I/usr/include/apr-1/"
> configure: error: unrecognized option: -pthread
> 
> 
> Also, looking back through the configure results, I just noticed these issues:
> httpd: illegal option -- q
> ./configure: line 3179: /: is a directory
> kerberos not enabled
> 
> I need kerberos to work with cosign, that is the entire point of this, so 
> that message worries me.  It gives no indication for any of these errors, but 
> the illegal option --q  one is repeated 3 times followed by the usage dump.
> 
> Any help is greatly appreciated.  Once I have working step by step 
> instructions that work I plan to post them on the wiki since I can’t seem to 
> find any documentation of this stuff.
> 
> Thanks!
> 
> -------------------------------------------------------------------
>   Yadin Flammer - Systems Administrator
>   College of Arts & Architecture, Penn State University
>   228 Borland Building              Office Phone: 814-865-0990
>   University Park, PA 16802         Dept. Phone:  814-865-1571
>   Email: [email protected]               Dept. Fax:    814-863-6227
> !DSPAM:4e161d4b86061804284693!
> ------------------------------------------------------------------------------
> All of the data generated in your IT infrastructure is seriously valuable.
> Why? It contains a definitive record of application performance, security 
> threats, fraudulent activity, and more. Splunk takes this data and makes 
> sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-d2d-c2
> 
> !DSPAM:4e161d4b86061804284693!
> _______________________________________________
> Cosign-discuss mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/cosign-discuss
> 
> 
> !DSPAM:4e161d4b86061804284693!


------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security 
threats, fraudulent activity, and more. Splunk takes this data and makes 
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
Cosign-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/cosign-discuss

Reply via email to