From: Bryan Phelps <bryphe@outlook.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: Bug Report: Regression in Cygwin 2.11.0-1
Date: Sat, 01 Sep 2018 20:08:00 -0000 [thread overview]
Message-ID: <BL2PR16MB096188578C751002BF54F8E5C80E0@BL2PR16MB0961.namprd16.prod.outlook.com> (raw)
In-Reply-To: <20180901155435.GL6350@calimero.vinschen.de>
> As for the bug in question: I pushed a patch which should fix this
> issue. I created new developer snapshots and uploaded them to
> https://cygwin.com/snapshots/. Please give them a try.
Thank you Corinna for the quick fix and investigation!
I set up an environment to test it out: https://github.com/bryphe/test-ocaml-build and ran a build against the patched dll.
It looks like the patch fixes our scenario - the build is green with the patched dll: https://ci.appveyor.com/project/bryphe/test-ocaml-build, so the patch fixes our problem.
> On the other hand, those that will find problems, the people building
packages, will only do that on "official" releases.
I'm pretty new to the Cygwin ecosystem - we could certainly create nightly builds that test against cygwin releases, if that helps (and adjust our CLI script to grab the nightly / latest test release of Cygwin).
I wonder if, for a change like this, we could add a test case that exercises it - looking through the source, it looks like cygload.cc has a few test cases around pathing - perhaps it would be helpful to add a regression test for the minimal repro?
Thanks again for the help and investigation!
Bryan
--
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:[~2018-09-01 20:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-01 1:25 Bryan Phelps
2018-09-01 7:58 ` Andreas Hauptmann
2018-09-01 15:54 ` Corinna Vinschen
2018-09-01 16:42 ` David Allsopp
2018-09-01 19:22 ` Corinna Vinschen
2018-09-02 8:38 ` David Allsopp
2018-09-03 7:39 ` Corinna Vinschen
2018-09-03 19:13 ` Achim Gratz
2018-09-03 20:31 ` Corinna Vinschen
2018-09-01 22:05 ` Andrey Repin
2018-09-02 3:36 ` cyg Simple
2018-09-02 7:32 ` David Allsopp
2018-09-01 18:08 ` Houder
2018-09-01 19:24 ` Corinna Vinschen
2018-09-01 21:25 ` Houder
2018-09-01 20:08 ` Bryan Phelps [this message]
2018-09-01 8:03 ` Marco Atzeri
2018-09-01 8:11 ` Marco Atzeri
2018-09-01 8:31 ` David Allsopp
2018-09-01 9:07 ` Thomas Wolff
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=BL2PR16MB096188578C751002BF54F8E5C80E0@BL2PR16MB0961.namprd16.prod.outlook.com \
--to=bryphe@outlook.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).