On 8/06/22 2:47 am, Jonathan Perkin wrote:
I'd love to get feedback on whether this works for you on exotic
platforms. I'm using it without issues on macOS and illumos, and
have had positive reports from NetBSD users. I'll also be turning
it on for all my daily bulk builds. Hopefully we can switch the
default to yes in the future.
Not a terribly exotic platform, but on my ArchLinux systems, with a
builtin sqlite3, trying to build devel/nss
if PKGSRC_USE_MKTOOLS=no then
pkgsrc/devel/nss/work/.buildlink/lib/pkgconfig/
ends up with
lrwxrwxrwx 1 root root 30 Jun 26 23:44 nspr.pc ->
/usr/pkg/lib/pkgconfig/nspr.pc
lrwxrwxrwx 1 root root 29 Jun 26 23:44 sqlite3.pc ->
/usr/lib/pkgconfig/sqlite3.pc
lrwxrwxrwx 1 root root 28 Jun 26 23:44 zlib.pc ->
/usr/lib64/pkgconfig/zlib.pc
and everything builds fine
while if PKGSRC_USE_MKTOOLS=yes then only get
lrwxrwxrwx 1 root root 30 Jun 26 23:41 nspr.pc ->
/usr/pkg/lib/pkgconfig/nspr.pc
lrwxrwxrwx 1 root root 28 Jun 26 23:41 zlib.pc ->
/usr/lib64/pkgconfig/zlib.pc
and nss fails to build with sqlite3 issues. Even though
USE_BUILTIN.sqlite3 is yes in both cases.