Hi Mike,
thanks for reporting this.
Spaces in filenames are these days supported on most platforms
but discouraged due to their bad interactions with shells.
Fixing this would require fixing it in autoconf which is used by GNU APL,
but not provided by it.
I would rather recommend to name your directory e.g. "APL2" rather
than "APL 2"
Best Regards,
Jürgen
On 5/3/24 05:55, M.Hall wrote:
Project: GNU APL
Version / SVN: 1.8 / SVN: 1775M
Build Date: 2024-04-24 13:04:25 UTC
Build OS: Darwin 23.3.0 arm64
config.status: default ./configure options
Archive SVN: 1775
When the source directory path has a space in it, the configure script
fails many checks.
Example path: /Volumes/Stuff/Language/APL 2/gnu-apl/trunk
Samples of failed tests in config.log:
configure:18691: checking for ncurses.h
configure:18691: g++ -c -g -O2 -I /Volumes/ARCHIVE/Language/APL
2/gnu-apl/trunk
conftest.cpp >&5
clang: error: no such file or directory: '2/gnu-apl/trunk'
configure:18731: checking for fftw3.h
configure:18731: g++ -c -g -O2 -I /Volumes/ARCHIVE/Language/APL
2/gnu-apl/trunk conftest.cpp >&5
clang: error: no such file or directory: '2/gnu-apl/trunk'
I tried quoting the include path in two places in the configure
script, but that didn't help:
$ diff configure-orig configure
5221c5221
< am__isrc=' -I$(srcdir)'
---
> am__isrc=' \"-I$(srcdir)\"'
18682c18682
< CXXFLAGS="$CXXFLAGS -I `pwd`"
---
> CXXFLAGS="$CXXFLAGS -I \"`pwd`\""
I also extracted from config.log a build command and test program from
one of the failed tests,, and it built successfully ... so I don't
know what 'configure' is really doing behind the scenes to cause those
failures.
When I rename the directory to remove the space, then the configure
script runs OK, and finds all the std headers and all the libs
installed in /usr/local.
I'm just mentioning this. It's not a big deal. I know the moral is
"Don't Do That.", :-)
Thanks!
--
Mike Hall
