Re: Avoiding llvm from ports on rpi4
- In reply to: Nuno Teixeira : "Re: Avoiding llvm from ports on rpi4"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Mon, 24 Feb 2025 03:30:49 UTC
Nuno Teixeira wrote: > > Next test will be build firefox with base compiler to achieve > x11+i3+firefox collection without ports llvm. > > <snip> > checking for libclang for bindgen... not found > ERROR: Could not find libclang to generate rust bindings for C/C++. > Please install the necessary packages, run `mach bootstrap`, or use -- > with-libclang-path to give the path containing it. > > and > > --with-libclang-path=`llvm-config --libdir` > so I presume that firefox needs llvm from ports as instructed in: > > Mk/bsd.gecko.mk <http://bsd.gecko.mk>: > MOZ_OPTIONS+= --with-libclang-path="${LLVM_PREFIX:S/${PREFIX}/ > ${LOCALBASE}/}/lib" > gecko@ ports require libclang for WebAssembly System Interface (WASI). The fact that gecko@ ports use Rust means you are already involving LLVM in that manner, whether the bundled copy or with PORT_LLVM set in lang/rust. You are finding out that trying to avoid LLVM is a futile exercise. -- Charlie Li ...nope, still don't have an exit line.