From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JmI1T-0007Nx-HI for qemu-devel@nongnu.org; Wed, 16 Apr 2008 20:30:43 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JmI1S-0007Mc-5H for qemu-devel@nongnu.org; Wed, 16 Apr 2008 20:30:43 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JmI1R-0007MZ-W1 for qemu-devel@nongnu.org; Wed, 16 Apr 2008 20:30:42 -0400 Received: from ug-out-1314.google.com ([66.249.92.168]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JmI1R-0004eb-Ei for qemu-devel@nongnu.org; Wed, 16 Apr 2008 20:30:41 -0400 Received: by ug-out-1314.google.com with SMTP id m2so1059284uge.4 for ; Wed, 16 Apr 2008 17:30:35 -0700 (PDT) Message-ID: Date: Thu, 17 Apr 2008 02:30:35 +0200 From: "andrzej zaborowski" Subject: Re: [Qemu-devel] No localtime_r in windows In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Hi, On 15/04/2008, consul wrote: > I don't pretend it is the correct patch, but at least it fixes the compile > time error on windows and seems to work. I'm not sure if the thread-safety > mechanism is needed here, or if this is the proper place to define the > function. Thanks for spotting that (also thanks to Herve Poussineau). I converted the TWL92230 RTC to use qemu's own time/date functions and there should be no localtime_r uses left there. Regards -- Please do not print this email unless absolutely necessary. Spread environmental awareness.