On Fri, Jul 19, 2019 at 07:13:28PM +0200, Florian Weimer wrote:
> * Adrian Bunk:
> For comparison, the original plan was to provide a macro, perhaps
> -D_TIME_BITS=32 and -D_TIME_BITS=64, to select at build time which ABI
> set is used (“dual ABI”).

To me this would sound like more trouble than a clear break,
similar to the mostly working dual OpenSSL 1.0 and 1.1 support
in stretch.

"Mostly working" as in Apache segfaulting depending on the load order of 
its modules - it is really hard to get all special cases like plugins 
sorted out correctly in such setups.

> Similar to the LFS support, with the
> additional property that binaries built in either mode should continue
> to work on kernels which predate support for the *_time64 system
> calls.

Debian does not support running on kernels older than the one in the
previous stable release.

E.g. Qt in Debian 9 unconditionally uses the getrandom syscall that is 
not in kernel 3.16 in Debian 7.

> > For i386 the last newly released 32bit-only hardware were some early
> > Intel Atoms 10 years ago, and when the AMD Geode goes out of production
> > soon there might be no hardware in production left.
> > There are still surprisingly many people using Debian on 32bit-only
> > hardware, but in 20 years this will have changed.
> You have thankfully edited out the Intel Quark. 8-)

Support for the Intel Quark was dropped when the i386 baseline was 
raised from 586 to 686 in stretch, so that's already irrelevant for
the Debian i386 port.



       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

Reply via email to