On Tue, Dec 15, 2020 at 11:10:17AM +0100, Eric Botcazou wrote:
> > Similarly for sparc,
> > --build=sparc64-redhat-linux --target=sparc64-redhat-linux --with-cpu=v7
> > was the bi-arch compiler with 32-bit binaries that defaults to -m32, but
> > also supports -m64, while
> > --build=sparc64-redhat-linux
> > was the 64-bit binary that defaults to -m64 but also supports -m32.
>
> OK, but what was the configuration of the system compiler of the distribution?
There were 32-bit and 64-bit distributions. The gcc build created (well,
still does, but the only remaining multilib we use is i686 for x86_64) some
subpackages that were for the primary multilib only (the compiler
subpackages) and others that were for both (the library subpackages).
So, in the 32-bit ppc distro, one had:
gcc-*.ppc.rpm - 32-bit C compiler
gcc-c++-*.ppc.rpm - 32-bit C++ compiler
...
libgcc-*.ppc.rpm - 32-bit libgcc.so
libgcc-*.ppc64.rpm - 64-bit libgcc.so
libstdc++-*.ppc.rpm - 32-bit libstdc++.so
libstdc++-*.ppc64.rpm - 64-bit libstdc++.so
etc.,
while in the 64-bit ppc distro one had:
gcc-*.ppc64.rpm - 64-bit C compiler
gcc-c++-*.ppc64.rpm - 64-bit C++ compiler
...
libgcc-*.ppc.rpm - 32-bit libgcc.so
libgcc-*.ppc64.rpm - 64-bit libgcc.so
libstdc++-*.ppc.rpm - 32-bit libstdc++.so
libstdc++-*.ppc64.rpm - 64-bit libstdc++.so
etc.
Similarly for *.sparcv9.rpm and *.sparc64.rpm.
Installing both gcc-*.ppc.rpm and gcc-*.ppc64.rpm wasn't possible,
both because they wouldn't appear in the repositories together and
because they conflicted if one manually downloaded them from the other
repository and tried to install.
Jakub