public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Fwd: Compatibility of binaries built with one version of cygwin with other versions of cygwin
Date: Fri, 27 Mar 2015 14:29:00 -0000	[thread overview]
Message-ID: <551559CA.3010101@gmail.com> (raw)
In-Reply-To: <CAAEKttyhPE0hxqfRb6yFQcfyNRnDASWfMDzwe66eKmVeoPGykw@mail.gmail.com>

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

      parent reply	other threads:[~2015-03-27 13:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAAEKttyS4UaLyvMRucn==kBGZCfZJVw_r_hxP1i+HXmSZFgDvQ@mail.gmail.com>
2015-03-27 13:12 ` Tom Kacvinsky
2015-03-27 13:23   ` Bryan Berns
2015-03-27 14:29   ` Marco Atzeri [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=551559CA.3010101@gmail.com \
    --to=marco.atzeri@gmail.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).