Re: [PATCH] FAT library support for libatomic, libgfortran, libgomp, libstdc++

2020-06-03 Thread Iain Sandoe via Gcc-patches
David Edelsohn wrote: On Wed, Jun 3, 2020 at 3:14 PM Iain Sandoe wrote: libstdc++-v3/ * Makefile.am (tmake_file): Build and install AIX-style FAT libraries. * Makefile.in: Regenerate. * configure.ac (tmake_file): Substitute. * configure: Regenerate. * configure

Re: [PATCH] FAT library support for libatomic, libgfortran, libgomp, libstdc++

2020-06-03 Thread David Edelsohn via Gcc-patches
On Wed, Jun 3, 2020 at 3:14 PM Iain Sandoe wrote: > > Hi David, > > thanks for working on this! > > David Edelsohn wrote: > > > [I'll start by repeating what I wrote about a similar libgcc change to > > provide background and context.] > > > > When AIX added 64 bit support, it implemented what Ap

Re: [PATCH] FAT library support for libatomic, libgfortran, libgomp, libstdc++

2020-06-03 Thread Iain Sandoe via Gcc-patches
Hi David, thanks for working on this! David Edelsohn wrote: [I'll start by repeating what I wrote about a similar libgcc change to provide background and context.] When AIX added 64 bit support, it implemented what Apple MacOS Darwin calls "FAT" libraries for its equivalent functionality --

Re: [PATCH] FAT library support for libatomic, libgfortran, libgomp, libstdc++

2020-06-03 Thread Thomas Koenig via Gcc-patches
Hi David, After trying various options, the best solution seems to be the inclusion of target-specific Makefile fragments. Directly adding the rules to the Makefiles conflicts with Automake conditionals syntax. And Makefile fragments are easily extendible to other targets, such as Darwin. It avo

[PATCH] FAT library support for libatomic, libgfortran, libgomp, libstdc++

2020-06-02 Thread David Edelsohn via Gcc-patches
[I'll start by repeating what I wrote about a similar libgcc change to provide background and context.] When AIX added 64 bit support, it implemented what Apple MacOS Darwin calls "FAT" libraries for its equivalent functionality -- both 32 bit and 64 bit objects (or shared objects) are co-located