On Thu, Aug 20, 2020 at 1:07 AM Jeffrey Walton wrote:
> You might want to check this. In practice I don't believe 32-bit ABIs
> are supported on the 64-bit iron.
>
> I don't recall if the Linux ABI supports 32-bit on these machines. I
> thought Steven Monroe said something about this (i.e., not
Jeffrey Walton writes:
> If the ABI does specify a 32-bit interface, then GCC does not support
> it. Here's from GCC112 on the compile farm. GCC112 offers GCC 4.8 and
> GCC 8.3.
>
> # GCC 4.8
> $ gcc -m32 test.c -o test
> In file included from /usr/include/features.h:399:0,
>
On Wed, Aug 19, 2020 at 5:42 PM Maamoun TK wrote:
> ...
> > Another question: When looking at the powerpc64 things in configure.ac,
> > I wonder if powerpc64 supports 32-bit binaries, which would be built
> > with something like CC='gcc -m32' ?
> >
> > If 32-bit builds are possible, and are
On Wed, Aug 19, 2020 at 10:46 PM Niels Möller wrote:
> Hi, I've been busy and silent for a while.
>
> I was thinking, that I don't want to merge to master with
> --enable-power-crypto-ext enabled by default. And then we really need
> fat builds to have easy ci testing.
>
> So I'm applying the
Hi, I've been busy and silent for a while.
I was thinking, that I don't want to merge to master with
--enable-power-crypto-ext enabled by default. And then we really need
fat builds to have easy ci testing.
So I'm applying the AES-parts of this patch, to try to get fat builds
working as soon as
