Skip to content
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

Jump to bottom

[SR-5358] Utilities/bootstrap fails on path with spaces #793

Closed
Bouke opened this issue Jul 2, 2017 · 4 comments
Closed

[SR-5358] Utilities/bootstrap fails on path with spaces #793

Bouke opened this issue Jul 2, 2017 · 4 comments
Labels
bug llbuild StarterBug

Comments

@Bouke
Copy link

Bouke commented Jul 2, 2017

Previous ID SR-5358
Radar None
Original Reporter @Bouke
Type Bug
Status Resolved
Resolution Cannot Reproduce
Environment

Xcode 9 beta 1

Additional Detail from JIRA
Votes 0
Component/s llbuild
Labels Bug, StarterBug
Assignee None
Priority Medium

md5: 9647c65899bb629c0723fe9d4ecb7042

Issue Description:

With latest master (a5d08ff), when running Utilities/bootstrap from a path with spaces, it shows the following error message. The exit code is 0, which is strange as it appears to be an error.

~/L/M/c/D/swift-package-manager ❯❯❯ Utilities/bootstrap -v
(...)
--- bootstrap: note: building self-hosted 'swift-build': env SWIFT_EXEC=/Users/bouke/Library/Mobile Documents/com~apple~CloudDocs/Developer/swift-package-manager/.build/debug/swiftc SWIFT_BUILD_PATH=/Users/bouke/Library/Mobile Documents/com~apple~CloudDocs/Developer/swift-package-manager/.build SYSROOT=/Applications/Xcode-beta.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.13.sdk /Users/bouke/Library/Mobile Documents/com~apple~CloudDocs/Developer/swift-package-manager/.build/debug/swift-build-stage1 --disable-sandbox -Xlinker -rpath -Xlinker @executable_path/../lib/swift/macosx -v --build-tests
xcrun --sdk macosx --show-sdk-platform-path
xcrun --find clang
'/Users/bouke/Library/Mobile Documents/com~apple~CloudDocs/Developer/swift-package-manager/.build/debug/swiftc' --driver-mode=swift -L '/Users/bouke/Library/Mobile Documents/com~apple~CloudDocs/Developer/swift-package-manager/.build/lib/swift/pm/4' -lPackageDescription -swift-version 4 -I '/Users/bouke/Library/Mobile Documents/com~apple~CloudDocs/Developer/swift-package-manager/.build/lib/swift/pm/4' -target x86_64-apple-macosx10.10 -sdk /Applications/Xcode-beta.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.13.sdk '/Users/bouke/Library/Mobile Documents/com~apple~CloudDocs/Developer/swift-package-manager/Package.swift' -fileno 5
'/Users/bouke/Library/Mobile Documents/com~apple~CloudDocs/Developer/swift-package-manager/.build/debug/swift-build-tool' -f '/Users/bouke/Library/Mobile Documents/com~apple~CloudDocs/Developer/swift-package-manager/.build/debug.yaml' test -v
sh: /Users/bouke/Library/Mobile: No such file or directory
@Bouke
Copy link
Author

Bouke commented Jul 12, 2017

I looked into this for some moments, but the correct arguments appear to be passed to swift-build-tool. The arguments are (according to the verbose output) quoted, so arguments might be handled incorrectly by the build tool. Disabling the sandbox makes no difference.

@Bouke
Copy link
Author

Bouke commented Aug 11, 2017

I don't feel like "StarterBug" suffices here. I've done some digging into this issue and the problem seems to arise from deep inside the build tooling. Might be even related to llbuild instead of SwiftPM, as the correct path is passed in quotes.

@ankitspd
Copy link
Member

I think we can call it a startbug for llbuild 🙂

@neonichu
Copy link
Member

Looks like this got fixed in the meantime, can't reproduce it anymore with current llbuild.

@swift-ci swift-ci transferred this issue from apple/swift-issues Apr 25, 2022
@shahmishal shahmishal transferred this issue from apple/swift May 5, 2022
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug llbuild StarterBug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@neonichu @Bouke @ankitspd