X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Thu, 25 Mar 2010 09:54:17 +0100 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: 1.7.1<->1.7.2 binary compatibility Message-ID: <20100325085417.GF7718@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) 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 Mar 25 03:07, Uri Simchoni wrote: > Hi, > > Can an executable that has been linked against 1.7.2 work with cygwin1.dll version 1.7.1? > > I'd like to upgrade my build env, but not the runtime env of stable releases of a program. Yes, except if it uses an API new to Cygwin 1.7.2 (for instance, strfmon), or if the packege relies on specific behaviour new to 1.7.2 (for instance, coreutils 8.4). Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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