From time to time this question rise up. So I would like to bring
another view from this issue.
I've tried to look at existing topics and the main issue seems the
requirement to build using rhel.
The other point is that if that both arches (i686,x86_64 as soon as
x86 is concerned) are built, it should be done at the scale of the
I haven't seen this point discussed, but I think what is really needed
when talking about multilibs is only a really small subset of
packages. wine, libva, libglvnd (if ever relevant for EL at this
point), probably others. (libvdpau was moved to base because of that
There are others packages that would be needed but not part of epel.
So, I'm going to enable support for multilibs for EL based OS in our
3rd part repository project:
Because we only rely on CentOS, this is an easy path for us, It's just
a matter to create a dedicated koji target and build tag that have
i686 along x86_64 and use the same destination tag as the normal
Unfortunately this cannot be done for epel because I expect that there
is no "public" compiler for the i686 arch on rhel. Instead I wonder if
it would be possible to consider using the x86_64 gcc and
cross-compile to i686 ? It would be a matter to tag few packages as
set-pkg-arches i686 in koji provided that the "base" i686 -devel
packages can be installed in the buildroot.
I hopes a long term solution can be found within epel (if any rhel8
The probable alternative is ask the package to migrate to base...