Open aduh95 opened 3 years ago
This issue has been automatically marked as stale because there has been no activity in the past year. It will be closed automatically if no further activity occurs in the next 30 days. Feel free to re-open at any time if this issue is still relevant.
@aduh95 I've stumbled upon a similar problem in #17431. Library is different, symptoms are different. But the underlying cause and the exception in config.log
are the same.
I see, it looks like the "#!" line that runs the emscripten "executables" under node is effected by package.json files. I guess we could/should override that in the #!
?
Please see my https://github.com/emscripten-core/emscripten/pull/17451#issuecomment-1902274071 for a possible fix.
Repro:
And in config.log:
This could be solved if
emconfigure
added apackage.json
file in the current directory: