Re: [PATCH v2 2/4] sbuild: do not build arch all packages on cross

["'MOESSBAUER, Felix' via isar-users" <isar-users@googlegroups.com>]

On Tue, 2026-05-05 at 07:10 +0200, Jan Kiszka wrote:
> On 04.05.26 10:50, Felix Moessbauer wrote:
> > Architecture all packages often cannot be built in cross mode, as the
> > dependencies cannot be resolved in the host architecture. This
> > especially applies to all packages which split their build dependencies
> > into Build-Depends-Arch and Build-Depends-Indep. We already have logic
> > in isar to built DPKG_ARCH=all packages non-cross, but this does not
> > work for packages that generate both arch specific and arch all binary
> > packages.
> > 
> > While sbuild automatically disables builds of arch-all packages on
> > cross, we previously explicitly overrode this setting. We now change
> > this by explicitly setting --no-arch-all flag on cross and --arch-all on
> > non-cross.
> > 
> > Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
> > ---
> >  RECIPE-API-CHANGELOG.md               | 16 ++++++++++++++++
> >  meta/classes-recipe/dpkg.bbclass      |  3 ++-
> >  meta/classes-recipe/multiarch.bbclass |  4 ++++
> >  3 files changed, 22 insertions(+), 1 deletion(-)
> > 
> > diff --git a/RECIPE-API-CHANGELOG.md b/RECIPE-API-CHANGELOG.md
> > index 856da5de..d4b093f4 100644
> > --- a/RECIPE-API-CHANGELOG.md
> > +++ b/RECIPE-API-CHANGELOG.md
> > @@ -1001,3 +1001,19 @@ do_copy_boot_files: The recipe isar-image-base is trying to install
> >  files into a shared area when those files already exists. It happens
> >  when some files have the same names (e.g., dtb files) for different
> >  distros.
> > +
> > +### No building of arch=all packages when cross building
> > +
> > +Architecture all packages often cannot be built in cross mode, as the
> > +dependencies cannot be resolved in the foreign architecture. This especially
> > +applies to all packages which split their build dependencies into
> > +`Build-Depends-Arch` and `Build-Depends-Indep`. We already have logic
> > +in isar to built `DPKG_ARCH = "all"` packages non-cross, but this does not
> > +work for packages that generate both arch specific and arch all binary packages.
> > +
> > +We now explicitly disable building `arch=all` binary packages during cross
> > +compilation (this only affects packages that produce both architecture-specific
> > +and `arch=all` binary packages). Recipes for such mixed packages should append
> > +`-all` to the `arch=all` binary packages listed in `PROVIDES` (e.g.,
> > +`PROVIDES="foo-doc-all"` for an `arch=all` binary package `foo-doc`). Consumers
> > +can then simply reference the package by its original name (e.g., `foo-doc`).
> 
> All this sounded very nice - but then I counted packages in trixie which
> end on -all: 60 right now. I suppose we need a different suffix, maybe
> "-archall" or "-arch-all".
> 
> BTW, we have the same problem with -compat and 25 name clashes there.
> Just -native is fine so far.

Even there we have a clash:

apt search '\-native$'
mlton-runtime-native/unstable 20241230+git20251029+dfsg-5 amd64
  Optimizing compiler for Standard ML - native runtime libraries

How about -archall? This hopefully also makes it more clear, that the -
archall is not part of the Debian package name.

Felix

> 
> Jan
> 
> -- 
> Siemens AG, Foundational Technologies
> Linux Expert Center

-- 
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/c8a217ce8270dfbb8f10210e93567cec1e88e089.camel%40siemens.com.