I did this by using the lipo command to thin out Apple's apache2
binary
(after making a backup of course) to just contain a 32-bit x86
image.
Works like a charm.
This is not a recommended path to follow, you're better off
compiling things using the correct flags than you to open yourself
up to issues caused by software update.
I guess you've haven't grasped the universal constant when it comes
to judging the efficacy of technological solutions:
It Depends.
YOUR situation may compel you to decide that this is not the a
"recommended path", however there are others in the world who have
differing circumstances where this particular approach works out
absolutely brilliantly.
Case in point, the server I first did this on was in need of being
updated from 10.5.2 to 10.5.4.
I ran the update and yes, Apple HAD updated the httpd binary wiping
out my thinned out binary. Apache was not loading due to the expected
errors described previously.
No matter. I had placed my commands for thinning httpd down into a
shell script. I simply reran that and lo and behold launchd pretty
much immediately started up the new i386-only based httpd without me
having to do anything else.
Problem solved. Case closed. No muss. No fuss.
Indeed. I guess I was just being 64bit stubborn ;)
Not really, right idea wrong approach.
Well, in my case, this particular servers usage pattern was such that
I deemed this an acceptable workaround that is well documented in our
system and works flawlessly. If Jeremy deems it works for him and he
accepts the consequences, then good for him.
Looking at your other email I see you recommend spending orders of
magnitude more time recompiling for an end result that most likely
provides no real-world practical benefit.
So how is thinning out the binary and being back up in 5 seconds the
"wrong" approach?
Dale, I respect your knowledge in how to tear apart and rebuild the
modules in PHP. You've frequently shared valuable knowledge in that
area with the list.
However in this case, a better approach might have been:
"Thinning out the binary is an interesting approach. It does pose
deployment risks from a Software Update wiping out your change, but
if you REALLY wanted 64-bit, here's how to do it:"
Otherwise, you just come across as rude and arrogant.
