All questions rhetorical, of course. I'm whining. I'm just as
frustrated with myself for having the unreasonable expectation that
--prefix controls where everything is installed (you know, like the
documentation says). I was forewarned with Perl and had a backup of all the relevant files. I didn't do this with Apache and I no longer have a virgin Apache setup. This wouldn't be a problem ordinarily (it left httpd.conf and other important files alone) but I have an incomplete install--it built me an httpd that looks for files in
This is why installing software on Mac OS X is such a clusterfuck. Even software that builds thinks it can shit all over your delicately-balanced system. "Hey, you're on Mac OS X!" it bellows inconsiderately, like a drunk loudly slurring "Hey, my sister's got your picture on her wall at the Ministry of Defence. She says you're the best spy they got!" to James Bond as he's tailing a KGB agent (or these days, an Axis-of-Evil ecoterrorist). The installer continues, however, to say "You're on Mac OS X, you install shit in fucked-up places! I know you can't handle commandlines so here, let me do what you didn't say and STUFF some MORE shit UP THERE" (the last half-dozen words accompanied by grunts as it dumps on your filesystem).
Mumble grumble.
--Nat
Boog ? (Score:2)
Re:Boog ? (Score:1)
Arthur
sky
Re:Boog ? (Score:1)
this is why i have a tarball of that build that i carry around so i never have to do that again.
for a contrast there, Configure on linux uses prefi
Re:Boog ? (Score:2)
--Nat
Re:Boog ? (Score:2)
Re:Boog ? (Score:1)