On x86-64, the makefiles also try to build the fedora-core tests as 32bit binaries. This does not work if the 32bit version of glibc is not available. The configure script should check that the 32bit binaries can be compiled, and if they cannot, it should either fail and complain, or switch off the arch32 tests. Moreover, our build instructions should perhaps list glibc.i386 among the requirements. Moreover, some of the tests require libgcc_s. Again, a possible solution might be to check that libgcc.i386 is installed. But I was adviced that an alternative might be to try gcc -static-libgcc.
(In reply to comment #0) > Moreover, some of the tests require libgcc_s. > Again, a possible solution might be to check that libgcc.i386 is installed. > But I was adviced that an alternative might be to try gcc -static-libgcc. Is this a separate bug? Or just another example of the same bug, that 32-bit libgcc was missing.
(In reply to comment #0) > On x86-64, the makefiles also try to build the fedora-core tests as 32bit > binaries. This does not work if the 32bit version of glibc is not available. And PPC64? And s390x? > The configure script should check that the 32bit binaries can be compiled, and > if they cannot, it should either fail and complain, or switch off the arch32 tests. > Moreover, our build instructions should perhaps list glibc.i386 among the > requirements. FAIL; part of 64-bit is building and running 32x64 tests. Is there a meta-rpm that this could refer to?
(In reply to comment #2) > And s390x? > And PPC64? I suppose the same problem will hit there, too. I just took the most common example for now. > > The configure script should check that the 32bit binaries can be compiled, and > > if they cannot, it should either fail [...] > FAIL; part of 64-bit is building and running 32x64 tests. Thanks for the answer!
*** This bug has been marked as a duplicate of 3692 ***