[pubcookie-users] Setting up on Mac OS X 10.5 and test server

[Kuohsing Tang]

Hello Chris,

I am using OS X 10.5 client and ran into a "make" problem today.

A similar issue was asked over a year ago on this list but no clear 
solution was found (search for "[pubcookie-users] Problem compiling 
Pubcookie 3.3.2c on Debian Etch x86", first posted on 2007/03/22). 
However the two issues seem different even though they both generate the 
same error.


My error on OS X 10.5 (stock Apache 2) with pubcookie 3.3.2 & 3.3.3:
****************
/usr/share/httpd/build/special.mk:27: /usr/build/rules.mk: No such file 
or directory
[...snip...]
****************

I am guessing this is the same problem you have. I finished the 
installation by modifying "module/Makefile" twice. I have not got my 
certificate yet so I can't test if this is really working. Maybe someone 
can let me know before I continue with a faulty installation :p

I don't know enough about how this works but I was able to trace back to 
this line in "configure"(~line 3810):

APACHE_PREFIX=`$APXS -q PREFIX`

When running "apxs -q PREFIX" in 10.5 it returns "/usr" which is what 
caused the error since there is no such file at /usr/build/rules.mk but 
instead at /usr/share/httpd/build/rules.mk.

So I manually modified "module/Makefile" (see below) after running 
configure *AND* after running make.


module/Makefile:
**** change these 3 values to "/usr/share/httpd"
top_dir      = /usr
top_srcdir   = /usr
top_builddir = /usr
****

Again, I have not tested this yet and do not know if the installation 
was successful. I do not know what the actual dir values should have 
been or the cause of the "incorrect" apxs prefix output. I'll appreciate 
if someone can let me know that this will or will not work. Thanks.

-David







Chris Moorehead wrote:

> I'm trying to find anyone with experience in getting pubcookie to work 

> on MacOSX 10.5 (client).  I've made a few attempts but can't get the 

> install to make.

> 

> Also right now this box is being built up while the old server continues 

> to chugs on.  So my test box does not have the name it will be using 

> when it replaces the old box (or the ssl certificates).  Is there any 

> way of getting pubcookie to work with a temporary self-signed 

> certificate and a different name?

> 

> Any pointers would be very appreciated.

> 

> Chris Moorehead

> CAUP Computing

> _______________________________________________

> pubcookie-users mailing list

> pubcookie-users at u.washington.edu

> http://mailman1.u.washington.edu/mailman/listinfo/pubcookie-users