> 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.
Go to know. I will not use spaces in the future. I was able to get the
package rebuilt by following this guide:
Which, incidentally, does not use spaces in its base directory.