Discussion:
Bug#1087919: meson: several packages FTBFS on reproducible-builds.org armhf: "Can not run test applications in this cross environment"
(too old to reply)
Simon McVittie
2024-11-20 09:00:02 UTC
Permalink
Package: meson
Version: 1.6.0-1
Severity: normal
Tags: ftbfs patch upstream
Forwarded: https://github.com/mesonbuild/meson/issues/13841
Control: affects -1 src:glib2.0 src:gobject-introspection src:accountsservice src:graphene jenkins.debian.org
X-Debbugs-Cc: qa-jenkins-***@lists.alioth.debian.org

reproducible-builds.org does a native build of armhf packages in an
armhf chroot on an arm64 host, and does not always wrap the build in
linux32 like the official buildds do.

This causes an inconsistency between Meson's meson.can_run_host_binaries(),
which returns true, and Compiler.run() (which fails with
"Can not run test applications in this cross environment". Previously
reported upstream as <https://github.com/mesonbuild/meson/issues/13841>,
which includes a simplified reproducer for the bug.

Proposed fix here: <https://github.com/mesonbuild/meson/pull/13930>

It would be useful if a fix for this could be included in Debian
testing/unstable, either via an upstream 1.6.1 release or as a patch.

Thanks,
smcv
Jussi Pakkanen
2024-11-20 19:40:01 UTC
Permalink
Post by Simon McVittie
It would be useful if a fix for this could be included in Debian
testing/unstable, either via an upstream 1.6.1 release or as a patch.
1.6.1 does not yet have a release date. Is it enough to get that in
within a week or two or would you need this sooner?
Simon McVittie
2024-11-20 20:30:01 UTC
Permalink
Post by Jussi Pakkanen
Post by Simon McVittie
It would be useful if a fix for this could be included in Debian
testing/unstable, either via an upstream 1.6.1 release or as a patch.
1.6.1 does not yet have a release date. Is it enough to get that in
within a week or two?
That sort of timeline is completely fine. The main thing I wanted to
establish is whether this is something that is likely to be fixed well
before the trixie freeze (and therefore can be ignored as a known issue
in the individual packages that are affected), or whether it's something
that needs to be worked around in debhelper or in individual packages.

smcv

Loading...