X-Recipient: archive-cygwin@delorie.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:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=FTr/fWPAyLDgM7vCHn0zn5futdtGHeJu4olyVJAMH9X
	BJ06r3pVfnzGVdJFZxsF7MTEz0/U5X/w89oBXVlH9Rvzwogg6lp2AM4C1mIl/7QL
	YCJB7RHBSG63QkFuKtGaA8w1DuBMqegfgY4ZnLxZonW+Fgt8oH5cjGwPsrJWOL1A
	=
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:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 s=default; bh=Kvsnnis7aZvehY5CmgoLP75d6MQ=; b=Syxb9/AYbkarsoL1N
	yqmLcv6rrnFWMCwEr+m9J3rG/IwWZm/iia5PDYM8f/tiyycgH1n4wzeMLLyhNmRL
	fs0IlPeNmxv7nJEHds35UZFf/cPrB5frTPkj1kHVVBojoSSCufFeran5fSSWBAfQ
	FOPcqdij+XPKyn3UanwnJEem8Y=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=0.7 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,KAM_FROM_URIBL_PCCC,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=no version=3.3.2
X-HELO: mail-wg0-f42.google.com
X-Received: by 10.180.90.113 with SMTP id bv17mr57585746wib.3.1427462606531;        Fri, 27 Mar 2015 06:23:26 -0700 (PDT)
Message-ID: <551559CA.3010101@gmail.com>
Date: Fri, 27 Mar 2015 14:23:22 +0100
From: Marco Atzeri <marco.atzeri@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: Fwd: Compatibility of binaries built with one version of cygwin with other versions of cygwin
References: <CAAEKttyS4UaLyvMRucn==kBGZCfZJVw_r_hxP1i+HXmSZFgDvQ@mail.gmail.com> <CAAEKttyhPE0hxqfRb6yFQcfyNRnDASWfMDzwe66eKmVeoPGykw@mail.gmail.com>
In-Reply-To: <CAAEKttyhPE0hxqfRb6yFQcfyNRnDASWfMDzwe66eKmVeoPGykw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

On 3/27/2015 2:01 PM, Tom Kacvinsky wrote:
> 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
>

compatibility is expected forward not backward.
New versions may have additional features that of course are not
available backward.

Regards
Marco

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

