Re: autoconf and paths with spaces

[Paul Kienzle]

On Jul 1, 2007, at 12:10 PM, Michael Goffioul wrote:

> On 7/1/07, Paul Kienzle <address@hidden> wrote:
> > With proper quoting of the arguments in mkoctfile we can indeed build
> > oct and mex files, even if the path has spaces in its name.  The last
> > sticking point seems to be autoconf.
> >
> > For example, configuring the octave-forge odepkg with:
> >
> >        ./autogen.sh
> >        ./configure CFLAGS="-I'path with spaces'"
> >
> > the configure script fails with:
> >
> >        configure:1598: gcc -I'path with spaces'   conftest.c  >&5
> >        gcc: with: No such file or directory
> >        gcc: spaces': No such file or directory
>
> Did you try with quoting the full command argument, including -I like
> '-Ipath with space', instead of -I'path with space'?

Doesn't help.  I also tried various levels of escape.  No luck.

Here are the operative lines in configure:

  ac_link_default='$CC $CFLAGS $CPPFLAGS $LDFLAGS conftest.$ac_ext 
$LIBS >&5'
  CFLAGS='-I"path with spaces"'
  (eval $ac_link_default)

And the output:

  gcc: with: No such file or directory
  gcc: spaces": No such file or directory

The following hack gets me farther:

  ./configure CC="eval gcc" CFLAGS="-I'path with spaces'"

Putting it in the package manager resolves the particular issue and 
gets me farther, but I still don't have it working completely so I 
don't know if it introduces other problems.  It's also really ugly :-(

        - Paul