> This is probably also why libtool's configure probes no fewer than 26 different names for the Fortran compiler my system does not have, and then spends another 26 tests to find out if each of these nonexistent Fortran compilers supports the -g option.
It's been awhile since I've dealt with autoconf and company, but I remember seeing things like this. This is bizarre, to me. It should be a simple process. Make a pass to detect fortran compilers, make a second pass to detect support for -g. (This is, of course, assuming that we even want to use this at all.)
I remember cleaning up a coworkers project that did something similarly inane. A pass over the data revealed something wasn't present. But his test scripts continued processing, including rereading the original data, as if the something were present. Wasted 20 minutes each time it was executed until I rewrote it to break early.
If X depends on Y and Y is absent, then don't do X.
It's been awhile since I've dealt with autoconf and company, but I remember seeing things like this. This is bizarre, to me. It should be a simple process. Make a pass to detect fortran compilers, make a second pass to detect support for -g. (This is, of course, assuming that we even want to use this at all.)
I remember cleaning up a coworkers project that did something similarly inane. A pass over the data revealed something wasn't present. But his test scripts continued processing, including rereading the original data, as if the something were present. Wasted 20 minutes each time it was executed until I rewrote it to break early.