[Rpm-maint] [rpm-software-management/rpm] configure.ac: add linux-gnux32 variant to triplet handling (PR #2143)

[Alexander Kanavin]

> > It does work for installing packages. But yes, we do not test building packages on targets.
> 
> People have different perceptions of "works", but I'm moderately surprised that it would work by any standard without futher patches. Which architecture packages are you feeding it, and how are you building them? Output of `rpm --showrc | head -20` from a x32 system would be interesting.

It's basically an x86_64 system that has been extended to accept x86_x32 packages, and with root filesystem composed entirely from the latter:

```
ARCHITECTURE AND OS:
build arch            : qemux86_64
compatible build archs: qemux86_64 noarch
build os              : Linux
compatible build os's : linux
install arch          : qemux86_64
install os            : Linux
compatible archs      : qemux86_64 all any noarch x86_64_x32
compatible os's       : linux
```

```
root at qemux86-64:~# cat /etc/rpmrc
arch_compat: qemux86_64: all any noarch x86_64_x32 qemux86_64
buildarch_compat: qemux86_64: noarch
```

And yes it's Yocto :) which means we build binaries outside of rpm, and use rpm only to package them and then indirectly via dnf to form a root filesystem from those packages (yes, we patch rpm to short circuit the build, and I know it's a 'rpm crime').

-- 
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/2143#issuecomment-1211961089
You are receiving this because you are subscribed to this thread.

Message ID: <rpm-software-management/rpm/pull/2143/c1211961089 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20220811/f34c19b5/attachment-0001.html>