From: Ronald <look@reply.to>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [WIN32] qemu-system-ppc fix
Date: Wed, 19 Jan 2005 00:37:26 +0100 [thread overview]
Message-ID: <pan.2005.01.18.23.37.25.645913@reply.to> (raw)
Hi,
This correct the build for windows which don't handle pre-1970 date
correctly.
With a lot of help from Jocelyn Mayer.
--- m48t59.c.old 2005-01-19 00:22:17.584979798 +0100
+++ m48t59.c 2005-01-18 23:49:11.000041668 +0100
@@ -80,6 +80,11 @@
static void set_time (m48t59_t *NVRAM, struct tm *tm)
{
time_t now, new_time;
+
+#ifdef _WIN32
+ if(tm->tm_year < 70)
+ tm->tm_year = 70;
+#endif
new_time = mktime(tm);
now = time(NULL);
Same thing in m48t08.c file
--- m48t08.c.old 2005-01-19 00:23:53.766894517 +0100
+++ m48t08.c 2005-01-19 00:25:01.224204587 +0100
@@ -71,6 +71,11 @@
static void set_time (m48t08_t *NVRAM, struct tm *tm)
{
time_t now, new_time;
+
+#ifdef _WIN32
+ if(tm->tm_year < 70)
+ tm->tm_year = 70;
+#endif
new_time = mktime(tm);
now = time(NULL);
reply other threads:[~2005-01-18 23:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=pan.2005.01.18.23.37.25.645913@reply.to \
--to=look@reply.to \
--cc=daimon55@free.fr \
--cc=qemu-devel@nongnu.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 NNTP newsgroup(s).