On 2011-07-07 at 16:54, Yadin Flammer ( [email protected] ) said:
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

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

--enable-apache2=/usr/sbin/apxs is correct for centos 5.x

You shouldn't have to tweak any environment variables.


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.

If all you need is the module, and you're not saving tickets (CosignGetKerberosTickets) then you don't have to worry about kerberos - that's what the cosign cgi's are there for (and even then, without looking at the code, --enable-krb probably only applies to the login cgi).

Otherwise: --enable-krb=/usr/kerberos/bin/krb5-config

And if you need to use CosignKerberosSetupGSS, then --with-gss by itself will work.

Make sure you're doing a 'make filters' and not just 'make'.

--andy
------------------------------------------------------------------------------
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