On Mon, Sep 19, 2016 at 11:57:13AM -0400, The Wanderer wrote: > Based on the error, it looks as if the build process is attempting to > run a command that uses the full path of the build directory, but does > not quote that path; as a result, the space gets treated as a token > separator.
Makefiles in general have no real way to handle filenames and directory names with spaces in them. The notion of a Makefile variable holding a space-delimited list of filenames is embedded in the design at the most fundamental levels. Passing these "lists" from Makefile to /bin/sh script fragments doesn't make things any simpler, either. > The net result is that it attempts to cp the absolute path > '/home/jschaeffer/Build' into the relative path > 'Test/nginx-1.6.2-5+deb8u2/auto', which does not exist. (The former path > may well not exist either, but I'd double-check that if I were you.) > > To fix this, either modify the build process to quote things > appropriately, or build from under a path which does not contain a > space. (The latter can be accomplished using symlinks, if preferred.) I doubt it's possible to make build paths containing spaces work correctly in the general case, even if the original poster does manage to hack it up this one time. My advice would be to stop attempting to use a directory with a space in its name as part of a build setup. It's doomed.
