Re: Bug Report: Regression in Cygwin 2.11.0-1

On 9/1/2018 5:52 PM, Andrey Repin wrote: > 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

Advice on setting Cygwin build parameters for OpenSC.

Hi, I’ve been talking to Doug Engert, one of the maintainers for the OpenSC project, and we could do with some advice on how best to set the build parameters for building OpenSC via Cygwin. The good news is that with a small tweak to the current stock configure.ac, OpenSC builds nicely and

Re: Cygwin fails to utilize Unicode replacement character

On Sat, 1 Sep 2018 15:50:04, Doug Henderson wrote: This is an issue with rendering the character in the terminal window. In both the CMD/Conhost/bash and Mintty/bash terminals, I have configure the font to be Lucinda Console. This font does not have a glyph for U+FFFD: Replacement Character. (To

Re: Bug Report: Regression in Cygwin 2.11.0-1

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

Re: [ANNOUNCEMENT] Updated: Cygwin 2.11.0-1

On 9/1/2018 2:52 PM, tl...@twcny.rr.com wrote: Now I can't get 2.11.0-1. I tried over 20 mirrors and none of them have the update. Are you sure you don't have it already? Try 'cygcheck -cd cygwin' to find out: $ cygcheck -cd cygwin Cygwin Package Information Package Version

Re: Cygwin fails to utilize Unicode replacement character

On Sat, 1 Sep 2018 at 10:13, Steven Penny wrote: ... > You get this result with Linux: > > $ cat alfa.txt > � ... > with Cygwin you get this: > > $ cat alfa.txt > ▒ ... This is an issue with rendering the character in the terminal window. In both the CMD/Conhost/bash and

Re: Bug Report: Regression in Cygwin 2.11.0-1

On Sat, 1 Sep 2018 21:23:56, Corinna Vinschen wrote: > > Yes, you would run the chance that you would have to mend an official > > release several times ... but is that bad? > > The idea of test releases is to avoid problem like the one we're discussing > here in official releases. I'd like to

Re: Cygwin fails to utilize Unicode replacement character

Am 01.09.2018 um 20:46 schrieb Steven Penny: On Sat, 1 Sep 2018 20:11:15, Thomas Wolff wrote: Which terminals are used and what's the output of `locale` and `cat --version` in both cases? ... Note that in addition to Linux, Windows PowerShell also gives correct output:    $ pwsh -c

Re: Bug Report: Regression in Cygwin 2.11.0-1

> 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:

Re: Cygwin fails to utilize Unicode replacement character

On Sep 1 09:13, Steven Penny wrote: > Using this file: > >$ printf '\353\n' > alfa.txt > >$ iconv -f CP1252 alfa.txt >ë > > You get this result with Linux: > >$ cat alfa.txt >� > > Where "cat" properly outputs Unicode 'REPLACEMENT CHARACTER' (U+FFFD). However > with

[newlib-cygwin] Cygwin: console: Print Unicode REPLACEMENT CHARACTER for invalid input chars

https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=d1454de7b03c93556c33c33c5fd8db288ab4feac commit d1454de7b03c93556c33c33c5fd8db288ab4feac Author: Corinna Vinschen Date: Sat Sep 1 21:34:34 2018 +0200 Cygwin: console: Print Unicode REPLACEMENT CHARACTER for invalid input chars

Re: Bug Report: Regression in Cygwin 2.11.0-1

On Sep 1 20:08, Houder wrote: > On Sat, 1 Sep 2018 17:54:35, Corinna Vinschen wrote: > > I'll fix this and release a 2.11.1 soon, but I still have a question: > > > > Why do I push out test releases if nobody cares? > > Yes, I know, it is a _hypothetical_question_. You do not really expect > an

Re: Bug Report: Regression in Cygwin 2.11.0-1

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

[newlib-cygwin] Cygwin: fix Win32 path ".." backtracking

https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=3a880bf5e0e4a11719c4ca1e42bd718e712fb0d2 commit 3a880bf5e0e4a11719c4ca1e42bd718e712fb0d2 Author: Corinna Vinschen Date: Sat Sep 1 21:01:08 2018 +0200 Cygwin: fix Win32 path ".." backtracking Commit

RE: [ANNOUNCEMENT] Updated: Cygwin 2.11.0-1

Am 31.08.2018 um 22:31 schrieb tl...@twcny.rr.com: > After running setup (64 bit) I still have version 2.10. I even tried > uninstalling and running setup again. > > Tom L have you stopped all processes including services before the update ? The problem turned out to be that the mirror I was

RE: [ANNOUNCEMENT] Updated: Cygwin 2.11.0-1

I don't see it on the 20-plus mirrors I tried. Tom L -Original Message- From: tl...@twcny.rr.com Sent: Friday, August 31, 2018 4:31 PM To: cygwin@cygwin.com Subject: RE: [ANNOUNCEMENT] Updated: Cygwin 2.11.0-1 After running setup (64 bit) I still have version 2.10. I even tried

Re: Cygwin fails to utilize Unicode replacement character

On Sat, 1 Sep 2018 20:11:15, Thomas Wolff wrote: Which terminals are used and what's the output of `locale` and `cat --version` in both cases? Linux: $ echo "$TERM" xterm-256color $ locale LANG=en_US.UTF-8 LC_CTYPE="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8"

Re: Cygwin fails to utilize Unicode replacement character

Am 01.09.2018 um 18:13 schrieb Steven Penny: Using this file:    $ printf '\353\n' > alfa.txt    $ iconv -f CP1252 alfa.txt    ë You get this result with Linux:    $ cat alfa.txt    � Where "cat" properly outputs Unicode 'REPLACEMENT CHARACTER' (U+FFFD). However with Cygwin you get this:

Re: Bug Report: Regression in Cygwin 2.11.0-1

On Sat, 1 Sep 2018 17:54:35, Corinna Vinschen wrote: > I'll fix this and release a 2.11.1 soon, but I still have a question: > > Why do I push out test releases if nobody cares? Yes, I know, it is a _hypothetical_question_. You do not really expect an answer. However it was my thought exactly.

RE: Bug Report: Regression in Cygwin 2.11.0-1

Corinna Vinschen wrote: > On Sep 1 09:56, Andreas Hauptmann wrote: > > On Sat, 1 Sep 2018 01:24:49 + > > Bryan Phelps wrote: > > > > > I'll continue to look around for a more minimal repro, > > > > The normalization of paths with backslashes has changed. > > > > The following doesn't work any

Cygwin fails to utilize Unicode replacement character

Using this file: $ printf '\353\n' > alfa.txt $ iconv -f CP1252 alfa.txt ë You get this result with Linux: $ cat alfa.txt � Where "cat" properly outputs Unicode 'REPLACEMENT CHARACTER' (U+FFFD). However with Cygwin you get this: $ cat alfa.txt ▒ Where "cat" outputs

Re: Bug Report: Regression in Cygwin 2.11.0-1

On Sep 1 09:56, Andreas Hauptmann wrote: > On Sat, 1 Sep 2018 01:24:49 + > Bryan Phelps wrote: > > > I'll continue to look around for a more minimal repro, > > The normalization of paths with backslashes has changed. > > The following doesn't work any longer: > > cd /tmp > stat

Re: New Cygwin Version

Am 01.09.2018 um 11:57 schrieb Thomas Lake: I tried my usual mirror but it hadn’t been updated yet. When I tried a different mirror it worked. mirros are not handled directly by the cygwin project https://cygwin.com/mirrors.html --- Diese E-Mail wurde von Avast Antivirus-Software auf Viren

[ANNOUNCEMENT] Updated: Perl distributions

The following Perl distributions have been updated to their latest version on CPAN, respectively: x86/x86_64 -- perl-Cpanel-JSON-XS-4.06-1 perl-DateTime-1.50-1 perl-Net-DNS-SEC-1.10-1 perl-YAML-LibYAML-0.74-1 noarch -- perl-Archive-Zip-1.63-1 perl-CGI-4.40-1 perl-Date-Manip-6.73-1

Updated: Perl distributions

The following Perl distributions have been updated to their latest version on CPAN, respectively: x86/x86_64 -- perl-Cpanel-JSON-XS-4.06-1 perl-DateTime-1.50-1 perl-Net-DNS-SEC-1.10-1 perl-YAML-LibYAML-0.74-1 noarch -- perl-Archive-Zip-1.63-1 perl-CGI-4.40-1 perl-Date-Manip-6.73-1

New Cygwin Version

I tried my usual mirror but it hadn’t been updated yet. When I tried a different mirror it worked. Sent from Mail for Windows 10 -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/

Re: Bug Report: Regression in Cygwin 2.11.0-1

Am 01.09.2018 um 10:10 schrieb Marco Atzeri: Am 01.09.2018 um 03:24 schrieb Bryan Phelps: Hello, Thank you for all the work on Cygwin! I've been using it to spin up an environment to build the OCaml compiler / toolchain, and it was working great. However, today, all our CI builds

RE: Bug Report: Regression in Cygwin 2.11.0-1

Marco Atzeri wrote: > Am 01.09.2018 um 03:24 schrieb Bryan Phelps: > > Hello, > > > > > > Thank you for all the work on Cygwin! I've been using it to spin up an > environment to build the OCaml compiler / toolchain, and it was working great. > > > > > > However, today, all our CI builds

Re: Bug Report: Regression in Cygwin 2.11.0-1

Am 01.09.2018 um 03:24 schrieb Bryan Phelps: Hello, Thank you for all the work on Cygwin! I've been using it to spin up an environment to build the OCaml compiler / toolchain, and it was working great. However, today, all our CI builds mysteriously started failing - at first, I suspected

Re: Bug Report: Regression in Cygwin 2.11.0-1

Am 01.09.2018 um 03:24 schrieb Bryan Phelps: Hello, In the meantime - is there a way we can pin the cygwin package to the 2.10.0-1 version, to unblock our builds? Thank you! Bryan What is the problem in installing the previous version of the package ? --- Diese E-Mail wurde von Avast

Re: Bug Report: Regression in Cygwin 2.11.0-1

On Sat, 1 Sep 2018 01:24:49 + Bryan Phelps wrote: > I'll continue to look around for a more minimal repro, The normalization of paths with backslashes has changed. The following doesn't work any longer: cd /tmp stat "..\bin\file.exe" # or stat "..\\bin\\file.exe" This however

Re: error in "cygpath" behavior

Am 31.08.2018 um 22:05 schrieb Eric Blake: On 08/31/2018 02:48 PM, cyg Simple wrote: Don't forget the possibility that '..' points to a symlink which Windows will not understand. $ mkdir -p /foo/baz $ ln -s /foo /bar $ cd /bar/baz $ cygpath -w .. Except .. never points to a symlink.  It

Re: error in "cygpath" behavior

On 2018-08-31 16:34, Steven Penny wrote: > On Fri, 31 Aug 2018 10:57:34, Corinna Vinschen wrote: >> Long-standing behaviour.  ".." in Cygwin and ".." in Windows can totally >> disagree.  The path is always convert to absolute at this point in favor >> of correct output.  There's also the

Re: error in "cygpath" behavior

Steven Penny writes: > I am not understanding - it appears that "dot-dot" (..) is well defined by > POSIX: […] > so it would appears that ".." would be an acceptable return value in any case. Except that you've asked for a Windows path, not POSIX, and you have no idea what Windows' idea of the