On Nov 2, 2015, at 1:07 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> I wonder how much we need that script at all though. If, say, configure
> doesn't find bison, what's so wrong with just defining BISON=bison and
> letting the usual shell "bison: command not found" error leak through?
+1 This would certainly make it easier for downstream use cases, as well. Was not relishing having to parse the PERL
variableto find out if Perl was missing.
David