From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Bug Report: Regression in Cygwin 2.11.0-1
Date: Mon, 03 Sep 2018 07:39:00 -0000 [thread overview]
Message-ID: <20180903073853.GP6350@calimero.vinschen.de> (raw)
In-Reply-To: <E51C5B015DBD1348A1D85763337FB6D901ADFF74F4@Remus.metastack.local>
[-- Attachment #1: Type: text/plain, Size: 1916 bytes --]
On Sep 2 08:37, David Allsopp wrote:
> Corinna Vinschen wrote:
> > On Sep 1 16:41, David Allsopp wrote:
> > > Corinna Vinschen wrote:
> > > > Some of the path handling is seriously crippled as soon as you start
> > > > using backslashes, and that's a delipberate decision and won't
> > > > change, even after fixing the aforementioned bug.
> > >
> > > I don't quite follow this - does that mean that that path definitely
> > > work even with a new Cygwin? i.e. our existing build system is
> > > permanently broken for Cygwin 2.11+?
> >
> > No. The problem we're talking about here is a regression and needs fixing, no
> > doubt about it.
> >
> > I was just saying that win32 paths *in general* get a less complete treatment
> > than POSIX paths for hopefully obvious reasons. Just be aware that \foo\bar is
> > not the same as /foo/bar and may even point to another file.
> >
> > 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.
>
> Thanks! That snapshot does indeed fix our build.
Thanks for testing.
> How feasible would it be to generate an alternate setup.ini
> (setup-snapshots.ini or something) and include the snapshots in the
> actual mirror with a switch to setup to select the alternate file?
> When we finally get to it with OCaml's CI, that is probably how I
> would configure our CI to operate (i.e. synchronise with a mirror,
> download the latest snapshot and then patch setup.ini), but I imagine
> there might be other projects which would set jobs running if it were
> very simple from upstream to do.
I'll release 2.11.1 today or tomorrow.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-09-03 7:39 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 [this message]
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
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=20180903073853.GP6350@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.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).