From: Tom Kacvinsky <tom.kacvinsky@vectorcast.com>
To: cygwin@cygwin.com
Subject: Fwd: Compatibility of binaries built with one version of cygwin with other versions of cygwin
Date: Fri, 27 Mar 2015 13:12:00 -0000 [thread overview]
Message-ID: <CAAEKttyhPE0hxqfRb6yFQcfyNRnDASWfMDzwe66eKmVeoPGykw@mail.gmail.com> (raw)
In-Reply-To: <CAAEKttyS4UaLyvMRucn==kBGZCfZJVw_r_hxP1i+HXmSZFgDvQ@mail.gmail.com>
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
next parent reply other threads:[~2015-03-27 13:01 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 [this message]
2015-03-27 13:23 ` Bryan Berns
2015-03-27 14:29 ` Fwd: " Marco Atzeri
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=CAAEKttyhPE0hxqfRb6yFQcfyNRnDASWfMDzwe66eKmVeoPGykw@mail.gmail.com \
--to=tom.kacvinsky@vectorcast.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).