On Tue, July 17, 2007 4:03 pm, Jani Taskinen wrote: >> Now if we could just get configure to HALT when an option that is >> enabled by default but is specified on the command line as well >> isn't >> available, so users aren't confused by it continuing to build >> something they didn't ask for in the first place... :-v > > This didn't compute. Halt on option that is enabled by default but > isn't > available?? huh?
Joe Sixpack or Betty Buick goes to compile PHP. They do something not unlike: ./configure --enable-jpeg Assume --enable-jpeg is "on" by default (or defaults to "on" after you turn on GD?) Then assume that JPEG is not actually installed, or can't be found. AFAICT, because it's on by default in the first place, the fact that the user asked for it has no effect on the outcome: configure will cheerfully continue to build a system which has no JPEG. The user asked for JPEG. The user gets no JPEG. And it *seems* to work, only it doesn't have what they asked for. It's been a never-ending source of confusion to users who kind of expect the darn thing to puke on their pretty blue shoes if they ask for X and it can't find X... -- Some people have a "gift" link here. Know what I want? I want you to buy a CD from some indie artist. http://cdbaby.com/browse/from/lynch Yeah, I get a buck. So? -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
