-
Notifications
You must be signed in to change notification settings - Fork 5.2k
[wasm] Having space in path fails builds #92399
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
Conversation
|
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsInvestigating #92335.
|
|
After escaping spaces the response file for AOT publish: The error still persists. Interestingly, emcc moves the quotations when passing arguments to clang, preserving the space escape: cc @radekdoulik |
|
Since the path is quoted we shouldn't need to escape space in |
In the current state we have |
Investigating #92335.
wbt->wbt artifactse.g.artifacts/bin/Wasm.Build.Tests/Release/net8.0/browser-wasm/wbt/blz_checkfingerprinting_Debug_gqyxbvpe_hfq->artifacts/bin/Wasm.Build.Tests/Release/net8.0/browser-wasm/wbt artifacts/blz_checkfingerprinting_Debug_gqyxbvpe_hfqThe change is not in the immediate parent directory but still fails BuildPublishTests.
Repro:
publish with AOT on Windows/Linux/iOS.
error (Windows):
in the default
WasmDedup=trueis caused by incorrect argv parsing indriver.cfor arguments with spaces.When dedup disabled or on Linux, error is:
Repro:
run the last line's command from the above error. The problem is on clang's side, even if we wrap included paths into quotations, like this:
it still splits the input by spaces instead of reading the whole string in the quotation.
Fix:
replacing spaces in
_EmccCFlagswith "\ " in WasmApp.Native.targets. However, MsBuild does not want to cooperate on that: dotnet/msbuild#3468, dotnet/msbuild#9200