Eventually what worked for me is just rebuilding the most recent emsdk tag on my machine:
./emsdk install sdk-tag-1.38.27-64bit ./emsdk activate sdk-tag-1.38.27-64bit As I now understand, what matters is the environment clang is compiled in. The version of clang doesn't make difference in this case. My current setup: devtoolset-7 llvm-toolset-7 (not sure if this was really needed) Hope this helps. On Friday, 22 February 2019 10:45:21 UTC, Sergei Romanov wrote: > > I'm using CentOS 7.6 and having the same problem. My solution was to > install an older tag - just before they updated to llvm 6. > ./emsdk install sdk-tag-1.38.2-64bit > ./emsdk activate sdk-tag-1.38.2-64bit > > After this [emmake cmake .. && emmake make] worked fine - successfully > generated .bc. But then emcc started to complain "cannot find binaryen js > libraries". This problem seems fixed in 1.38.8 - > https://github.com/emscripten-core/emsdk/issues/157 > I struggle to find the exact change which fixed it. Anyone knows if it's > possible to patch sdk-tag-1.38.2 locally and get it sorted? Or maybe it > just needs the right build configuration? > > To restate the problem: > We need a working emsdk with llvm 5. > > On Thursday, 21 February 2019 17:15:05 UTC, Mike Alberghini wrote: >> >> One of our devs requested emscripten on our build nodes. I'm trying to >> get it working on our build nodes, which are Red Hat 7.6. I keep hitting >> roadblocks and I'm wondering if anyone has managed to get this working on >> RHEL. >> >> Problem 1: new clang meets old libstdc++ >> >> When I install the SDK by following the directions, running emcc -v >> returns: >> >> clang++: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.20' not found >> (required by clang++) >> clang++: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.21' not found >> (required by clang++) >> >> Seems the version of clang that comes with emscripten does not like the >> old c libs on Red Hat. >> >> I know that Red Hat has a newer verison of clang available, so I track >> that down in llvm-toolset-6.0 >> >> Problem 2: Red Hat clang is not the clang emscripten is looking for >> >> Now when I run emcc -v I get >> >> shared:CRITICAL: fastcomp in use, but LLVM has not been built with the >> JavaScript backend as a target, llc reports >> >> shared:CRITICAL: you can fall back to the older (pre-fastcomp) compiler >> core, although that is not recommended, see >> http://kripken.github.io/emscripten-site/docs/building_from_source/LLVM-Backend.html >> shared:ERROR: failing sanity checks due to previous llvm failure >> >> Has anyone managed to get emscripten working on RHEL? Do I need to >> compile fastcomp to get this all working? >> > -- You received this message because you are subscribed to the Google Groups "emscripten-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
