Re: autoconf and paths with spaces

On 7/1/07, Paul Kienzle <pkienzle <at> users.sourceforge.net> 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'?

Michael.