Open Bug 2037387 Opened 2 days ago

Fix m-c rusttests that now require sqlite

Categories

(Data Platform and Tools :: Glean: SDK, defect)

defect

Tracking

(Not tracked)

People

(Reporter: janerik, Unassigned)

References

(Depends on 1 open bug, Blocks 1 open bug)

Details

With Glean using sqlite we need to link sqlite for the Rust tests, so that mach rusttests works as expected.

A new try run: https://treeherder.mozilla.org/jobs?repo=try&revision=8b2b84d6536c9b07319d65dd819ca4618d349c17&selectedTaskRun=dQXkUlzVRjKiRdGBEV6IPQ.0

[task 2026-05-06T11:03:37.383+00:00] 11:03:37     INFO -  [libsqlite3-sys 0.35.0]
[task 2026-05-06T11:03:37.383+00:00] 11:03:37     INFO -  [libsqlite3-sys 0.35.0]
[task 2026-05-06T11:03:37.386+00:00] 11:03:37     INFO -  [libsqlite3-sys 0.35.0] error occurred in cc-rs: command did not execute successfully (status code exit status: 1): LC_ALL="C" "/builds/worker/fetches/sccache/sccache" "/builds/worker/fetches/clang/bin/clang" "-O2" "-ffunction-sections" "-fdata-sections" "-fPIC" "-gdwarf-4" "-fno-omit-frame-pointer" "-m64" "--target=x86_64-unknown-linux-gnu" "-fno-omit-frame-pointer" "-DSQLITE_CORE" "-DSQLITE_DEFAULT_FOREIGN_KEYS=1" "-DSQLITE_ENABLE_API_ARMOR" "-DSQLITE_ENABLE_COLUMN_METADATA" "-DSQLITE_ENABLE_DBSTAT_VTAB" "-DSQLITE_ENABLE_FTS3" "-DSQLITE_ENABLE_FTS3_PARENTHESIS" "-DSQLITE_ENABLE_FTS5" "-DSQLITE_ENABLE_JSON1" "-DSQLITE_ENABLE_LOAD_EXTENSION=1" "-DSQLITE_ENABLE_MEMORY_MANAGEMENT" "-DSQLITE_ENABLE_RTREE" "-DSQLITE_ENABLE_STAT4" "-DSQLITE_SOUNDEX" "-DSQLITE_THREADSAFE=1" "-DSQLITE_USE_URI" "-DHAVE_USLEEP=1" "-DHAVE_ISNAN" "-D_POSIX_THREAD_SAFE_FUNCTIONS" "-DSQLITE_HAS_CODEC" "-DSQLITE_TEMP_STORE=2" "-DHAVE_LOCALTIME_R" "-DSQLITE_ENABLE_UNLOCK_NOTIFY" "--sysroot" "/builds/worker/fetches/sysroot-x86_64-linux-gnu" "-I/builds/worker/workspace/obj-build/dist/system_wrappers" "-include" "/builds/worker/checkouts/gecko/config/gcc_hidden.h" "-U_FORTIFY_SOURCE" "-D_FORTIFY_SOURCE=2" "-fstack-protector-strong" "-fstack-clash-protection" "-ftrivial-auto-var-init=pattern" "-fstrict-flex-arrays=1" "-DDEBUG=1" "-I/builds/worker/workspace/obj-build/dist/include" "-I/builds/worker/workspace/obj-build/dist/include/nspr" "-I/builds/worker/workspace/obj-build/dist/include/nss" "-DMOZILLA_CLIENT" "-include" "/builds/worker/workspace/obj-build/mozilla-config.h" "-pthread" "-ffunction-sections" "-fdata-sections" "-fno-math-errno" "-fPIC" "-fcrash-diagnostics-dir=/builds/worker/artifacts" "-gdwarf-4" "-gsimple-template-names" "--start-no-unused-arguments" "-mllvm=-dwarf-linkage-names=Abstract" "--end-no-unused-arguments" "-O2" "-fno-omit-frame-pointer" "-funwind-tables" "-Wno-error=tautological-type-limit-compare" "-Wno-range-loop-analysis" "-Wno-error=deprecated-declarations" "-Wno-error=array-bounds" "-Wno-error=free-nonheap-object" "-Wno-error=atomic-alignment" "-Wno-error=deprecated-builtins" "-Wno-psabi" "-Wno-error=builtin-macro-redefined" "-Wno-unknown-warning-option" "-fno-strict-aliasing" "-ffp-contract=off" "-o" "/builds/worker/workspace/obj-build/x86_64-unknown-linux-gnu/debug/build/libsqlite3-sys-4a469117ecf983cb/out/ac0e812c7f297407-sqlite3.o" "-c" "sqlcipher/sqlite3.c"
[task 2026-05-06T11:03:37.386+00:00] 11:03:37     INFO -  [libsqlite3-sys 0.35.0]
[task 2026-05-06T11:03:37.386+00:00] 11:03:37     INFO -  [libsqlite3-sys 0.35.0]
[task 2026-05-06T11:03:37.386+00:00] 11:03:37     INFO -  warning: libsqlite3-sys@0.35.0: sqlcipher/sqlite3.c:110872:10: fatal error: 'openssl/crypto.h' file not found
[task 2026-05-06T11:03:37.386+00:00] 11:03:37     INFO -  warning: libsqlite3-sys@0.35.0:  110872 | #include <openssl/crypto.h> /* amalgamator: dontcache */
[task 2026-05-06T11:03:37.387+00:00] 11:03:37     INFO -  warning: libsqlite3-sys@0.35.0:         |          ^~~~~~~~~~~~~~~~~~
[task 2026-05-06T11:03:37.387+00:00] 11:03:37     INFO -  warning: libsqlite3-sys@0.35.0: 1 error generated.

Locally mach rusttests however works.

a-s previously dabbled around in that area (bug 1981745, bug 1958000), however the merged solution doesn't seem to help our case. I haven't gotten the other approach to work either. This will require help from other build folks.

You need to log in before you can comment on or make changes to this bug.