Re: Application of package options from within buildlink3.mk?

[Havard Eidnes <he%NetBSD.org@localhost>]

>>  - Do "make update" in textproc/libxml2/
>
> My first recommendation is:
>
>   Do not ever run make update.  Really not ever.  I would be inclined to
>   remove it, but I don't want to deal with that, and by not running it,
>   it doesn't bother me.
>
>   If you are using make update, and having a problem, please clearly
>   state that you are using make update when asking for help.

I hear you, but do not agree.

> All schemes involve a consistent pkgsrc tree.   cvs up -A, or to a
> branch, or to a date.  No mixing.

I hear this, and while it is a sound principle which has the best
chance of success, strictly adhering to it requires a lot of work.

> Then the choices are 
>
>   set up pbulk and build your packages.  resolve any bugs.  use pkgin to
>   update your system

That is a LOT of work, requiring both a lot of configuring,
handholding, time and disk space.  Several of these are in short
supply in this case.

In fact it's too much work when the actual target of this whole
excercise is to get LLVM 19 installed, so that I may re-try the
lang/rust build with an external LLVM on NetBSD 9.x.

>   run pkg_rolling-replace.  resolve any bugs in building.  work around
>   pkg_rr not handling py313-foo when default is 312.  work around
>   conflicts when files are moved from one package to another.   Really
>   it's just pkg_delete -f, or -r, keep track of what's gone, and rebuild
>   those, mostly, and it's easier than people who don't like pkg_rr make
>   it out to be.

You didn't mention the "safe" method that I sometimes use when no
binary package repository is available (and I dislike on principle the
"pkg_rolling-replace" method):

Sometimes, I use the method outlined in the pkgdepgraph man page,
i.e.:

cd /usr/pkgsrc
lintpkgsrc -i > pkgdepgraph.in
audit-packages >> pkgdepgraph.in
pkgdepgraph -D pkgdepgraph.in > delete_order
pkgdepgraph -R pkgdepgraph.in > rebuild.sh

>> My currently installed gnutls package is version 3.8.9nb1, so is
>> the current version, and the exacutables in the package have
>> yesterday's date, so it's been recently updated.  So this should
>> not have anything to do with my currently installed gnutls
>> package is too old.
>
> Maybe your current problem is not about make update.

Indeed.

> On my netbsd-10 amd64 system with all packages up to date
>
>   $ make show-var VARNAME=PKG_BUILD_OPTIONS.gnutls
>    pkcs11
>
> (yes, there's a space)

Thanks.

> Have you set any options?

Not really:

d3: {36} grep OPT /etc/mk.conf
#PKG_OPTIONS.rust+=     rust-internal-llvm
#PKG_OPTIONS.firefox+=  debug-info
d3: {37} 

> what does 'make show-options' show in gnutls?

d3: {35} make show-options
Any of the following general options may be selected:
        dane     Enable DANE support.
        pkcs11   Use certificate-on-a-stick (or card) support.

These options are enabled by default:
        pkcs11

These options are currently enabled:
        pkcs11

You can select which build options to use by setting PKG_DEFAULT_OPTIONS
or PKG_OPTIONS.gnutls.

> What does pkg_info -L, and -B show for installed gnutls?
> Is p11-kit installed?

"pkg_info -L gnutls" shows what one would expect.
"pkg_info -B gnutls" shows lots of things, among them

BUILD_DATE=2025-06-19 22:18:10 +0200
automatic=yes

The output is otherwise "normal" and too large for it to not be
rude to include here.

Regards,

- Håvard