Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 21 Jun 2023 12:44:26 -0700
From: enh <enh@...gle.com>
To: Guy Harris <gharris@...ic.net>
Cc: Time zone mailing list <tz@...a.org>, libc-coord@...ts.openwall.com
Subject: Re: [tz] thread-safe localtime() for an arbitrary timezone

On Wed, Jun 21, 2023 at 12:05 AM Guy Harris <gharris@...ic.net> wrote:

> On Jun 20, 2023, at 11:27 PM, Guy Harris via tz <tz@...a.org> wrote:
>
> > On Jun 20, 2023, at 2:00 PM, enh via tz <tz@...a.org> wrote:
> >
> >> it's actually the openbsd strptime.c that's unhappy:
> >> ```
> >> In file included from bionic/libc/tzcode/strptime.c:40:
> >
> > I see the string "bionic" rather than "openbsd" there, so that appears
> to be *Bionic's* strptime.c that's unhappy.  Is there a requirement that
> Bionic's strptime.c be unchanged from OpenBSD's?
>
> In fact, the openbsd strptime.c, as of CVS revision 1.32:
>
>
> https://cvsweb.openbsd.org/src/lib/libc/time/strptime.c?rev=1.31&content-type=text/x-cvsweb-markup
>
> does *not* contain the line
>
>         typedef struct state *timezone_t;
>
> so it appears that it's the *Bionic* strptime.c that's unhappy.


(this is answered on the other thread: it's tz's "private.h" that contains
that. i'm afraid without reading _both_ threads, the tz@ thread is going to
be confusing.)

Content of type "text/html" skipped

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.