Martijn van Oosterhout wrote: > On Fri, May 05, 2006 at 08:34:36AM -0400, Bruce Momjian wrote: > > > > I am thinking we would need an option at the start like --strict that > > would throw an error for any later invalid options. > > Well, --strict would be tricky, if it's possible. My reading of the > autoconf code doesn't indicate a means of doing adding abitrary > options. But something like --enable-strict-options would be fairly > straight forward. Problem being, if you mistype that option, it'll seem > to work even when it isn't :)
I've been bitten by this in the past as well. I'd vote for applying the patch as-is, no "strict mode" necessary (because, as you say, it's easy to get it wrong). Can the Debian build script be fixed? Does the RPM spec have the same problem? -- Alvaro Herrera http://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc. ---------------------------(end of broadcast)--------------------------- TIP 6: explain analyze is your friend
