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:date:from:to:subject:message-id:reply-to :references:mime-version:content-type:in-reply-to; q=dns; s= default; b=BezXYXfv9GqN0ccP4fIiMYObTrV2J1OU/kSz6wkLV2ZNmobbpbq91 IR4MNfsLx9KCgZFwaHYsWURRXq20wcE6T/Tzf6+WcZDtd2/87Gi1N9Ph9F3kopni clDzzAGTEN/bc3JQpE4OZoevsV5xkoLbK6oM9/bsiGxmqmNiUVb3mo= 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:date:from:to:subject:message-id:reply-to :references:mime-version:content-type:in-reply-to; s=default; bh=zMQmgBDDwT2Cg8xkI1sr7WS40Bk=; b=TjPUv3l6FXBFHOxYlB98nIUTwSwM yClRLHAc/RZybR2xQ2fPFPjrDwjiflF2W/DRuNc34dna8MQzRUkBzl3XUjwJpatP JKm39CNYV3LWVQGua5RP+F0Aj/ROh39zo7s8QiJWTIwobOacBTiSxZpLlykXlLne RMyufMv1YLTbJGQ= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , 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=-5.4 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY autolearn=no version=3.3.2 X-HELO: calimero.vinschen.de Date: Mon, 17 Aug 2015 10:10:58 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: js185 package problem (was Re: Seg Fault in strftime) Message-ID: <20150817081058.GD25127@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20150803083634 DOT GE17917 AT calimero DOT vinschen DOT de> <20150803134223 DOT GB18434 AT calimero DOT vinschen DOT de> <20150805080216 DOT GS17917 AT calimero DOT vinschen DOT de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="O3RTKUHj+75w1tg5" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) --O3RTKUHj+75w1tg5 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Aug 16 20:00, Michael Enright wrote: > On Wed, Aug 5, 2015 at 1:02 AM, Corinna Vinschen wrote: > > On Aug 3 23:33, Michael Enright wrote: > >> On Mon, Aug 3, 2015 at 9:52 AM, Michael Enright wrote: > >> > I'm interested in a solution at the libmozjs level > >> > >> Is there anything I can do to advance a solution in libmozjs? > > > > You could report the problem upstream, ideally. Since the behaviour > > is not restricted to Cygwin (at least glibc and OpenBSD both use the > > same way to handle tm_zone/tm_gmtoff in strftime), they should be > > interested in a fix. >=20 > Looking at the upstream source it seems that they (mozilla.org) have > done something to allow their configure script to detect tm_zone's > presence. If the related configure variable HAVE_TM_ZONE_TM_GMTOFF is > defined as a result of configure's testing, then some code is enabled > that has the goal of getting those fields populated in the struct tm > that is passed to strftime. The steps are to transfer values from the > pseudo-tm struct they use to a temporary struct tm, call mktime with > that to get a time_t, pass the time_t to localtime_r, and then use the > resulting tm_zone and tm_gmtoffset values in the struct tm that they > pass to strftime. To me this all means that mozilla.org has the proper > code available and machinery to activate it. >=20 > I think the only reason there's a crash is because this mozilla.org > code is not enabled in cygwin's libmozjs185 for some reason. >=20 > I cloned the git repo that mozilla.org makes available and ran the > configure script. I was not able to build from the resulting setup, > but I was able to confirm that the HAVE_TM_ZONE_TM_GMTOFF macro is > defined. So the mozilla.org configure script does detect the members > on current Cygwin headers. Since that is the case the next step is to > look specifically at how libmozjs185 is built for distribution within > Cygwin. >=20 > Is there a possibility that the maintainer of Cygwin's library uses > hand-modified configure output to get around some problem, and that > stuff needs to be tweaked? Maybe the package just needs rebuilding. Yaakov? Corinna --=20 Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat --O3RTKUHj+75w1tg5 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJV0ZcSAAoJEPU2Bp2uRE+gN4UP/2pmBynP6bMOSg13dN+YlTXw 5zhXRnpo27i98rS51SnpnQHn6jO/+/XEywH0uNQdG8njBtQOmVTx3PYKUoEq/avG jC5xGnD9vNMsEZZTWFuULRiNmg+rlnCLCPNbuF+kepyxCQOAZ+bnrXs7usI3A0+C Ul96imbwN1NiqKpg2nJ6upyFdUUabjSzbE6bIyitav+TW+kHYQqFUEvXrpl46dt2 s2qp/FRzEQEorxePEW9rKhNv+AfRh4KjAyKlGJktzyXdcTIV3xK9a+ZbRx/bMUZP yK2oUdzFzgU5FaGbWSHOzzBJUeQrPVi9EfJsZM/Ufj/h1lkPEIuq8/eShokYXtwo KP3X463Jd8d6rOGOFuu6twKO0m2fPQ3Fmi8i8uf9fcUFVtyDGb+5wXkd/eWHHNek RvaVJU86GwJsNHTYRiBvAgFjaCrn4fvz+4VixNB9tDx7zjLf0E0VFJgNYgnGsMON gBpsqkVPQ1cCELcWst/u/tRDLEKscTro8HHzL3BpNgo4j3UDij2uTeXJ70aYFcCf KikoHQr5KXyg950Q1E5PHdjNIjinzkxCstYjWkT7M1P5RspYGtbz5zrs85AbhmCF Ym9MCJnMFzwRiUejBkubil3aPaf2oLEDDgmEIPmC0vUw25j/Rx7kazQ42Yh7G5ef nl+lrrhvBaRrAhH1IytZ =lcbm -----END PGP SIGNATURE----- --O3RTKUHj+75w1tg5--