I have been updating to pkgsrc HEAD and running pkg_rr, to look for and fix issues, as usual. Mostly this has been ok recently. A rebuild of clamav failed. It turned out to be a combination of: pcre and pcre2 are installed (because git uses pcre2) clamav buildlinks pcre pcre2 has /usr/pkg/bin/pcre2-config, despite having pkg-config and that everything should use pkg-config instead these days. bl3 doesn't hide /usr/pkg/bin/ clamav's configure.ac looks for pcre2-config, finds it, and then fails to find the headers (because bl3 properly hid those) This won't hit bulk builds, because pcre2 won't be installed, but it causes source builds to fail if pcre2 is installed. With git requiring pcre2, that's very likely. So, options: 1) patch clamav's configure to not look for pcre2 and instead use pkg-config. Maybe send this upstream. 2) Maybe file a bug with pcre2 that foo-config files are bad :-) 3) Switch clamav to pcre2 (trivial, builds and works), avoiding the issue. This is safe because it looks for pcre2-config first, and if that's forced present, there will be no differing behavior. Expect that many programs will be flipping to pcre2 over time and just flip them when they hit this. 4) Somehow extend bl3 to shadow bin also. 1 is icky. 2 is tiling at windmills. 3 is easy and other than avoiding the real issue causes no real trouble. 4 is hard, and doing 3 doesn't preclude someone doing 4. So I'm going to do 3, barring someone explaining why not.
Attachment:
signature.asc
Description: PGP signature