Question about multilib testings

Hi everyone,  I've discovered, when building gcc10, that the tests in multilib directories aren't launched correctly, at least in our configuration (powerpc-ibm-aix* with ppc64 and pthread multilibs).  The tests are using the default compiler and the default library path instead of using the mu

Tar version being used

Hi everyone, I'm wondering if someone knows which tar version / configuration was being used when creating gcc-10.2.0 tarballs ? I'm getting some directory checksum errors while trying to unpack it with the AIX tar (which can be a bit old). But they are disappearing when I'm building these tar

Re: Tar version being used

> On Mon, Jul 27, 2020 at 12:59 PM CHIGOT, CLEMENT via Gcc > wrote: > > > > Hi everyone, > > > > I'm wondering if someone knows which tar version / configuration was being > > used when creating gcc-10.2.0 tarballs ? > > > > I'm gettin

Multilib Hierarchy

Hi everyone,  Recently, with David, we have introduced FAT library support on AIX to enable 64bit as default target (called gcc64 here). Currently, 32bit is the default (gcc32) and 64bit is just a multilib linked to -maix64 option. These FAT libraries are archives including both 32 and 64bit sh

Re: Multilib Hierarchy

Hi everyone, Since noone answered, I assume that MULTILIB_REUSE was indeed not the solution. Thus, I've implemented a solution using a new target macro MULTILIB_FALLBACK. It allows any target to return a new multilib suffix based on the current one being used by the algorithm. This solution is m

Re: Multilib Hierarchy

Resent with the patch expanded correctly (I guess, it wasn't because of UTF-8 encoding...).  Hi everyone, Since noone answered, I assume that MULTILIB_REUSE was indeed not the solution. Thus, I've implemented a solution using a new target macro MULTILIB_FALLBACK. It allows any target to return

Re: Multilib Hierarchy

On Tue, Oct 13, 2020 at 4:01 PM David Edelson via Gcc wrote: > On Tue, Oct 13, 2020 at 4:09 AM CHIGOT, CLEMENT via Gcc > wrote: > > > > Hi everyone, > > > > Since no one answered, I assume that MULTILIB_REUSE was indeed not the > > solution. > > Thu

Difference between MULTISUBDIR and "-print-multi-os-directory"

Hi everyone,  I'm wondering what is the real difference between the Makefile variable MULTISUBDIR which is set as the "installed subdirectory name" and the result of "-print-multi-os-directory" which is the "the relative path to OS libraries".                 Especially, some GCC libraries' config