Re: configure script can't handle blanks in paths (CVS version)

> > [The] configure script can't handle blanks in paths
> 
> Good point.  It is not just the configure script that will fail, but
> also the driver scripts for nhc98, hmake, and so on.  I have fixed
> these scripts, and will commit then to CVS once they have been tested.

In fact my modifications failed, and it turns out to be rather more
complicated than I imagined to support directory names with spaces,
everywhere they might required.  Shell scripts and Makefiles end up
with multiple levels of quoting around almost everything, and I'm
not sure it is worth adding the bother to the normal case, just to
handle an extremely rare case.  Instead, I am inclined to detect a
build path with spaces early on, and reject it.

Regards,
    Malcolm