Autoconf bug: space in volume name

[John Dundas, III]

Autoconf maintainers,

I may have encountered a bug in the autoconf suite.  In testing one of 
my own very simple projects, things work as expected until I use a 
volume that has a blank or space embedded in the volume name.  The 
following is an example running from a volume with an embedded space:

ddhcp-137-164-83-65:sparse johndundas$ pwd
/Volumes/NO NAME/sparse
ddhcp-137-164-83-65:sparse johndundas$ autoreconf -v
autoreconf: Entering directory `.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal
autoreconf: configure.ac: tracing
autoreconf: configure.ac: not using Libtool
autoreconf: running: /usr/local/bin/autoconf
autoreconf: configure.ac: not using Autoheader
autoreconf: configure.ac: not using Automake
autoreconf: Leaving directory `.'
ddhcp-137-164-83-65:sparse johndundas$ ./configure
./configure: line 1: syntax error near unexpected token `('
./configure: line 1: `m4trace:aclocal.m4:679: -1- AC_SUBST([am__quote])'
ddhcp-137-164-83-65:sparse johndundas$

Whereas running the same code from a volume without a space in the name 
yields:

ddhcp-137-164-83-65:sparse johndundas$ pwd
/Users/johndundas/Documents/Projects/sparse
ddhcp-137-164-83-65:sparse johndundas$ autoreconf -v
autoreconf: Entering directory `.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal
autoreconf: configure.ac: tracing
autoreconf: configure.ac: not using Libtool
autoreconf: running: /usr/local/bin/autoconf
autoreconf: running: /usr/local/bin/autoheader
autoreconf: configure.ac: not using Automake
autoreconf: Leaving directory `.'
ddhcp-137-164-83-65:sparse johndundas$ ./configure
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking for a BSD-compatible install... /usr/local/bin/install -c
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /usr/local/bin/grep
checking for egrep... /usr/local/bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking fcntl.h usability... yes
checking fcntl.h presence... yes
checking for fcntl.h... yes
checking for stdlib.h... (cached) yes
checking for string.h... (cached) yes
checking for unistd.h... (cached) yes
checking for off_t... yes
checking for ftruncate... yes
checking for memset... yes
checking for strerror... yes
checking for strrchr... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating config.h
config.status: config.h is unchanged
configure: Configured to build sputils

sputils Version 1.0

  Host setup:
  Install prefix:   /usr/local
  Compiler:         gcc
   CFLAGS:          -g -O2
   CPPFLAGS:
   LDFLAGS:
   LIBS:

Now type 'make [<target>]'
  where the optional <target> is:
    all                - build all binaries
    check              - validate correct operation
    install            - install everything

ddhcp-137-164-83-65:sparse johndundas$

This under Mac OS X 10.14.6, though I think other systems would be 
similarly affected.

ddhcp-137-164-83-65:sparse johndundas$ uname -a
Darwin ddhcp-137-164-83-65.cenic.org 18.7.0 Darwin Kernel Version 
18.7.0: Tue Aug 20 16:57:14 PDT 2019; 
root:xnu-4903.271.2~2/RELEASE_X86_64 x86_64 i386 MacBookPro14,3 Darwin
ddhcp-137-164-83-65:sparse johndundas$

If you need additional information, please let me know.

Thanks,

John