Hi,
I have the following error from pkgsrc/deve/wayland-protocol under
NetBSD/amd64 10.99.12 of yesterday.
I have update wayland-protocol to 1.42 in my local tree for testing.
However the version in pkgsrc cvs tree has the same problem.
Any other NetBSD/amd64-current users reproduce this failure?
Thank you.
$ cd /usr/pkgsrc/devel/wayland-protocols
ryoon@castella: /usr/pkgsrc/devel/wayland-protocols
$ make clean install
===> Cleaning for wayland-protocols-1.42
=> Lock /usr/tmp/pkgsrc/devel/wayland-protocols/work/.lockfile
acquired for ``bootstrap-depends'' on behalf of process 13975
=> Bootstrap dependency digest>=20211023: found digest-20220214
=> Lock /usr/tmp/pkgsrc/devel/wayland-protocols/work/.lockfile
released for ``bootstrap-depends'' on behalf of process 13975
=> Checksum BLAKE2s OK for wayland-protocols-1.42.tar.xz
=> Checksum SHA512 OK for wayland-protocols-1.42.tar.xz
=> Lock /usr/tmp/pkgsrc/devel/wayland-protocols/work/.lockfile
acquired for ``depends'' on behalf of process 13975
===> Installing dependencies for wayland-protocols-1.42
=> Tool dependency meson>=0: found meson-1.7.0
=> Tool dependency mktools-[0-9]*: found mktools-20250213
=> Tool dependency pkgconf-[0-9]*: found pkgconf-2.4.3
=> Tool dependency cwrappers>=20150314: found cwrappers-20220403
=> Tool dependency checkperms>=1.1: found checkperms-1.12
=> Full dependency wayland>=1.21.0: found wayland-1.23.1
=> Full dependency libepoll-shim>=0.0.20210418: found libepoll-shim-0.0.20240608
=> Full dependency libffi>=1.20: found libffi-3.4.7
=> Lock /usr/tmp/pkgsrc/devel/wayland-protocols/work/.lockfile
released for ``depends'' on behalf of process 13975
===> Invoking ``install'' after barrier for wayland-protocols-1.42
===> Skipping vulnerability checks.
WARNING: No /usr/pkg/pkgdb/pkg-vulnerabilities file found.
WARNING: To fix run: `/usr/sbin/pkg_admin -K /usr/pkg/pkgdb
fetch-pkg-vulnerabilities'.
=> Lock /usr/tmp/pkgsrc/devel/wayland-protocols/work/.lockfile
acquired for ``tools'' on behalf of process 20252
===> Overriding tools for wayland-protocols-1.42
=> Lock /usr/tmp/pkgsrc/devel/wayland-protocols/work/.lockfile
released for ``tools'' on behalf of process 20252
=> Lock /usr/tmp/pkgsrc/devel/wayland-protocols/work/.lockfile
acquired for ``extract'' on behalf of process 20252
===> Extracting for wayland-protocols-1.42
=> Lock /usr/tmp/pkgsrc/devel/wayland-protocols/work/.lockfile
released for ``extract'' on behalf of process 20252
=> Lock /usr/tmp/pkgsrc/devel/wayland-protocols/work/.lockfile
acquired for ``patch'' on behalf of process 20252
===> Patching for wayland-protocols-1.42
=> Applying pkgsrc patches for wayland-protocols-1.42
=> Verifying
/usr/pkgsrc/devel/wayland-protocols/patches/patch-stable_xdg-shell_xdg-shell.xml
=> Applying pkgsrc patch
/usr/pkgsrc/devel/wayland-protocols/patches/patch-stable_xdg-shell_xdg-shell.xml
Hmm... Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-stable_xdg-shell_xdg-shell.xml,v 1.2 2025/02/18
10:53:25 wiz Exp $
|
|* Remove 0x97 characters to fix gtk3 under NetBSD/amd64 10.99.2 as of
2022-01-03.
|
|--- stable/xdg-shell/xdg-shell.xml.orig 2022-11-29
13:37:41.000000000 +0000
|+++ stable/xdg-shell/xdg-shell.xml
--------------------------
Patching file stable/xdg-shell/xdg-shell.xml using Plan A...
Hunk #1 succeeded at 111.
done
=> Verifying
/usr/pkgsrc/devel/wayland-protocols/patches/patch-unstable_xdg-output_xdg-output-unstable-v1.xml
=> Applying pkgsrc patch
/usr/pkgsrc/devel/wayland-protocols/patches/patch-unstable_xdg-output_xdg-output-unstable-v1.xml
Hmm... Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-unstable_xdg-output_xdg-output-unstable-v1.xml,v 1.2
2023/07/05 22:36:45 wiz Exp $
|
|* Remove 0x97 characters to fix gtk3 under NetBSD/amd64 10.99.2 as of
2022-01-03.
|
|--- unstable/xdg-output/xdg-output-unstable-v1.xml.orig
2023-07-03 09:26:25.000000000 +0000
|+++ unstable/xdg-output/xdg-output-unstable-v1.xml
--------------------------
Patching file unstable/xdg-output/xdg-output-unstable-v1.xml using Plan A...
Hunk #1 succeeded at 125.
done
=> Lock /usr/tmp/pkgsrc/devel/wayland-protocols/work/.lockfile
released for ``patch'' on behalf of process 20252
=> Lock /usr/tmp/pkgsrc/devel/wayland-protocols/work/.lockfile
acquired for ``wrapper'' on behalf of process 20252
===> Creating toolchain wrappers for wayland-protocols-1.42
=> Lock /usr/tmp/pkgsrc/devel/wayland-protocols/work/.lockfile
released for ``wrapper'' on behalf of process 20252
=> Lock /usr/tmp/pkgsrc/devel/wayland-protocols/work/.lockfile
acquired for ``configure'' on behalf of process 20252
===> Configuring for wayland-protocols-1.42
=> Adding run-time search paths to pkg-config files.
INFO: [subst.mk:_pkgconfig] Nothing changed in "wayland-protocols.pc.in".
=> Checking for portability problems in extracted files
=> Creating meson native file
The Meson build system
Version: 1.7.0
Source dir: /usr/tmp/pkgsrc/devel/wayland-protocols/work/wayland-protocols-1.42
Build dir:
/usr/tmp/pkgsrc/devel/wayland-protocols/work/wayland-protocols-1.42/output
Build type: native build
Project name: wayland-protocols
Project version: 1.42
Host machine cpu family: x86_64
Host machine cpu: x86_64
Found pkg-config: YES
(/usr/tmp/pkgsrc/devel/wayland-protocols/work/.tools/bin/pkg-config)
2.4.3
Build-time dependency wayland-scanner found: YES 1.23.1
Program /usr/pkg/bin/wayland-scanner found: YES (/usr/pkg/bin/wayland-scanner)
Configuring wayland-protocols.pc using configuration
Configuring wayland-protocols-uninstalled.pc using configuration
Build targets in project: 53
wayland-protocols 1.42
Headers : YES
User defined options
Native files: /usr/tmp/pkgsrc/devel/wayland-protocols/work/.meson_native
buildtype : plain
libdir : lib
libexecdir : libexec
mandir : man
prefix : /usr/pkg
sysconfdir : /usr/pkg/etc
tests : false
wrap_mode : nodownload
Found ninja-1.12.1 at /usr/pkg/bin/ninja
=> Lock /usr/tmp/pkgsrc/devel/wayland-protocols/work/.lockfile
released for ``configure'' on behalf of process 20252
=> Lock /usr/tmp/pkgsrc/devel/wayland-protocols/work/.lockfile
acquired for ``build'' on behalf of process 20252
===> Building for wayland-protocols-1.42
ninja: Entering directory `output'
[21/53] Generating include/wayland-pro...gement-v1-enum.h with a custom command
FAILED: include/wayland-protocols/color-management-v1-enum.h
/usr/pkg/bin/wayland-scanner --strict enum-header
../include/wayland-protocols/../../staging/color-management/color-management-v1.xml
include/wayland-protocols/color-management-v1-enum.h
[36/53] Generating include/wayland-pro...iewporter-enum.h with a custom command
ninja: build stopped: subcommand failed.
*** Error code 1
Stop.
make[1]: stopped making "install" in /usr/pkgsrc/devel/wayland-protocols
*** Error code 1
Stop.
make: stopped making "clean install" in /usr/pkgsrc/devel/wayland-protocols
ryoon@castella: /usr/pkgsrc/devel/wayland-protocols
$
--
Ryo ONODERA // r...@tetera.org
PGP fingerprint = 82A2 DC91 76E0 A10A 8ABB FD1B F404 27FA C7D1 15F3
