-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot detect kernel during native build on Debian GNU/Hurd #13740
Comments
I've opened a downstream bug in Debian, cc'ing the Hurd porting team, to ask what they think |
smcv
added a commit
to smcv/meson
that referenced
this issue
Oct 2, 2024
All official Debian release architectures use the Linux kernel, but unofficial ports like hurd-i386 and kfreebsd-amd64 use the Hurd and FreeBSD kernel, respectively. Map Linux to 'linux' and kFreeBSD ports to 'freebsd' as per the reference tables in Meson's documentation. For now, use the Debian system name such as 'hurd' for anything else (see mesonbuild#13740 for the question of whether Hurd should identify its kernel differently). Signed-off-by: Simon McVittie <[email protected]>
smcv
added a commit
to smcv/meson
that referenced
this issue
Oct 2, 2024
All official Debian release architectures use the Linux kernel, but unofficial ports like hurd-i386 and kfreebsd-amd64 use the Hurd and FreeBSD kernel, respectively. Map Linux to 'linux' and kFreeBSD ports to 'freebsd' as per the reference tables in Meson's documentation. For now, use the Debian system name such as 'hurd' for anything else (see mesonbuild#13740 for the question of whether Hurd should identify its kernel differently). Signed-off-by: Simon McVittie <[email protected]>
jpakkane
pushed a commit
that referenced
this issue
Oct 2, 2024
All official Debian release architectures use the Linux kernel, but unofficial ports like hurd-i386 and kfreebsd-amd64 use the Hurd and FreeBSD kernel, respectively. Map Linux to 'linux' and kFreeBSD ports to 'freebsd' as per the reference tables in Meson's documentation. For now, use the Debian system name such as 'hurd' for anything else (see #13740 for the question of whether Hurd should identify its kernel differently). Signed-off-by: Simon McVittie <[email protected]>
It would normally be |
sthibaul
added a commit
to sthibaul/meson
that referenced
this issue
Oct 13, 2024
uname -s does return gnu there. Resolves: mesonbuild#13740 Signed-off-by: Samuel Thibault <[email protected]>
sthibaul
added a commit
to sthibaul/meson
that referenced
this issue
Oct 14, 2024
uname -s does return gnu there. Resolves: mesonbuild#13740 Signed-off-by: Samuel Thibault <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Using
host_machine.kernel()
during a native build on Debian GNU/Hurd causes setup to fail.The wider context for this is that if
meson env2mfile
is asked to generate a cross-file to build GNU/Hurd binaries based ondpkg-architecture -ahurd-i386
, it haskernel='linux'
, which is certainly wrong. To fix that bug (see #13722) I would like it to have itskernel
set to whatever happens in native builds, but right now, what happens in native builds is an error, which doesn't seem like what anyone wants either.To Reproduce
outputs:
Expected behavior
I expected
host_machine.kernel()
to have some reasonable value, probably eithergnu
,hurd
ormach
.Whatever value is chosen, adding
'gnu': <the chosen value>
toKERNEL_MAPPINGS
inmesonbuild/environment.py
would probably be sufficient to resolve this bug.If I understand correctly, the kernel of a Hurd system is technically the GNU Mach microkernel, but that's an implementation detail that ordinary Unixy software is not expected to interact with? For what it's worth,
uname -s
(uname --kernel-name
) outputsGNU
on this system.system parameters
meson --version
? 1.5.2ninja --version
if it's a Ninja build? irrelevant, I don't get that farThe text was updated successfully, but these errors were encountered: