[llvm-bugs] [Bug 40358] New: wasm32: Failed to write output file on Vagrant shared filesystem

via llvm-bugs llvm-bugs at lists.llvm.org
Thu Jan 17 08:55:27 PST 2019


            Bug ID: 40358
           Summary: wasm32: Failed to write output file on Vagrant shared
           Product: lld
           Version: unspecified
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: enhancement
          Priority: P
         Component: All Bugs
          Assignee: unassignedbugs at nondot.org
          Reporter: alex at crichton.co
                CC: llvm-bugs at lists.llvm.org, peter.smith at linaro.org,
                    sbc at 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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20190117/c575714c/attachment-0001.html>

More information about the llvm-bugs mailing list