Comments on: Compiling Apache in 64 bits mode on Snow Leopard

By: Compiling and install Apache 2 for Mac OS X Snow Leopard | pwn3d

Compiling and install Apache 2 for Mac OS X Snow Leopard | pwn3d — Mon, 06 Feb 2012 16:07:33 +0000

[...] use directions from DIY Mac Server instead, they adhere to using /usr/local/ and I believe it’s a better setup. [...]

By: Richard

Richard — Thu, 10 Feb 2011 06:12:12 +0000

@Robert, did you install XCode (developer tools)? You can find it on your OS X install DVD or download it from developer.apple.com

By: Robert

Robert — Thu, 10 Feb 2011 05:21:21 +0000

I keep getting this error:

configuring package in srclib/apr now
checking build system type… i386-apple-darwin10.6.0
checking host system type… i386-apple-darwin10.6.0
checking target system type… i386-apple-darwin10.6.0
Configuring APR library
Platform: i386-apple-darwin10.6.0
checking for working mkdir -p… yes
APR Version: 1.4.2
checking for chosen layout… DIYMacServer
checking for gcc… no
checking for cc… no
checking for cl.exe… no
configure: error: in `/Users/Robert/downloads/httpd-2.2.17/srclib/apr’:
configure: error: no acceptable C compiler found in $PATH
See `config.log’ for more details.
configure failed for srclib/apr

By: Scott Benton

Scott Benton — Fri, 03 Sep 2010 16:29:55 +0000

@Richard Thanks for the reply. Yeah, I decided that prefork was prob. my best bet as it seems to offer better compatibility. Good to know that I was making sense of this overall though. Great post and thanks again.

By: Richard

Richard — Fri, 03 Sep 2010 16:11:42 +0000

@Scott, no you aren’t missing much. If you look at the target market we are aiming for is the Mac mini. Those are still limited to two cores, in which case prefork still performs the best. If you have a quad core or better then you can switch to worker.

But to really benefit from this you’ll need to be having a very busy site. If you are just running Apache on your MacBook for development purposes it does not really matter I think.

By: Scott Benton

Scott Benton — Fri, 03 Sep 2010 15:08:52 +0000

Hey all. I’m getting ready to roll out apache 2.2.16 on a MacBook Pro, core 2 duo processor. I’m noticing all of the instructions here are to specify -with-mpm=prefork. Just wondering why this is, as from reading the MPM summaries at Apache, it seems to me as if the worker MPM is better optimized for most of the recent Mac chips (core 2 duo and later). Also, if you google “mpm prefork vs worker” you will find some benchmark testing that indicates worker is more efficient. Just wondering if there’s anything I’m missing?

By: Richard

Richard — Fri, 13 Aug 2010 11:35:49 +0000

@Matjaz, sorry don’t know never used it. The error points to a problem having a 64bits compiled apache and a 32 bit module.

By: Matjaz

Matjaz — Thu, 12 Aug 2010 15:04:30 +0000

thx,

i fixed it, the problem was that in the process i changed the permission of home directory, so localhost didn’t work.

i have another question, what about thomcat. i downloaded 1.24.xxx mod_jk.so and i got a problem

Syntax error on line 4 of /usr/local/Tomcat/tomcat6/conf/auto/mod_jk.conf: Cannot load /usr/local/apache2/modules/mod_jk.so into server: dlopen(/usr/local/apache2/modules/mod_jk.so, 10): no suitable image found. Did find:\n\t/usr/local/apache2/modules/mod_jk.so: mach-o, but wrong architecture

thx for your help

By: Richard

Richard — Tue, 10 Aug 2010 04:29:16 +0000

@Matjaz, did you look at the next page in the series:
http://diymacserver.com/installing-apache/configuring-apache-on-leopard/

By: Matjaz

Matjaz — Mon, 09 Aug 2010 14:51:42 +0000

I have a problem with permissions to the website.

localhost/index.php –> you don’t have permission

i have added httpd.conf

but this doesn’t work

please help….