Closed Bug 1928105 Opened 1 year ago Closed 1 year ago

liblmdb.a: No such file or directory

Categories

(Firefox Build System :: General, defect, P5)

Firefox 134
defect

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: uravasinski, Unassigned)

Details

Steps to reproduce:

building firefox from source code. I was doing it using intel C++:

  • create a wrapper icxw and icpxw, where if the target is wasm redirect to clang, otherwise remain intel C++. Those making wasm available still building with icx
  • create a mozconfig file and fill there following configuration:
    ac_add_options --disable-debug
    mk_add_options MOZ_PARALLEL_BUILD=6
    ac_add_options --enable-project=browser
    ac_add_options --with-libclang-path=/usr/lib/llvm-18/lib
    ac_add_options --disable-optimize
    ac_add_options RUSTC_OPT_LEVEL=0
    ac_add_options --disable-tests
    ac_add_options --as-milestone=release
    ac_add_options --without-wasm-sandboxed-libraries
    #ac_add_options --enable-artifact-builds
    mk_add_options --wasm-compiler=clang
    export CC=icxw
    export CXX=icpxw
    export AR=ar
    export CFLAGS="-march=native -mtune=native -I /usr/lib/x86_64-linux-gnu"
    export CXXFLAGS="-march=native -mtune=native-I /usr/lib/x86_64-linux-gnu"
    export WASI_OS=linux
    export WASI_ARCH=x86_64
    export WASI_VERSION=24
    export WASI_VERSION_FULL=${WASI_VERSION}.0
    export WASI_SDK_PATH=/opt/wasi-sdk-${WASI_VERSION_FULL}-${WASI_ARCH}-${WASI_OS}
    export PATH=$PATH:$WASI_SDK_PATH/bin
  • run ./mach build
    (if change CC and CXX to gcc the same error occurs in same place)

Actual results:

0:48.63 error: failed to run custom build command for lmdb-rkv-sys v0.11.2
0:48.63 note: To improve backtraces for build dependencies, set the CARGO_PROFILE_RELEASE_BUILD_OVERRIDE_DEBUG=true environment variable to enable debug information generation.
0:48.63 Caused by:

< ... >

0:48.70 exit status: 0
0:48.70 exit status: 0
0:48.70 cargo:rerun-if-env-changed=AR_x86_64-unknown-linux-gnu
0:48.70 AR_x86_64-unknown-linux-gnu = None
0:48.70 cargo:rerun-if-env-changed=AR_x86_64_unknown_linux_gnu
0:48.70 AR_x86_64_unknown_linux_gnu = Some("/usr/bin/ar")
0:48.70 cargo:rerun-if-env-changed=ARFLAGS_x86_64-unknown-linux-gnu
0:48.70 ARFLAGS_x86_64-unknown-linux-gnu = None
0:48.70 cargo:rerun-if-env-changed=ARFLAGS_x86_64_unknown_linux_gnu
0:48.70 ARFLAGS_x86_64_unknown_linux_gnu = None
0:48.70 cargo:rerun-if-env-changed=HOST_ARFLAGS
0:48.70 HOST_ARFLAGS = None
0:48.70 cargo:rerun-if-env-changed=ARFLAGS
0:48.70 ARFLAGS = Some("rcs")
0:48.70 cargo:warning=/usr/bin/ar: /home/ura/bin/ffx/obj-x86_64-pc-linux-gnu/x86_64-unknown-linux-gnu/release/build/lmdb-rkv-sys-04b89edb7b7068c7/out/liblmdb.a: No such file or directory
0:48.70 --- stderr
0:48.71 error occurred: Command ZERO_AR_DATE="1" "/usr/bin/ar" "rcs" "cq" "/home/ura/bin/ffx/obj-x86_64-pc-linux-gnu/x86_64-unknown-linux-gnu/release/build/lmdb-rkv-sys-04b89edb7b7068c7/out/liblmdb.a" "/home/ura/bin/ffx/obj-x86_64-pc-linux-gnu/x86_64-unknown-linux-gnu/release/build/lmdb-rkv-sys-04b89edb7b7068c7/out/bd90e9435131a953-mdb.o" "/home/ura/bin/ffx/obj-x86_64-pc-linux-gnu/x86_64-unknown-linux-gnu/release/build/lmdb-rkv-sys-04b89edb7b7068c7/out/bd90e9435131a953-midl.o" with args "" did not execute successfully (status code exit status: 1).

Expected results:

A finished build

The Bugbug bot thinks this bug should belong to the 'Firefox Build System::General' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → General
Product: Firefox → Firefox Build System

Can you reproduce with something other than intel C++? Intel C++ is not actively supported.

If you are able to reproduce, can you attach a full log with ./mach build -v?

Flags: needinfo?(uravasinski)
Severity: -- → S4
Priority: -- → P5

unset all flags that affect compilation seems solved plus using clang from mozilla toolchain (e.g not providing CC and CXX flags). The gcc also thrown a lot of errors in stl.

Flags: needinfo?(uravasinski)

(In reply to Yuriy from comment #3)

unset all flags that affect compilation seems solved

I'll close this bug then.

If you have different errors that gcc is throwing, raise them in a separate bug with the full logs attached.

Status: UNCONFIRMED → RESOLVED
Closed: 1 year ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.