[Interest] Chromium build failure, SSL and Qt 5.6.3 vs 5.6.0,

[André Pönitz]

On Wed, Aug 01, 2018 at 12:09:03AM +1200, Christian Gagneraud wrote:
> On 31 July 2018 at 23:55, Kai Koehne <Kai.Koehne at qt.io> wrote:
> >> -----Original Message-----
> >> From: Interest <interest-bounces+kai.koehne=qt.io at qt-project.org> On Behalf
> >> Of Christian Gagneraud
> >> [...]
> >> >> We used to build Qt-5.6.3 on and for Linux-i386.
> >> >> I recently had to downgrade to Qt-5.6.0 [...]
> >
> >> I don't want to be mean or rude, but honestly i have notice a degradation of
> >> patch release management in the recent years...
> >> To the point that now the "Qt Maintenance Tool" offers you to install different
> >> patch release, like nobody trust they are actually equivalent and ABI backward
> >> compatible as they used to be...
> >
> > Criticizing the MaintenanceTool to (again) provide non-latest patch level releases in a thread you started with "I recently had to downgrade to Qt 5.6.0' is ... interesting 😉
> 
> It is indeed! ;)
> The core problem, is that you have dropped Linux32 for both open
> source and commercial users.
> 
> Unfortunately the code base i'm dealing with cannot run on 64 bits
> machine (both runtime and build time).
> We need to run Qt 5.6 on:
> - Windows/intel 32 bits
> - Linux/intel 32 bits
> - Linux/arm 32 bits
> 
> We need to build Qt and Qt apps on:
> - Windows/intel 32 bits
> - Linux/intel 32 bits
> 
> And building Qt for Linux 32 is a real pain.

Can you remind me of an actual problem with that? 

The machine I am using to write this mail here has a Qt base at
cc03bad229 (last September) and Qt Creator at 99e3635ef3c (last week).

Linux 32 bit.

Andre'