From: Andrey Repin <anrdaemon@yandex.ru>
To: David Allsopp <David.Allsopp@cl.cam.ac.uk>, cygwin@cygwin.com
Subject: Re: Bug Report: Regression in Cygwin 2.11.0-1
Date: Sat, 01 Sep 2018 22:05:00 -0000 [thread overview]
Message-ID: <1177432276.20180902005232@yandex.ru> (raw)
In-Reply-To: <E51C5B015DBD1348A1D85763337FB6D901ADFF2257@Remus.metastack.local>
Greetings, David Allsopp!
>> In terms of this OCAML build system problem:
>>
>> Please fix your build system. Do not mix POSIX and Win32 paths, use POSIX
>> paths only. Backslashes are *no* drop-in replacement for slashes.
> The "problem" for us is more subtle than this. The program which is
> generating that path is not a Cygwin executable, so it is correctly
> combining a path it has been supplied (the ../stdlib which has been supplied
> via Cygwin's make) with a filename, so it uses a backslash. It's been on my
> TODO for years to enhance to understand that the program it's supplying the
> path back to is a Cygwin executable and so sort it out properly but, well,
> we're a small number of maintainers! That said, WSL is forcing us to address it properly...
You CAN just send back forward slashes. Windows don't care.
If any program would choke, it would be that program's problem after all.
--
With best regards,
Andrey Repin
Sunday, September 2, 2018 0:51:18
Sorry for my terrible english...
--
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 22:05 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 [this message]
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=1177432276.20180902005232@yandex.ru \
--to=anrdaemon@yandex.ru \
--cc=David.Allsopp@cl.cam.ac.uk \
--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).