Open humphd opened 11 months ago
seems bun somehow created a corrupted file, maybe due to linuxkit
the fallback run it creates the file it is missing a / in the path. i can open a fix for that but im not sure about the first EACCES
dang this is happening in Windows too , very similar . I used ProcMon to trace and it shows these same folder/files. one difference is the error is "ENOENT"
note that windows does not support --compile right now, though this bug might be shared.
yes i do note that , its not working on both Windows 11 and WSL(Ubuntu), its working on MacOS(Hackintosh). All on the same machine
What version of Bun is running?
1.0.15
What platform is your computer?
Linux 6.4.16-linuxkit aarch64 unknown (Linux Dev Contianer on MacOS))
What steps can reproduce the bug?
file.ts
:console.log('hello world');
bun build file.ts --compile --outfile ./file
What is the expected behavior?
I'd expect to have an executable created
What do you see instead?
Additional information
The two calls that are failing in this
strace
are interesting, specifically:I'm not clear why it can't write to
.
(I have permissions to do it), but should the second not be/tmp/.179e939cefeff7f3-00000000.bun-build
(trying to write to the root)?Full trace:
Afterward, I have the current files in my cwd:
I noticed this was also fixed for https://github.com/oven-sh/bun/issues/2944 in https://github.com/oven-sh/bun/commit/5bec0252a0223e45571f56dc49c240366df99852