Re: www/chromium-128.0.6613.84 build failure (amd64; poudriere)

2024-08-29 Thread David Wolfskill
On Wed, Aug 28, 2024 at 07:19:54AM -0700, Cy Schubert wrote: > I should have checked ports-committers first. Looks like the fix went in > this morning. > Confirmed: after updating my ports tree (in my case, to main-n675360-efd8eb280e0b), I was able to (eventually!) build chromium-128.0.6613.

Re: www/chromium-128.0.6613.84 build failure (amd64; poudriere)

2024-08-28 Thread Cy Schubert
I should have checked ports-committers first. Looks like the fix went in this morning. -- Cheers, Cy Schubert FreeBSD UNIX: Web: https://FreeBSD.org NTP: Web: https://nwtime.org e^(i*pi)+1=0 In message <20240828070856.69d3c5cb@slippy>, Cy Schubert

Re: www/chromium-128.0.6613.84 build failure (amd64; poudriere)

2024-08-28 Thread Cy Schubert
Seeing this here in a 15-CURRENT poudriere jail too. Just a guess but this is likely because the base system has no libclang.so whereas the various LLVM ports do. This port depends on llvm15, which does supply a libclang.so. The message suggesting that LIBCLANG_PATH be set could be the correct cou

Re: www/chromium-128.0.6613.84 build failure (amd64; poudriere)

2024-08-27 Thread Ronald Klop
When you scroll back a bit in the logs the error output I see is: ... FAILED: gen/third_party/crabbyavif/crabbyavif_libyuv_bindings.rs ... thread 'main' panicked at /wrkdirs/usr/ports/devel/rust-bindgen-cli/work/bindgen-cli-0.70.1/cargo-crates/bindgen-0.70.1/lib.rs:622:27: Unable to find libclan