On 06/14/2012 08:18 AM, Timothy Madden wrote: >> If the "CUBRID Bison" version has some fatal flaw such that it cannot >> be used with your package, then you should test for *that* (e.g., by >> trying to run the detected bison on a test case) and fail the configure >> if the test fails. > > Oh, I thought there might be something like that. > > I get no fatal errors from CUBRID bison, it works fine, I just do not > trust CUBRID packagers, since they did such a thing as putting their own > bison on my PATH, which is not even needed by CUBRID. Why not change your PATH to put CUBRID after your desired bison, then? There's no rule that says you have to live with CUBRID's attempt to inject themselves first in your PATH. -- Eric Blake eblake@xxxxxxxxxx +1-919-301-3266 Libvirt virtualization library http://libvirt.org
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Autoconf mailing list Autoconf@xxxxxxx https://lists.gnu.org/mailman/listinfo/autoconf
