Hi!
On Mon, 2024-09-16 at 21:12:51 +0200, Chris Hofstaedtler wrote:
> On Mon, Sep 16, 2024 at 04:01:06PM +0200, Gianfranco Costamagna wrote:
> > Hello, after the time64_t transition, kannel started FTBFS on armel, armhf
> > and where time_t is 64 bit defined.
>
> With my ex-kannel-maintainer hat on, I have to say that is
> unsurprising.
>
> > I don't know how to patch it, and I don't know if changing that struct size
> > is source of troubles (is this a struct sent over network?)
>
> Best case you'd have to introduce a new TIME_T macro and what not.
> Maybe best to just remove the old binaries on arm{el,hf} and
> whenever a porter comes along, they can fix it.
I started looking into this yesterday, and went with something along this
suggestion, but then while adding 64-bit versions of dumping and
parsing functions I've realized that I don't think even 64-bit arches
are time64 safe, as the time is serialized into 4-bytes. :/
I'll continue this next Monday, hopefully with a full fix (ideally
even for 64-bit arches). But I need how and whether it is possible at
all to modify the serialized data, because I'm not sure that's part of
a standard on-wire protocol or similar.
Thanks,
Guillem
