You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
emcc will now treat .bc files as source files. These means that will get compiled by clang before being passed to the linker. This matches the behaviour of clang. (emscripten-core/emscripten#20922)
When building with 3.1.52, the build fails with out/sqlite3.bc:1:2: error: expected top-level entity (the somewhat garbled output seems to be due to -j8):
Another project's tracking issue for this (libretro/RetroArch#16160) suggests renaming the .bc to .a in the makefile, but I am not knowledgeable enough to suggest a solution.
Building with 3.1.51 produces warnings which I think may be related to this:
emcc: warning: .bc output file suffix used without -flto or -emit-llvm. Consider using .o extension since emcc will output an object file, not a bitcode file [-Wemcc]
Here is a Dockerfile to reproduce this:
FROM emscripten/emsdk:3.1.52
# this works:#FROM emscripten/emsdk:3.1.51WORKDIR /src
RUN apt-get update && apt-get install -y libdigest-sha3-perl
# pull sourcesRUN wget https://github.com/sql-js/sql.js/archive/d58d741189660f64555a603fbebfe4fae6a121bd.zip \
&& unzip d58d741189660f64555a603fbebfe4fae6a121bd.zip
# build sql.jsRUN cd /src/sql.js-d58d741189660f64555a603fbebfe4fae6a121bd \
&& npm i \
&& MAKEFLAGS="-j8" npm run build
The text was updated successfully, but these errors were encountered:
Hello,
I just wanted to give a heads-up that it seems that emscripten
3.1.51
is the latest version with whichsql.js
builds.Version 3.1.52 added this change:
When building with 3.1.52, the build fails with
out/sqlite3.bc:1:2: error: expected top-level entity
(the somewhat garbled output seems to be due to-j8
):Another project's tracking issue for this (libretro/RetroArch#16160) suggests renaming the
.bc
to.a
in the makefile, but I am not knowledgeable enough to suggest a solution.Building with 3.1.51 produces warnings which I think may be related to this:
Here is a
Dockerfile
to reproduce this:The text was updated successfully, but these errors were encountered: