DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:content-type; q=dns; s=default; b=jR
	EwVH0umaEt9R988NDBnUrY78nYQK3Ts4JWIwcEJhDi/fE6vofqevLCZNfWaPan7a
	FNFHBUV0/q8z5L9uo7ay3R/H9BCQoleHnByILFh5ksHIRopUnp/7P1wqdDMK//LH
	KZ8YjkOKeHDZzeBhqIfJMz10813DxXLNcrOBAHzdA=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
MIME-Version: 1.0
In-Reply-To: <CAAEKttyS4UaLyvMRucn==kBGZCfZJVw_r_hxP1i+HXmSZFgDvQ@mail.gmail.com>
References: <CAAEKttyS4UaLyvMRucn==kBGZCfZJVw_r_hxP1i+HXmSZFgDvQ@mail.gmail.com>
Date: Fri, 27 Mar 2015 09:01:41 -0400
Message-ID: <CAAEKttyhPE0hxqfRb6yFQcfyNRnDASWfMDzwe66eKmVeoPGykw@mail.gmail.com>
Subject: Fwd: Compatibility of binaries built with one version of cygwin with other versions of cygwin
From: Tom Kacvinsky <tom.kacvinsky@vectorcast.com>
To: cygwin@cygwin.com
Content-Type: text/plain; charset=UTF-8

Question:  if I build an executable/shared library on one version of
cygwin, is it guaranteed to work on later versions of cygwin, or is
that not recommended?

I learned the difficult way that building on one version and running
on an earlier version doesn't work.  My binaries are based on C++
code, so there is a dependency on libstd++ and libgcc_s (using the
Linux names for these libraries) and that is where I think I was
getting burned.  I don't think it is a problem with cygwin1.dll

Thanks,

Tom

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