i'm contributing the the Crypt::GCrypt perl bindings for libgcrypt. Certain old versions of libgcrypt are simply buggy, and will guarantee a test suite failure for the perl module. I'd like to refuse module compilation entirely when those versions are present (and print a helpful error message explaining why users should upgrade). What's the best way to do that?
I have a very simple C program written that could be compiled with the same flags used by the translated GCrypt.xs; It returns a 1 for "bad version" or 0 for "good version".
Is there a standard way to have the perl Makefile.PL step build and run this program before emitting a Makefile? Or should i look at some other way to check this information? Or should i just let the test suites fail without any other checking?
In reply to Testing for C library status at perl binding build time? by dkg
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |