Re: 64-bit time_t transition for 32-bit archs: a proposal

2023-06-07 Thread Bastien ROUCARIES
Le jeu. 8 juin 2023 à 05:31, Paul Wise a écrit : > > On Tue, 2023-06-06 at 11:45 +0100, Simon McVittie wrote: > > > 2. i386 as a multiarch foreign architecture to run legacy binaries on > >modern x86_64 systems > >2a. legacy native Linux i386 binaries > >2b. legacy Windows i386 binarie

Re: 64-bit time_t transition for 32-bit archs: a proposal

2023-06-07 Thread Paul Wise
On Tue, 2023-06-06 at 11:45 +0100, Simon McVittie wrote: > 2. i386 as a multiarch foreign architecture to run legacy binaries on >    modern x86_64 systems >    2a. legacy native Linux i386 binaries >    2b. legacy Windows i386 binaries via Wine (which requires a somewhat >    complete i386 Li

Re: 64-bit time_t transition for 32-bit archs: a proposal

2023-06-07 Thread Andreas Metzler
On 2023-06-07 Paul Wise wrote: [...] > There was another option mentioned earlier in the thread that could > help resolve some aspects of these conflicts; make 32-bit arches > (or just i386) support both time_t ABIs, like glibc and Linux do. > The 64-bit time_t ABI would be the default but the 32

Re: 64-bit time_t transition for 32-bit archs: a proposal

2023-06-07 Thread Guillem Jover
Hi! On Mon, 2023-05-22 at 18:17:44 -0700, Steve Langasek wrote: > On Fri, May 19, 2023 at 05:34:56AM +0200, Guillem Jover wrote: > > Enabling time64 explicitly is what also had first come to my mind, > > which does not seem too onerous if all the debhelper override > > disappears? :) Then NEW proc

Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal)

2023-06-07 Thread Lisandro Damián Nicanor Pérez Meyer
Hi, late on the thread, but... On Tue, 30 May 2023 at 19:51, Diederik de Haas wrote: > > [Please CC me in replies as I'm not subscribed to this list] > > I hope I'm not too late for this discussion ... > > Steve McIntyre wrote: > > Luca Boccassi wrote: > > >On Fri, 19 May 2023 at 12:42, Steve Mc

[i386] adlibtracker2 and fp-units-i386

2023-06-07 Thread Ivan Shmakov
> On 2023-06-07, Sune Vuorela wrote: > On 2023-06-07, Paul Wise wrote: >> I note that there are a number of packages available on i386 but not >> available on amd64, is anyone planning on an MBF about this issue? > I got curious. Some of them are hurd specific. Others are a i386 >

Re: 64-bit time_t transition for 32-bit archs: a proposal

2023-06-07 Thread The Wanderer
On 2023-06-07 at 03:19, Sune Vuorela wrote: > On 2023-06-07, Paul Wise wrote: > >> On Tue, 2023-06-06 at 09:33 +0200, Helmut Grohne wrote: >> >>> I've been reading the discussion around i386 a bit and found the >>> direction it has taken a little unproductive. >> >> I note that there are a number

Re: 64-bit time_t transition for 32-bit archs: a proposal

2023-06-07 Thread Simon McVittie
On Wed, 07 Jun 2023 at 07:19:39 -, Sune Vuorela wrote: > On 2023-06-07, Paul Wise wrote: > > I note that there are a number of packages available on i386 but not > > available on amd64, is anyone planning on an MBF about this issue? > > game stuff, mostly contrib, likely binary data for binar

Re: 64-bit time_t transition for 32-bit archs: a proposal

2023-06-07 Thread Peter Van Eynde
Hi, On Wed, Jun 7, 2023, at 09:19, Sune Vuorela wrote: > lisp runtie. unsure why restricted >> cmucl deb lisp optional arch=i386 >> cmucl-clm deb lisp optional arch=i386 cmucl contains a compiler and is self hosting (the compiler is used to create the new version of the environment). x86 is th

Re: 64-bit time_t transition for 32-bit archs: a proposal

2023-06-07 Thread Sune Vuorela
On 2023-06-07, Paul Wise wrote: > On Tue, 2023-06-06 at 09:33 +0200, Helmut Grohne wrote: > >> I've been reading the discussion around i386 a bit and found the >> direction it has taken a little unproductive. > > I note that there are a number of packages available on i386 but not > available on a