From: Steven Penny <svnpenn@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Link error with static version of zlib?
Date: Fri, 21 Jul 2017 10:11:00 -0000 [thread overview]
Message-ID: <59715271.482cca0a.8fce9.85d2@mx.google.com> (raw)
In-Reply-To: <003a8d3c-691b-738f-96e7-ec3bf53b82a9@t-online.de>
On Thu, 20 Jul 2017 20:59:00, =?UTF-8?Q?Hans-Bernhard_Br=c3=b6ker?= wrote:
> And that's where you went off in the wrong direction. You're writing to
> the Cygwin mailing, but that's the MSYS2 package repository. Those are
> two different environments, so you should _not_ mix up them up like that.
This is a pretty awful response. The MSYS2 part of my answer, the part OP tried
is certainly possible. When Cygwin package maintainers are ignoring serious
package issues for months:
- http://cygwin.com/ml/cygwin/2017-07/msg00055.html
- http://github.com/cygwinports/mingw64-x86_64-expat/issues/1
- http://github.com/cygwinports/mingw64-x86_64-lua/issues/1
- http://github.com/cygwinports/mingw64-x86_64-nghttp2/issues/1
- http://github.com/cygwinports/mingw64-x86_64-pcre/issues/1
it is not wrong to seek a sane alternative, which this is. You certainly can mix
these as in this case we are not involving the Cygwin DLL. To J (OP), if you
want a real answer and not this brush off, repost your question here and I will
try to work with you:
http://github.com/svnpenn/glade
as technically your original question has already been answered (by me), and
your new issue is outside the scope of this mailing list.
--
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 prev parent reply other threads:[~2017-07-21 1:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-19 15:47 J
2017-07-20 14:07 ` Steven Penny
2017-07-20 14:16 ` J
2017-07-21 0:32 ` Hans-Bernhard Bröker
2017-07-21 10:11 ` Steven Penny [this message]
2017-07-24 23:55 ` J (Jean-Claude Gervais)
2017-07-25 14:42 ` cyg Simple
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=59715271.482cca0a.8fce9.85d2@mx.google.com \
--to=svnpenn@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).