Package: meson
Version: 1.5.2-1
Severity: normal
Tags: upstream
X-Debbugs-Cc: debian-hurd@lists.debian.org
User: debian-hurd@lists.debian.org
Usertags: hurd
Forwarded: https://github.com/mesonbuild/meson/issues/13740
See the upstream bug report, but the tl;dr is that configuring this
Meson project on Hurd:
project('test')
message('system is @0@'.format(host_machine.system()))
message('subsystem is @0@'.format(host_machine.subsystem()))
message('kernel is @0@'.format(host_machine.kernel()))
outputs:
> Message: system is gnu
> Message: subsystem is gnu
>
> meson.build:4:43: ERROR: Kernel not defined or could not be autodetected.
Untested solution: in mesonbuild/environment.py, edit KERNEL_MAPPINGS and
add 'gnu': 'some suitable value'.
Hurd porters: what do you want host_machine.kernel() to return on Hurd?
Should it be 'gnu' (consistent with uname -s which prints 'GNU'), or
should it be 'hurd' or 'mach' or something else?
Whatever is the desired value, it would be great if someone who uses
Hurd could send a tested PR upstream.
The context for this is that I noticed that `meson env2mfile` (used during
cross-compilation) sets kernel to 'linux' for all Debian architectures,
which is certainly wrong.
https://github.com/mesonbuild/meson/pull/13722 fixes that for kFreeBSD,
but I don't know whether the kernel field on Hurd ought to be
'gnu', 'hurd', 'mach' or something else.
Thanks,
smcv
