missing "bootstrap" sh files for `emar`, `emranlib`, `emcmake` and many others

[kapodamy]

Version of emscripten/emsdk:
emcc (Emscripten gcc/clang-like replacement + linker emulating GNU ld) 4.0.21 (d6f4231
9bab01a4b33aae255b7)
clang version 22.0.0git (https:/github.com/llvm/llvm-project 60513b8d6ebacde46e8fbe4faf1319ac87e990e
3)
Target: wasm32-unknown-emscripten
Thread model: posix
InstalledDir: C:\emsdk\upstream\bin

Failing command line in full:
bash: emar: command not found

Full link command and output with -v appended:

make generic CC='emcc' AR='emar rcu' RANLIB='emranlib' MYLDFLAGS="-sALLOW_MEMORY_GROWTH -sWASM_BIGINT -sENVIRONMENT=web"

After updating emscripten, sh files for emar and emranlib are missing or not created in %EMSDK%\upstream\emscripten. i can not use in mingw64.
As workarround i created copies of bootstrap file and then remaned to emar and emranlib.

Also noticied that maint directory is missing in %EMSDK%\upstream\emscripten\tools.

I always follow the update instructions from https://emscripten.org/docs/getting_started/downloads.html

EDIT: lastest working version was 4.0.12, newer versions do not include these files:

• emar
• embuilder
• emcmake
• emmake
• emnm
• emprofile
• emranlib
• emrun
• emscan-deps
• emscons
• emsize
• emstrip

[kripken]

Perhaps something went wrong in your emsdk checkout. I would try erasing it and re-installing from scratch.

[sbc100]

It looks like you are using windows, and therefore the windows version of the sdk is being installed, and that include .bat launcher files instead of the shell script launcher files.

[sbc100]

If we want to make the windows emsdk install work from bash I guess we can go back to shipping both shell scripts and bat file?

I'm worried we don't have good test coverage of this setup though. Are you running ./emsdk activate latest from a mingw64 bash shell? Does that work in terms of adding the right PATH elements such that which emcc could be expected to work? I wonder like to have better testing of all the different ways the windows SDK can be used.

[kapodamy]

I reinstalled from cmd and mingw64 without success.
the whole upstream directory is downloaded from a zip file and such files are not shipped. Examples:

• version 1.39.3 (included) :
  • https://storage.googleapis.com/webassembly/emscripten-releases-builds/win/b024b71038d1291ed7ec23ecd553bf2c0c8d6da6/wasm-binaries.zip
• version 4.0.12 (included) :
  • https://storage.googleapis.com/webassembly/emscripten-releases-builds/win/209b886304498eff50dd835850dc5715803401ed/wasm-binaries.zip
• version 4.0.13 (not included):
  • https://storage.googleapis.com/webassembly/emscripten-releases-builds/win/32b8ae819674cb42b8ac2191afeb9571e33ad5e2/wasm-binaries.zip
• version 4.0.21 (lastest) (not included):
  • https://storage.googleapis.com/webassembly/emscripten-releases-builds/win/d70a5da89b3e673bf6a482724478fc17e81e575e/wasm-binaries.zip

[kapodamy]

@sbc100 PR #23761 removed these files and for some reason bootstrap does not generate those files.