I have a program that builds with no errors or warnings on a Windows-10 system internal drive (C:) that runs in a Parallels VM on OSX. The same program won't build if the project files are on a Parallels shared drive, which is mapped into Windows as a network drive. The error is: LLVM ERROR: IO failure on output stream: bad file descriptor There seems to be a related problem from the Rust community: https://github.com/rust-lang/rust/issues/54216
I believe this error often arises when the file descriptor limit is reached. It's plausible that network drives have lower descriptor limits. LLD's current normal file I/O pattern looks like this: - for all inputs: - open fd - memory map file from fd - close fd ... work - open temp output fd for write - calculate output file size, reserve bytes - memory map output file - ... write bytes in place - commit the temp file by renaming it and closing fds However, the text of the error message comes from raw_fd_ostream, which is not used for normal output writing in LLD. Are you using LTO or some other feature? LLD seems to only use output streams for auxiliary files like XML manifests and LTO blobs.
Sorry for the late answer. I don't think I'm using anything special. Here is the linker command line: 'C:\Program Files (x86)\LLVM\bin\lld-link.exe' /dll /def:dll.def /libpath:../../../libs /libpath:'C:\Program Files (x86)\IntelSWTools\compilers_and_libraries\windows\compiler\lib\ia32' /libpath:'C:\Program Files (x86)\LLVM\lib\clang\8.0.0\lib\windows' /nodefaultlib:libcmt.lib /nodefaultlib:libcpmt.lib /out:c:\tmp\\video-player.dll ../src/main.o ../src/player.o kernel32.lib user32.lib gdi32.lib ole32.lib msvcrt.lib mf.lib mfplat.lib mfuuid.lib strmiids.lib But I'm going to link Parallels Support to this ticket. Maybe that helps them too.
One more note: Using MSVC or the Intel C++ compiler instead of LLVM, everything works.
We have emscripten users reporting the similar issues with wasm-ld that I suspect is related to VM usage: https://github.com/emscripten-core/emsdk/issues/686 https://github.com/emscripten-core/emsdk/issues/677