X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Sat, 1 Dec 2007 11:31:55 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Failure in building GFortran on Cygwin
Message-ID: <20071201103155.GZ30894@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <Pine DOT CYG DOT 4 DOT 58 DOT 0711292328360 DOT 1532 AT homepc> <474F61CD DOT 1060405 AT verizon DOT net> <20071130142008 DOT GX30894 AT calimero DOT vinschen DOT de> <47501D95 DOT 3030200 AT byu DOT net> <20071130145842 DOT GY30894 AT calimero DOT vinschen DOT de> <20071130213601 DOT GC24092 AT ednor DOT casa DOT cgf DOT cx>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20071130213601.GC24092@ednor.casa.cgf.cx>
User-Agent: Mutt/1.5.16 (2007-06-09)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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

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?


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
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/