Closed merceyz closed 1 year ago
Probably this was introduced by commit 1a0b77c572adbaa6e207aae0912b9cc27b573d80, which removes the #define SYS_open __syscall_open
definition causing __syscall_openat
to be called instead. Some more context: https://github.com/emscripten-core/emscripten/pull/16296#issuecomment-1079979886.
(I've a patch lying around here that fixes this, but it didn't fully pass the test suite the last time I tried to upstream it).
Starting in Emscripten v3.1.8, calling
fopen
with absolute Windows file paths causesENOENT
errors. The error comes from___syscall_openat
where it tries to open the following path:Reproduction:
Build the following C code with the provided build command
and run the following Node.js script.
Version of emscripten/emsdk:
Full link command and output with
-v
appended: