Alexander Belopolsky <belopol...@users.sourceforge.net> added the comment:
On Wed, Apr 20, 2011 at 9:53 AM, STINNER Victor <rep...@bugs.python.org> wrote:
..
> test_time.test_tzset() fails on "x86 FreeBSD 7.2 3.x":
> 'AEST-10AEDT-11,M10.5.0,M3.5.0' timezone becomes 'EST'.
I was able to reproduce this error by faking a file named
'AEST-10AEDT-11,M10.5.0,M3.5.0' in /usr/share/zoneinfo/ on Mac OS X.
(As far as I know, OSX is not that different from BSD with respect to
basic posix interfaces.)
$ cd /usr/share/zoneinfo/
$ sudo cp EST AEST-10AEDT-11,M10.5.0,M3.5.0
Is it possible that the buildbot has such a file? What I find strange
is that autoconf logic tests for working tzset using exactly the same
TZ spec:
"""
putenv("TZ=AEST-10AEDT-11,M10.5.0,M3.5.0");
tzset();
if (localtime(&groundhogday)->tm_hour != 11)
exit(1);
#if HAVE_TZNAME
if (strcmp(tzname[0], "AEST") || strcmp(tzname[1], "AEDT"))
exit(1);
#endif
""" See 'configure' script.
In other words, if TZ=AEST-10AEDT-11,M10.5.0,M3.5.0 breaks tzset, this
should be detected at the configure stage and the tzset tests should
be skipped. Is there a way to force configure run on the bot?
----------
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue11886>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
