On Dec 23, 2008, at 7:36 PM, Mark Montague wrote: > On Tue, Dec 23, 2008 17:14, Trek Glowacki <pietr...@umich.edu> wrote: >> Are there any directions for building the cosign filter and >> cosignd specifically on MacOS 10.5 (client)? >> > > The last official release of cosign predates the release of Leopard, > so be sure to use cosign 2.1.0rc2, which is available from: > > http://sourceforge.net/project/showfiles.php?group_id=170747&package_id=194945 > > > I was able to build the cosign filter for Apache HTTPD 2 under MacOS > 10.5.6 by running: > > ./configure --enable-apache2=/usr/sbin/apxs > make > > Note, however, that this will result in a single-architecture Apache > HTTPD module that is for whatever architecture you built it on: > > $ file ./mod_cosign.so > ./mod_cosign.so: Mach-O bundle i386 > $
Hey Mark, all, 2.1.0rc2 does indeed build properly on leopard client and without any additional options and the build is for an arch of i386 $ file mod_cosign.so mod_cosign.so: Mach-O bundle i386 The included install of Apache won't start with this bundle, however. Running configtest shows that Apache wants some other architecture than what builds by default. $ apachectl configtest httpd: Syntax error on line 116 of /private/etc/apache2/httpd.conf: Cannot load /usr/libexec/apache2/mod_cosign.so into server: dlopen(/ usr/libexec/apache2/mod_cosign.so, 10): no suitable image found. Did find:\n\t/usr/libexec/apache2/mod_cosign.so: mach-o, but wrong architecture The machine I'm building on (a 2007 Macbook) is definitely i386: $ arch i386 I followed Dave Pugh's directions on the wiki for building for OS X Server(http://webapps.itcs.umich.edu/cosign/index.php/Mac_OS_X_Installation_Notes ) which involves editing the makefile (similar to what you suggested below) to specifically build an x86_64. Oddly, the x86_64 build of cosign seems to *not* cause Apache to complain at startup, but stops the other parts of cosign (cosignd and monsterd) from building and return architecture warnings. I've used the directions for building a universal binary and all the parts are building happily now. It seems like a universal build is the way to go for Leopard. > Finally, note that cosignd, monsterd, and the CGI are only needed if > you are setting up your own central weblogin servers. If you are at > an institution that already has central weblogin servers set up, you > will only need the filter (mod_cosign.so). I'm setting up cosign in an entirely new environment (no existing central auth servers), so we do need all the parts of cosign. The directions for setting up a new institution seem a bit piecemeal right now, but we're making progress. Thanks, Trek ------------------------------------------------------------------------------ _______________________________________________ Cosign-discuss mailing list Cosign-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/cosign-discuss
