> The problem is that the install-script will be run *before* the configure
> script ;-)
I haven't looked at it in awhile, but why not just use autogen.sh
and have it do the configure.in checks, and populate a $MAKE environment
variable, which your install-script can pick up? Call it ./install or
something, and leave the innards under the hood, invisible.
> I guess I could add a check to see if 'gmake' exists and if not use 'make'
> instead.
Be aware though, that it may not always be in the path, like on
Solaris machines where gmake is on the system (and preferred) but buried in
a completely non-LSB location.
d.
