Re: Argument parsing with gcc compiled program

>* From: Marco Atzeri >* To: cygwin at cygwin dot com >* Date: Fri, 27 Nov 2015 18:08:44 +0100 >* Subject: Re: Argument parsing with gcc compiled program >* Authentication-results: sourceware.org; auth=none >* References: gmail dot com> <91DCAC3CB99C724EB365BB64677FBE7B01DFDC >at MX204CL04 dot

Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.4.0-0.4

2015-11-26 14:16 GMT+01:00 Corinna Vinschen : > Hi Kacper, > > On Nov 23 19:09, Kacper Michajlow wrote: >> 2015-11-21 17:24 GMT+01:00 Corinna Vinschen : >> > Hi Cygwin friends and users, >> > >> > >> > I released a new TEST version of Cygwin,

Re: Argument parsing with gcc compiled program

Gluszczak, Glenn writes: > Thanks for the email reference. Cygwin.dll always strips backslashes > so I'm stuck compiling with VS, ok. You can do a cross-compile from Cygwin to MinGW if you need Windows semantics. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk

Re: 64bit cygwin 2.4.0-0.4 hangs when pinging unresponsive host

On 27/11/2015 16:07, Corinna Vinschen wrote: 64 $ ping 2.2.2.2 PING 2.2.2.2 (2.2.2.2): 56 data bytes 2.2.2.2 PING Statistics 2 packets transmitted, 0 packets received, 100.0% packet loss the problem seems restricted to the 64bit test version of cygwin. I think this is pure

Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.4.0-0.4

2015-11-27 20:02 GMT+01:00 Kacper Michajlow : > 2015-11-26 14:16 GMT+01:00 Corinna Vinschen : >> Hi Kacper, >> >> On Nov 23 19:09, Kacper Michajlow wrote: >>> 2015-11-21 17:24 GMT+01:00 Corinna Vinschen : >>> > Hi Cygwin

Re: Argument parsing with gcc compiled program

On Fri, Nov 27, 2015 at 5:03 PM, Gluszczak, Glenn wrote: > Please look at my example again. The same program compiled with Visual > Studio does *not* > strip out the backslash whether run in cmd.exe or bash.exe. Other utilities > like Perl > do not strip out the backslash either. It is only

RE: Argument parsing with gcc compiled program

>On Fri, Nov 27, 2015 at 5:03 PM, Gluszczak, Glenn wrote: > Please look at my example again. The same program compiled with Visual > Studio does *not* > strip out the backslash whether run in cmd.exe or bash.exe. Other utilities > like Perl > do not strip out the backslash either. It is

Re: Argument parsing with gcc compiled program

On 27/11/2015 17:55, Gluszczak, Glenn wrote: On Fri, Nov 27, 2015 at 5:03 PM, Gluszczak, Glenn wrote: Please look at my example again. The same program compiled with Visual Studio does *not* strip out the backslash whether run in cmd.exe or bash.exe. Other utilities like Perl do not

Re: AVX on Cygwin

Corinna Vinschen writes: >> I hope this affects 64 bit only? I don't know if it would even be possible to run AVX code from 32bit, but yes, the three reports so far have been from 64bit systems. > Btw., for the time being it might be prudent to disable AVX in gmp... There is no configure option

RE: Argument parsing with gcc compiled program

>-Original Message- >From: Jan Nijtmans [mailto:jan.nijtm...@gmail.com] >Sent: Friday, November 27, 2015 4:30 AM >To: cygwin@cygwin.com >Subject: Re: Argument parsing with gcc compiled program > >2015-11-26 21:30 GMT+01:00 Gluszczak, Glenn : >> Sorry I should have

Incorrect Python errors when using os.remove to delete a directory

If I use os.remove in Python to remove a directory, I expect it to fail with an OSError on Python2 or a IsADirectoryError on Python3. On Python2, I get OSError, but with the wrong error code, whereas on Python3 I get completely the wrong exception. Simple testcases: $ rm -rf testdir &&

[newlib-cygwin] Fix race condition when waiting for a signal

https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=c43e9340f1bebe97d8e8ea683ec7f2bf911b5a85 commit c43e9340f1bebe97d8e8ea683ec7f2bf911b5a85 Author: Corinna Vinschen Date: Fri Nov 27 14:39:11 2015 +0100 Fix race condition when waiting for a signal

Re: AVX on Cygwin

