[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: MinGW-related patches that were reported in 2014 but not applied
From: |
Eli Zaretskii |
Subject: |
Re: MinGW-related patches that were reported in 2014 but not applied |
Date: |
Sat, 23 Jul 2016 16:07:01 +0300 |
> From: Andy Wingo <address@hidden>
> Cc: address@hidden
> Date: Sat, 23 Jul 2016 14:15:06 +0200
>
> > * libguile/stime.c (scm_strftime) [__MINGW32__]: Don't use the
> > trick of appending "0" to the time-zone string, Windows runtime
> > doesn't support that.
> > +#ifndef __MINGW32__
> > + /* Don't do this for MinGW: it only supports fixed-format
> > + TTTnnnDDD TZ specifications, and gets confused if a zero is
> > + appended. */
>
> This patch disables the setzone() call entirely; seems to be the wrong
> thing, given that MinGW doesn't appear to have struct tm->tm_zone. What
> if we just disable appending the 0 to the time zone?
I'm not sure I understand what you have in mind, but if you show a
patch and a simple test, I can run it here.
Thanks.
Re: MinGW-related patches that were reported in 2014 but not applied, Andy Wingo, 2016/07/23