X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:message-id:date:from:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; q=dns; s=default; b=Jo/UmNEzUwtTBx2338kpCtIBC1CJuCF47wByDnjUq3/ H+VaS8hYrLHUD2XWiuuh40i6IyjWnNbWwYvBkBWwUOGG9s3dC+9hBIQ+wcaPGhX4 wKRyAnZt+tVDk8u6bxy9FLbTkKw0tsNK1Q/yRwVAESaICDqy+z0FQUUt6kxSi0zI = DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:message-id:date:from:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; s=default; bh=74myoTGFlJCRAIqFH2MA3PdzM9M=; b=BZHNmp/t8+SLhDnZ4 KMrrAD+wDBnKBmu1pllvuSABGZqQ0kvmr6XakpQb5kFem3YAV618RZBP0EJi1nbb Nu6qPlQ41ysbLF8lYDzmz5kTSHmObR6WCP6psdWqdnVys1gwTRtPtAt7UTQLSgMk vD5L99uGl98xNz+SUdwAQEsoTo= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: <cygwin.cygwin.com> List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com> List-Archive: <http://sourceware.org/ml/cygwin/> List-Post: <mailto:cygwin AT cygwin DOT com> List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs> Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=0.2 required=5.0 tests=AWL,BAYES_05,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS,UNSUBSCRIBE_BODY autolearn=no version=3.3.2 X-HELO: mail-bk0-f54.google.com X-Received: by 10.205.36.11 with SMTP id sy11mr35907bkb.172.1394108744690; Thu, 06 Mar 2014 04:25:44 -0800 (PST) Message-ID: <5318693E.5050709@gmail.com> Date: Thu, 06 Mar 2014 13:25:34 +0100 From: Marco Atzeri <marco DOT atzeri AT gmail DOT com> User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Fwd: struct tm problem References: <CAJoYywWqyBYEJKriugeU0deHm=DsS_LYgHotaX6K=q6TO_tmQQ AT mail DOT gmail DOT com> <20140304081928 DOT GF7236 AT calimero DOT vinschen DOT de> <CAJoYywUF2gpX5+-9H3gExyRMYUtJQyi_mHOX42uG9kRfaQ0Nvg AT mail DOT gmail DOT com> <53172C18 DOT 5090906 AT redhat DOT com> <20140305140553 DOT GC2192 AT calimero DOT vinschen DOT de> <CAJoYywXWrs+kreKb+_cZbTCJJ+7DQhFAgXgX6w5d8k-KC_Nbqw AT mail DOT gmail DOT com> <CAJoYywW-yyh21ndB0m=vOtZPEohxtioXU3z3T2-KZdqkT+zNdw AT mail DOT gmail DOT com> In-Reply-To: <CAJoYywW-yyh21ndB0m=vOtZPEohxtioXU3z3T2-KZdqkT+zNdw@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes On 06/03/2014 13:17, Irfan Adilovic wrote: > On Wed, Mar 5, 2014 at 3:05 PM, Corinna Vinschen wrote: >> On Mar 5 06:52, Eric Blake wrote: >>> On 03/05/2014 03:45 AM, Irfan Adilovic wrote: >>>> If it is recognized that the executable was compiled against a >>>> different sized struct tm, how would you instruct cygwin1.dll code not >>>> to write to tm_gmtoff? >>> >>> Linker magic, the same as how we converted to 64-bit stat, and the same >>> as what we will eventually have to do if we want to convert to 64-bit >>> time_t. Basically, we add a new entry point, and alias the public name >>> to the new entry point. Any old program is still linked to the old >>> name, where we know they use the smaller size. Any new program is >>> linked to the new name, where we know they use the larger size. New >>> programs cannot run against the old dll, but the new dll is able to >>> handle both old and new apps by virtue of dual entry points. >> >> Not in this case. I just applied a patch which simply tests the API >> version of the executable and skips the code handling tm_offset and >> tm_zone, which are just a few lines anyway. > > Can you point me to the patch in CVS? I'd like to see the code -- > being curious, as I already said. > http://cygwin.com/ml/cygwin-cvs/2014-q1/msg00092.html -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple