public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ktietz at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/42950] gfortran testsuite failures on mingw64
Date: Fri, 05 Mar 2010 10:34:00 -0000 [thread overview]
Message-ID: <20100305103405.1094.qmail@sourceware.org> (raw)
In-Reply-To: <bug-42950-13404@http.gcc.gnu.org/bugzilla/>
------- Comment #7 from ktietz at gcc dot gnu dot org 2010-03-05 10:34 -------
(In reply to comment #6)
As by this patch libgfortran.h defines _POSIX, some additional features (at
least for mingw-w64) getting active about localtime_r and gmtime_r (which
getting implemented by defines, if _POSIX is defined). So the following patch
is getting necessary too.
Index: gcc/libgfortran/intrinsics/date_and_time.c
===================================================================
--- gcc.orig/libgfortran/intrinsics/date_and_time.c 2009-06-22
09:43:32.000000000 +0200
+++ gcc/libgfortran/intrinsics/date_and_time.c 2010-03-05 11:14:39.200103300
+0100
@@ -55,6 +55,11 @@ see the files COPYING3 and COPYING.RUNTI
thread-local storage so they are threadsafe. */
#ifndef HAVE_LOCALTIME_R
+/* If _POSIX is defined localtime_r gets defined by mingw-w64 headers. */
+#ifdef localtime_r
+#undef localtime_r
+#endif
+
static struct tm *
localtime_r (const time_t * timep, struct tm * result)
{
@@ -64,6 +69,11 @@ localtime_r (const time_t * timep, struc
#endif
#ifndef HAVE_GMTIME_R
+/* If _POSIX is defined gmtime_r gets defined by mingw-w64 headers. */
+#ifdef gmtime_r
+#undef gmtime_r
+#endif
+
static struct tm *
gmtime_r (const time_t * timep, struct tm * result)
{
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42950
next prev parent reply other threads:[~2010-03-05 10:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-03 21:09 [Bug fortran/42950] New: " burnus at gcc dot gnu dot org
2010-02-04 4:10 ` [Bug fortran/42950] " nightstrike at gmail dot com
2010-02-04 12:32 ` burnus at gcc dot gnu dot org
2010-02-28 17:42 ` burnus at gcc dot gnu dot org
2010-03-04 17:56 ` burnus at gcc dot gnu dot org
2010-03-04 19:09 ` pinskia at gcc dot gnu dot org
2010-03-05 10:04 ` ktietz at gcc dot gnu dot org
2010-03-05 10:34 ` ktietz at gcc dot gnu dot org [this message]
2010-03-06 7:21 ` ktietz at gcc dot gnu dot org
2010-03-08 2:54 ` jvdelisle at gcc dot gnu dot org
2010-03-08 8:03 ` ktietz at gcc dot gnu dot org
2010-03-12 8:57 ` ktietz at gcc dot gnu dot org
2010-03-17 9:30 ` burnus at gcc dot gnu dot org
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=20100305103405.1094.qmail@sourceware.org \
--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).