Re: [Groff] groff 1.19.1 compile/installation failure

[Mike Parson]

On Mon, May 17, 2004 at 08:19:00PM -0500, Alejandro Lopez-Valencia
wrote:

> At 04:41 p.m. 17/05/2004, Larry Kollar wrote:
>
>> I suspect that making the makefiles work with non-GNU makes would be
>> a chore since they're built with configure (aka GNU autoconf). But
>> requiring bash, and requiring it to be in /bin, is probably something
>> that could be fixed.
>
> Not really. They are a home grown system that comes from the times
> when Automake and libtool didn't exist. I did try recently to port
> the Makefile system to automake/libtool (because automake alone is a
> disaster and libtool cleans up the act), but didn't go too far. I'll
> need to read the documentation again at least five times before it
> sinks in, and cut my teeth with a smaller project.
>
> There are problems with the autoconf script, no doubt. Under zsh it
> gives a weird error message:
>
> - % ./configure --prefix=/usr func_success failed.

Shouldn't configure run whatever shell is specified in the #! at the top
of the script?  What does sh ./configure or bash ./configure give you?

> And then churns away happily. This with zsh 4.02 under cygwin. If I use 
> bash 2.05b as my shell, surprise!, no problems at all. I concede, zsh is 
> *weird* and somewhat broken, but I love the command completion...

Shell discussions should probably be taken offline or another list, but
the current version of bash does have configurable tab completion.  I've
got it set to complete my NetBSD pkgs on pkg_* commands (someone else's
work), and wrote a set to complete my mh folders for (n)mh commands, cd
only tab-completes to directories, unzip to .zip files, chown to users
in /etc/passwd, lots of stuff.  Many examples are included with the
source distribution.

-- 
Michael Parson
address@hidden