Configure script doesn't work properly if working directory path contains spaces

[GoogleCodeExporter]

Clone libvpx library into the folder like this "~/Development/sand box/" and 
run "./configure" script there. The result is like the following:

./configure: line 146: [: ~/Development/sand: binary operator expected
./configure: line 146: [: ~/Development/sand: binary operator expected
./configure: line 146: [: ~/Development/sand: binary operator expected
./configure: line 178: [: ~/Development/sand: binary operator expected
./configure: line 180: [: ~/Development/sand: binary operator expected
./configure: line 185: [: ~/Development/sand: binary operator expected
lConfiguring selected codecs
Configuring for target 'x86_64-darwin11-gcc'
  enabling x86_64
  enabling runtime_cpu_detect
  enabling mmx
  enabling sse
  enabling sse2
  enabling sse3
  enabling ssse3
  enabling sse4_1
  using yasm
  enabling postproc
  enabling unit_tests
~/Development/sand box/libvpx/build/make/version.sh: line 72: box/libvpx: No 
such file or directory
cp: ~/Development/sand: No such file or directory
cp: box/libvpx/build/make/Makefile: No such file or directory

Original issue reported on code.google.com by dkova...@google.com on 14 Nov 2012 at 8:03

[GoogleCodeExporter]

Original comment by albe...@google.com on 6 Dec 2012 at 10:22

• Changed state: Available

[GoogleCodeExporter]

This is normal and not unique to libvpx; most UNIX software behaves this way. 
It is a user error to attempt to compile software in a directory containing a 
space, so don't do that.

Original comment by ryandesi...@gmail.com on 12 Oct 2013 at 4:41