On Nov 27 20:33, Achim Gratz wrote: > Corinna Vinschen writes: > >> I hope this affects 64 bit only? > > I don't know if it would even be possible to run AVX code from 32bit, > but yes, the three reports so far have been from 64bit systems. > > > Btw., for the time being it might be prudent to

Re: AVX on Cygwin

Corinna Vinschen writes: > On second thought, what I'm wondering about is what exactly *is* the > problem with AVX? While the AVX context isn't saved when running signal > handlers or getcontext, it's very unlikely that the AVX state changes at > all when running a system function or signal

[newlib-cygwin] Belatedly create release notes for commits 2f4fef9 and 9471b0b

https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=a4d1cb105366a0fc697d8b682229ca65b7cffeed commit a4d1cb105366a0fc697d8b682229ca65b7cffeed Author: Corinna Vinschen Date: Fri Nov 27 15:56:01 2015 +0100 Belatedly create release notes for commits 2f4fef9 and

Re: 64bit cygwin 2.4.0-0.4 hangs when pinging unresponsive host

On Nov 26 21:15, Corinna Vinschen wrote: > On Nov 25 22:01, Marco Atzeri wrote: > > > > > > On 25/11/2015 12:03, Marco Atzeri wrote: > > >On 25/11/2015 08:06, Thomas Wolff wrote: > > >>Am 24.11.2015 um 23:29 schrieb Marco Atzeri: > > >>> > > > > > >>>... > > >>>I assume it is an interaction with

Re: Incorrect Python errors when using os.remove to delete a directory

On Fri, Nov 27, 2015 at 3:51 PM, Adam Dinwoodie wrote: > If I use os.remove in Python to remove a directory, I expect it to fail > with an OSError on Python2 or a IsADirectoryError on Python3. On > Python2, I get OSError, but with the wrong error code, whereas on > Python3 I

TEST RELEASE: Cygwin 2.4.0-0.5

Hi Cygwin friends and users, I released a new TEST version of Cygwin, 2.4.0-0.5. There are three bugfixes compared to 2.4.0-0.4: - Fix handling of relative paths in native symlinks if the target is in a drive's root dir or one level below. Addresses:

[ANNOUNCEMENT] TEST RELEASE: Cygwin 2.4.0-0.5

Hi Cygwin friends and users, I released a new TEST version of Cygwin, 2.4.0-0.5. There are three bugfixes compared to 2.4.0-0.4: - Fix handling of relative paths in native symlinks if the target is in a drive's root dir or one level below. Addresses:

Re: AVX on Cygwin

On Nov 27 10:32, Corinna Vinschen wrote: > Hi Achim, > > On Nov 26 19:17, Achim Gratz wrote: > > > > You may have noted that the recent gmp update makes problems on some > > machines and two of the three reports come from Broadwell CPU. There is > > one thing that did indeed change with the

Re: AVX on Cygwin

On Nov 27 10:37, Corinna Vinschen wrote: > On Nov 27 10:32, Corinna Vinschen wrote: > > Hi Achim, > > > > On Nov 26 19:17, Achim Gratz wrote: > > > > > > You may have noted that the recent gmp update makes problems on some > > > machines and two of the three reports come from Broadwell CPU.

Re: [h-e-w] cygwin-64 2.3.1. bash fails when running under FSF emacs 24.5

Thanks, I'll look in that direction... Next question is where can I find an official Emacs 64-bit build? Went to the FAQ, read it at (https://www.gnu.org/software/emacs/manual/html_node/efaq-w32/Downloading.html) it says it should be on the ftp site and there would be both a 32 and 64 bit

Re: Argument parsing with gcc compiled program

2015-11-26 21:30 GMT+01:00 Gluszczak, Glenn : > Sorry I should have specified, this is not bash as this happens with the gcc > compiled > program within a Command Prompt session. > > > K:\>a.exe -s something "something d\:\\hello" > > Command-line arguments: > argv[0]

Re: AVX on Cygwin

Hi Achim, On Nov 26 19:17, Achim Gratz wrote: > > You may have noted that the recent gmp update makes problems on some > machines and two of the three reports come from Broadwell CPU. There is > one thing that did indeed change with the update and that is use of the > AVX ADC instruction on

Re: [h-e-w] cygwin-64 2.3.1. bash fails when running under FSF emacs 24.5

> Date: Fri, 27 Nov 2015 10:00:11 +0100 > From: Dominique de Waleffe > Cc: cygwin@cygwin.com, help-emacs-wind...@gnu.org > > Next question is where can I find an official Emacs 64-bit build? There is none. -- Problem reports: http://cygwin.com/problems.html FAQ: