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

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

First, many thanks for the follow-up.

> This is caused by a change that made p11-kit support optional in
> gnutls. When such an option is added, the ABI version in the
> buildlink3.mk must be bumped (and a recursive PKGREVISION bump is
> needed) because the old package that had p11-kit enabled by default,
> does not have the p11-kit option listed in its options, so the include
> will not happen.
>
> This option change was on 15 May 2024, and the recursive bump was on
> 16 May 2024 (i.e. last year). So I'm not sure why you stumble over
> this now - are your packages really that old?

The existing packages were probably old, yes.

What I am doing is:

 - Remove all work dirs from the /usr/pkgsrc tree
 - Update pkgsrc to HEAD
 - Do "make update" in textproc/libxml2/

This first removes all the packages which directly or indirectly
depended on libxml2, and then proceeds to (try to, unsuccessfully
in my case) re-build and re-install all of those removed packages
again.

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.

I am therefore repeating my question:

What does

  $ cd /usr/pkgsrc/multimedia/ffmpeg7
  $ make show-var VARNAME=PKG_BUILD_OPTIONS.gnutls

output in your case?  In my case it outputs just a blank line,
and I suspect that this causes my observed build problem.

> I didn't analyze your second problem because it looks very similar to
> your first one.

Yes, it appears to be caused by the same underlying, but as yet,
undiagnosed problem.

I just verified that my /usr/pkgsrc/mk has no local changes.

Hints for debugging this problem gratefully accepted.

Regards,

- Håvard