X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Sat, 1 Dec 2007 11:13:03 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: Failure in building GFortran on Cygwin Message-ID: <20071201161303.GA13773@ednor.casa.cgf.cx> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <474F61CD.1060405@verizon.net> <20071130142008.GX30894@calimero.vinschen.de> <47501D95.3030200@byu.net> <20071130145842.GY30894@calimero.vinschen.de> <20071130213601.GC24092@ednor.casa.cgf.cx> <20071201103155.GZ30894@calimero.vinschen.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20071201103155.GZ30894@calimero.vinschen.de> User-Agent: Mutt/1.5.16 (2007-06-09) Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Sat, Dec 01, 2007 at 11:31:55AM +0100, Corinna Vinschen wrote: >On Nov 30 16:36, Christopher Faylor wrote: >> On Fri, Nov 30, 2007 at 03:58:42PM +0100, Corinna Vinschen wrote: >> >On Nov 30 07:26, Eric Blake wrote: >> >> -----BEGIN PGP SIGNED MESSAGE----- >> >> Hash: SHA1 >> >> >> >> According to Corinna Vinschen on 11/30/2007 7:20 AM: >> >> > >> >> > However, this *is* a problem in the newlib/cygwin headers. Cygwin >> >> > exports a timezone function and a _timezone variable. The timezone >> >> > function was an ill-advised invention in Cygwin way back in the last >> >> > century. Unfortunately it has to be kept for backward compatibility. >> >> >> >> For 1.5.x, yes. But can we delete timezone() for 1.7.x, on the grounds >> >> that any binary that still uses the timezone function is old enough that >> >> it would benefit from re-porting to the latest cygwin sources anyway? >> > >> >I'm thinking along the same lines. While that breaks backward >> >compatibility, I'm not overly concerned in case of applications which >> >have never been ported to a newer Cygwin version the last 10 or so >> >years. >> >> But we do have a fairly transparent way of dealing with this problem which >> will allow any ancient apps to continue to work. We used it for the transition >> from 32 -> 64 bit file I/O. > >Unfortunately it doesn't work for variables. We can hide the timezone >function, but how do we alias timezone to _timezone in libcygwin.a? Why do you say that? It should just be a simple aliasing. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/