[wasm] Using wasm-ld on paths containing symlinks doesn't work, on Windows
#63786
Assignees
Labels
arch-wasm
WebAssembly architecture
area-Build-mono
needs-further-triage
Issue has been initially triaged, but needs deeper consideration or reconsideration
Milestone
Comments
dotnet-issue-labeler
bot
added
area-Build-mono
untriaged
|
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsIs there an existing issue for this?
Describe the bugA project created with the default Expected BehaviorIt publishes. Steps To Reproduce
$vhd = New-VHD .\Source.vhdx -SizeBytes 128MB
$vhd | Mount-VHD
$disk = Get-VHD .\Source.vhdx | Get-Disk
$disk | Initialize-Disk -PartitionStyle GPT
$part = $disk | New-Partition -UseMaximumSize
$part | Format-Volume -FileSystem NTFS
$part.AccessPaths
New-SymbolicLink -Name VolIdDir -Target $part.AccessPaths[0] -Type Junction
cd VolIdDir
mkdir BlazorWasm
cd BlazorWasm
dotnet new blazorwasm
dotnet publish -c Release -fl "-flp:logfile=msbuild.log;verbosity=detailed"
dir .\obj\Release\net6.0\wasm\for-publish\Exceptions (if any).NET Version6.0.200-preview.21617.4 Anything else?I suppose yet another tool not written on and for Windows misbehaves by resolving symlinks, supposedly golang/go issues/40180
|
|
cc @radekdoulik can we do anything about this? |
|
I cannot reproduce this with 7.0 preview5. I didn't try it in docker though. The base issues shared by @ericwj are still open - docker/cli#2648, and https://github.com/golang/goissues/40180 . I don't see what we can do here though. We are running @ericwj do you see the issue only in docker? Can you try with a nightly build from https://github.com/dotnet/installer/ ? |
radical
added
the
needs-author-action
|
This issue has been marked |
radical
changed the title
wasm-ld : error : cannot open output file (...)\wasm\for-publish\dotnet.wasm: no such file or directorywasm-ld on paths containing symlinks doesn't work, on Windows
|
Looks like it got fixed! I wouldn't expect a fix to require source code changes in this repository; I would expect people here to be faster and better at diagnosing and suggesting changes to those tools though. I didn't use docker. All I do is keep my Source directory on a VHD and keeping the files located at USERPROFILE\Source. Wrt the issues
Both for go and docker the situation is, it isn't written by Microsoft. Both of these projects, on Windows, are giant hacks that only keep up appearance of working as long as nobody touches their system after Windows setup. What can I do with /dotnet/installer? There is only source code in the releases. On 6.0.400-previewI find my system in this state; I'm surprised Visual Studio didn't update any of this just today: On .NET 7 Preview 4 it seems to work. Running this will fail, albeit with a different error On latest SDKsAfter manually updating from dot.net: On both frameworks the publish succeeds. |
ghost
added
needs-further-triage
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there an existing issue for this?
Describe the bug
A project created with the default
blazorwasmtemplate has issues publishing if the project directory full path contains symbolic links to volumes that do not have a drive letter.Expected Behavior
It publishes.
Steps To Reproduce
repro.ps1:Exceptions (if any)
.NET Version
6.0.200-preview.21617.4
Anything else?
msbuild.log
I suppose yet another tool not written on and for Windows misbehaves by resolving symlinks, supposedly
wasm-ldsince it appears it is responsible for producing theC:\BlazorLink\VolIdDir\BlazorWasm\obj\Release\net6.0\wasm\for-publish\dotnet.wasmfile.golang/go issues/40180
docker/cli issues/2648
The text was updated successfully, but these errors were encountered: