Re: On time64 and Large File Support
"Andreas K. Huettel" <[email protected]> Fri, 11 Nov 2022 10:40:35 +0100
| Newsgroups | dev.linux.lists.c-std-porting |
|---|---|
| Organization | Gentoo Linux |
| Message-ID | <9018152.CDJkKcVGEf@pinacolada> |
> > > > Proposal: glibc gains two new build-time configure options: > > * --enable-hard-time64 > > * --enable-hard-lfs > > We should define new target triplets for this if it's really required. > That doesn't really help anyone *but* Debian ... > We need to support legacy binaries on i386. Few libraries are > explicitly dual-ABI. Whether it's safe to switch libraries above > glibc to LFS or time64 needs to be evaluated on a per-library > basis. For most distributions, no one is going to do that work, > and we have to stick to whathever we are building today. ... since for Debian the libraries with different ABI end up in different multiarch paths then. Anyone with a more, ahem, standard filesystem arrangement has to find a different solution for the problem of legacy binaries. -- Andreas K. Hüttel [email protected] Gentoo Linux developer (council, toolchain, base-system, perl, libreoffice)
signature.asc
(application/pgp-signature, 981 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQKTBAABCgB9FiEE/Rnm0xsZLuTcY+rT3CsWIV7VQSoFAmNuGJNfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEZE MTlFNkQzMUIxOTJFRTREQzYzRUFEM0RDMkIxNjIxNUVENTQxMkEACgkQ3CsWIV7V QSpfXRAAwRfEjN2IiXQLFQn+zfd49l/hdgQrIFLa7+/b7JpBuWUCLxscfN0c3SoP PcCRt+D4a9MSxz1NzS3ySTmI850rJJCQtfSZOKPFiDLhkeuZhJwpo4/Q8+gzAa9s ICnQjXz71sRQkgyd/Z2JWBtvRrTlpGu2ZCoMwr+kYIxdQ4/c3qCHwNykHtRzxuL9 /uNTSiLpRA1w1sn8+ktuWBSj+mACxXICy8OfzPIhLiFHRudjJkC5I1x8iWCPPCto HJI/joO8Tu6tTJXc/Io215zz7R7Al+3qibVamuJseHlxCcHsU0fQGGaLHVUFWMps aggJ0nPAxnF4DNG3/MEiTdu1RVvjhymF4ad2/OKtBVmrj2lDKiDMvPQlh/TXAvC+ m1pj2RhyKCYJnIcEKDSApQG0+dclzz7zE7EPoJDrVMvRzRBhjd/kZbsdSX+lV2YK LSOU4XMNzQy3Why9HtKI1cR+3kzaKm3+HYa9plBwznP5lc6LndMxCPaLSxnZPPLC wh/GD+glANzvrvwh9dbWygyb4gfdc/kElb22qhvkb0nH3vIWgjLWOuHkyC3VOjJO g4+HglE2KD2eBtu5vPC9L9SBMpEs0E3uRmA882QGKO0tf8mZ9tvMHagsSi436ZIg LjF2Z8tGiLYXD5ZV2jgxCBA0L0iLfemzzaT/kfVOqB2mWqGzbEQ= =S8DN -----END PGP SIGNATURE-----