Will Galway <[email protected]> writes: Invoking runbench as "./runbench", on my first attempt I kept getting the message "./runbench: gexpr: not found". Looking at runbench I see that gexpr is invoked as "gexpr" and not as "./gexpr". Rightly or wrongly, but being paranoid, I do not include "." in my PATH variable. Of course, after editing runbench to substitute "./gexpr" for "gexpr" everything worked fine. I hate to call this a bug, but I found it to be infelicitous. Perhaps runbench could be modified, or a few words could be added to the README file to indicate that you should have "." in your PATH variable? Don't you think people will work this out (like you did)?
The gmpbench web page tells people "To run the benchmarks, you also need to compile gexpr.c and put it somewhere in your path." -- Torbjörn Please encrypt, key id 0xC8601622 _______________________________________________ gmp-bugs mailing list [email protected] https://gmplib.org/mailman/listinfo/gmp-bugs
