Closed GoogleCodeExporter closed 9 years ago
There are many people who add lots of command line arguments, and expect
configure to use the ones that work. This patch to bail out if something if
failing breaks that.
How about adding another argument --fail-if-missing?
Doesn't configure have a nicer way to abort than 'exit 1'?
Original comment by brammool...@gmail.com
on 18 Jun 2011 at 6:23
Bram: yes, I've been thinking of something like that myself (a
"--fail-if-missing" option). However, I don't know how to add it to
"configure.in" without putting it inside an --enable option. Can you shed some
light about it?
Original comment by shlomifi...@gmail.com
on 18 Jun 2011 at 8:43
Bram: so what do you think?
Original comment by shlomifi...@gmail.com
on 21 Jun 2011 at 7:24
Hi Bram!
Can you please voice your opinion about that? It's been over two weeks since my
last message. I think the best policy would be to have both a command line
option and an environment variable (say "FAIL_IF_MISSING") that can be set. But
I need your input to proceed further.
Regards,
-- Shlomi Fish
Original comment by shlomifi...@gmail.com
on 8 Jul 2011 at 12:09
OK, now http://code.google.com/r/shlomif-changes/ contains a
--enable-fail-if-missing flag that also controls failure on the rest of the
interpreters. (Tested on Linux).
The patch is attached, but you should try Mercurial first.
Regards,
-- Shlomi Fish
Original comment by shlomifi...@gmail.com
on 11 Jul 2011 at 3:57
Attachments:
Patch included
Original comment by brammool...@gmail.com
on 14 Dec 2011 at 7:56
Original issue reported on code.google.com by
shlomifi...@gmail.com
on 18 Jun 2011 at 1:41Attachments: