Add options --force-manifest and --test-build to bisect.pl

--force-manifest touches any files in MANIFEST that are missing. This avoids
hanging on 5.004 or earlier (where Configure's stdin is a tty) when Configure
detects the missing files and asks you if you want to stop. It's also useful
on 5.005 or later if you don't want to treat missing files as a "skip".
--test-build changes behaviour to treat failing to build the target exectuable
as a "fail", instead of a "skip".

1 files changed, 10 insertions, 0 deletions

diff --git a/Porting/bisect.pl b/Porting/bisect.pl
index 929c854677..ebaf4021c2 100755
--- a/Porting/bisect.pl
+++ b/Porting/bisect.pl
@@ -19,10 +19,20 @@ unless(GetOptions(\%options,
                   'expect-fail',
                   'one-liner|e=s',
                   'match=s',
+                  'force-manifest',
+                  'test-build',
                  )) {
     usage();
 }
 
+foreach (qw(force-manifest test-build)) {
+    # This is a bodge. I can't see a clean way to pass through suitably exact
+    # strings the various arguments to bisect-runner.pl that are argument-less
+    # flags. It might be easier for this program not to use Getopt::Long, and
+    # instead just grep out --start and --end
+    undef $options{$_} if exists $options{$_};
+}
+
 my $start = delete $options{start};
 # Currently the earliest version that the runner can build
 $start = 'perl-5.004' unless defined $start;