-
Notifications
You must be signed in to change notification settings - Fork 158
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Nar breaks if there is a space in the path to the source #225
Comments
Thanks for the report, @SteveSmith16384. Care to file a PR to address it? It would be super helpful. |
It looks to me like chmod worked successfully. Otherwise should see This seems like it might be an issue in using "sh" (shell?) to call configure rather than calling configure directly. "sh" is used in body of If it is the shell, does it really need to be involved? Including shell typically also includes per user environment making a build less stable/reproducible. |
Yes, I think you're right Greg. I've just created a PR. Please note I rarely use nar or c/cpp, so I wouldn't know how to test my changes to destruction. |
For reference, the PR @SteveSmith16384 mentions above is #227, but it went stale waiting on feedback. |
If there is a space in the path to the source, then the build breaks quite soon with something like:-
.. which leads to lots of further errors. This seems to be cause by the function MakeExecutable() in NarUtils.jar (among other places) not wrapping the path in apostrophes when it runs the chmod command.
The text was updated successfully, but these errors were encountered: