On Tue, 9 Mar 2021, Michael Andres wrote:
On Tuesday 09 March 2021 08:51:52 Richard Biener wrote:
Yeah. I've long wanted a way to deploy an arm "chroot" in /usr/arm-suse-linux/sysroot for the purpose of cross-compiling. You might remember talking about this a few (10) years ago.
See also https://hackweek.suse.com/projects/package-proper-cross-compilers
It _should_ be as simple as
# zypper --root /usr/arm-suse/linux/sysroot --arch arm {--noscripts,--scripts=qemu} install glibc-devel
Well 'ZYPP_TESTSUITE_FAKE_ARCH=arm zypper --root /usr/arm-suse/linux/sysroot...' could do the trick, though the variables name looks a bit hackisch. It was introduced in a time where you didn't have things images in mind.
Anyhow, turning the VAR into a --arch option to overwrite the auto detection is no big deal, if you find this helpful. It could be tied it to the usage of --root to prevent accidentally damaging the outer system.
Yeah, it definitely would be nice. I'm not sure whether rpm stores some "global" architecture in the rpmdb so further sanitization based on that could be done as well. As said, scripts handling needs some magic as well, or alternatively some --noscripts option or a way to check the transaction for LUA-only scriptlets (it would be nice to have the "bootstrap" set of packages be fully LUA-only - I guess for a native install we rely on the unpack-w/o-scripts and then script invocation strathegy to handle pre-in scriptlets on an empty system) Richard. -- Richard Biener <rguenther@suse.de> SUSE Software Solutions Germany GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany; GF: Felix Imendörffer; HRB 36809 (AG Nuernberg)