[Dan Bungert]
> Thanks Paul, I didn't know about that. Clearly architecture-is-64-bit
> is the better solution.
I did not know about it either, and I agree that it is a much better
solution than listing individual architectures. It will ensure new 64
bits architectures will be handled
[Paul Wise]
> The right way to do this is to Build-Depend: architecture-is-64-bit
Thanks Paul, I didn't know about that. Clearly architecture-is-64-bit is the
better solution.
[Petter Reinholdtsen]
> [Dan Bungert]
> > I suggest adjusting the control file to reflect this state so that
> > builds
On Wed, 2024-01-24 at 23:59 +, Dan Bungert wrote:
> I suggest adjusting the control file to reflect this state so that
> builds are only attempted on 64 bit systems. Something like this
> should work.
The right way to do this is to Build-Depend: architecture-is-64-bit, so
that when new
[Dan Bungert]
> I suggest adjusting the control file to reflect this state so that
> builds are only attempted on 64 bit systems.
Why? Which problem are you trying to solve? Doing such change will
fail to automatically discover if gloo start working on other
architectures, and require extra
Source: gloo
Version: 0.0~git20230519.597accf-2
Severity: normal
X-Debbugs-Cc: daniel.bung...@canonical.com
Dear Maintainer,
gloo attempts to build on 32 bit systems.
https://buildd.debian.org/status/package.php?p=gloo
We know this will not work, as cmake reports the following:
> Gloo can only
5 matches
Mail list logo
