-native working as designed? target vs host sbuild-chroot

["cedric.hombourger@siemens.com" <cedric.hombourger@siemens.com>]

Hello,

I was wondering if handling of -native was working as designed (or if I 
am missing something).

Let's consider the following steps:

     git clone -b next https://github.com/ilbers/isar
     . isar-init-build-env
     mc:qemuarm64-bookworm:hello-native

Observe that the build constructs sbuild-chroot-target when I would have 
expected sbuild-chroot-host. The sbuild environment for hello is indeed 
configured to build an amd64 package while running on an arm64 userland 
=> the build of that package alone takes several minutes (on an Intel 
Xeon 6242 and with /proc/cpuinfo listing 64 processors)

In addition, when using Isar from master (where support for -native and 
-compat is already there), the build fails to install build dependencies 
for hello-native:

|  sbuild-build-depends-main-dummy:amd64 : Depends: libc-dev:amd64 but 
it is not installable
|                                          Depends: libstdc++-dev:amd64 
but it is not installable

This issue may also be reproduced on next with 
7bc68bb27f562257977bb5f701564ab08d4c5b3a (base: Fix HOST_ARCH for native 
builds) removed. I guess I just making a note that -native may have 
issues on master.

My outstanding question would be: shouldn't -native use the *host* 
sbuild-chroot? If we agree that it should then I am happy to look into this.

Thanks
Cedric

Refs:
     next @ b602e36defa0abacb9ba874b4e98bc9741a006a0 kas: Fix a typo in 
KAS_IMAGE_PREINSTALL list
     master @ 61086915e6c83fff22effa85cda64a2ac0c2f100 dpkg: Fix 
internal deb import for sbuild