https://bugs.llvm.org/show_bug.cgi?id=40358

            Bug ID: 40358
           Summary: wasm32: Failed to write output file on Vagrant shared
                    filesystem
           Product: lld
           Version: unspecified
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: enhancement
          Priority: P
         Component: All Bugs
          Assignee: unassignedb...@nondot.org
          Reporter: a...@crichton.co
                CC: llvm-bugs@lists.llvm.org, peter.sm...@linaro.org,
                    s...@chromium.org

In one of the rustwasm projects we received a report -
https://github.com/rustwasm/wasm-bindgen/issues/1136 - about LLD failing. After
some debugging it looks like this is related to LLD's output file being on a
Vagrant shared filesystem between a host and guest VM. Some `strace` narrowed
this down --
https://github.com/rustwasm/wasm-bindgen/issues/1136#issuecomment-454879850 --
which seems to indicate that the call to `mmap` is failing with EINVAL.

Would it be possible perhaps to write the file a different way? It seems that
Vagrant's shared filesystem doesn't support mmap'ing files unfortunately :(

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

Reply via email to