public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/108530] [13 regression] std/time/tzdb/1.cc fails after r13-5168-g559993b85744ae
Date: Thu, 26 Jan 2023 13:38:32 +0000 [thread overview]
Message-ID: <bug-108530-4-f0cHGLcdpu@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108530-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108530
--- Comment #8 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>:
https://gcc.gnu.org/g:93e2bf51dedd0870b78b770b72e34b15a7a0d14a
commit r13-5385-g93e2bf51dedd0870b78b770b72e34b15a7a0d14a
Author: Jonathan Wakely <jwakely@redhat.com>
Date: Thu Jan 26 09:26:35 2023 +0000
libstdc++: Fix strings read from /etc/sysconfig/clock [PR108530]
In r13-5339-ge00d5cafbe1a77 I made std::chrono::current_zone() look for
DEFAULT_TIMEZONE in /etc/sysconfig/clock but that is the wrong variable.
Old Suse systems use TIMEZONE to determine which zone /etc/localtime is
a copy of, and old RHEL system use ZONE.
libstdc++-v3/ChangeLog:
PR libstdc++/108530
* src/c++20/tzdb.cc (current_zone): Look for TIMEZONE or ZONE in
/etc/sysconfig/clock, not DEFAULT_TIMEZONE.
prev parent reply other threads:[~2023-01-26 13:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-24 19:46 [Bug libstdc++/108530] New: " seurer at gcc dot gnu.org
2023-01-24 20:16 ` [Bug libstdc++/108530] " redi at gcc dot gnu.org
2023-01-24 21:20 ` seurer at gcc dot gnu.org
2023-01-24 23:21 ` redi at gcc dot gnu.org
2023-01-24 23:42 ` redi at gcc dot gnu.org
2023-01-24 23:51 ` cvs-commit at gcc dot gnu.org
2023-01-24 23:53 ` redi at gcc dot gnu.org
2023-01-25 7:37 ` rguenth at gcc dot gnu.org
2023-01-26 13:38 ` cvs-commit at gcc dot gnu.org [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-108530-4-f0cHGLcdpu@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).