* Mark Wielaard: > Hi Florian, > > On Thu, Jun 26, 2025 at 11:02:51AM +0200, Florian Weimer wrote: >> * Chris Adams: >> > Once upon a time, David Airlie <airl...@redhat.com> said: >> >> Does anyone know if it's possible to install i686 build deps into an >> >> x86-64 build? >> >> >> >> I was going to try and see what building a mesa package that produced >> >> a 32-bit subpackage, but >> >> >> >> BuildRequires: llvm-devel.i686 doesn't seem to work, >> > >> > I think there would have to be like a llvm32-devel, like all the >> > mingw32/mingw64 packages. >> >> Right, we already have glibc32.x86_64 because that's the most convenient >> way to get -m32 support into gcc.x86_64. > > I assumed that was a hack that you would like to get rid of?
The hack was the glibc32 source RPM which contained a copy of glibc.i686.rpm, as previously built in Koji. The new glibc32 approach is not particularly hackish, it's just a bit like building firmware. There's another thing we do: The glibc binaries consumed by the GCC cross-compilers are copies of the natively built glibc binaries, but in a noarch package. This uses a peculiar Koji behavior, where noarch packages leak between architectures. This way, the x86_64 GCC build can install a glibc package on AArch64, and is able to build a usable libgcc_s as result (among other things). > At least for valgrind we assumed it would go away eventually. It > cleaned up the valgrind.spec and build. The valgrind i686 tools are > now just build as part of the valgrind.i686 package. A user that needs > them as part of their x86_64 install just does a dnf install > valgrind.i686 to get them. And I think that's still the right way to do it. Today, glibc32 only provides what GCC needs to build its -m32 bits, it's not a generally useful 32-bit development or execution environment. Thanks, Florian -- _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
