cygwin coreutils-5.3.0-4 rm change breaks Libtool

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Mittwoch, 13. April 2005 03:50 To: cygwin@cygwin.com Subject: cygwin Digest 13 Apr 2005 01:49:36 - Issue 4198 cygwin coreutils-5.3.0-4 rm change breaks Libtool 106161 by: [EMAIL PROTECTED] (Eric Blake) 106164 by: Christop

AW: More error level issues

> > - Right shift exit code by eight when not started in a cygwin environment > > If you want to see if this helps in your situation, try a recent snapshot > (<http://cygwin.com/snapshots/>). > Thanks! A quick test proves that cygwin1-20050404.dll solves the problem pro

gawk: Bad File Descriptor error with concurrent readonly access to a network file

We let thousands of tiles undergo the same time consuming processing tasks. We use a multi core Windows 7 workstation running several tiles simultaneously in separate shell windows (parallel processing). A batch script controls the work flow of the task with gawk interpreting a number of setup /

Re: gawk: Bad File Descriptor error with concurrent readonly access to a network file

On Fri, 25 Sep 2015 18:58:57 +0200, Marco Atzeri wrote: >> "Bad file descriptor" just arose recently in another problem >> https://cygwin.com/ml/cygwin/2015-09/msg00374.html >> https://cygwin.com/ml/cygwin/2015-09/msg00436.html >> I don't think this applies to our case. We use massive parallel proc

Re: Cygwin bash for loops : repeated errors : [main] bash 1972 fork: child -1 - CreateProcessW failed for errno 9 bash: fork: Bad file descriptor

Hi Paul, I also get Bad File Descriptor errors, though in a quite different situation, see my recent topic "gawk: Bad File Descriptor error with concurrent readonly access to a network file" on Sep 25. There seems to be some issue in some file opening process that occurs with parallel processes

Re: gawk: Bad File Descriptor error with concurrent readonly access to a network file

Marco suggested I should wait for Corinna being back for that issue. Did you ever look into that, Corinna? For your info, my first mail in that thread contains a description and test case. Thanks, Wolfgang -Original Message- From: Vermessung AVT - Wolfgang Rieger Sent: Sa, 26

Re: gawk: Bad File Descriptor error with concurrent readonly access to a network file

From: Corinna Vinschen [mailto:corinna-cyg...@cygwin.com] Sent: Tuesday, October 27, 2015 10:53 To: cygwin@cygwin.com Subject: Re: gawk: Bad File Descriptor error with concurrent readonly access to a network file (Snip) > Cygwin uses full sharing for all files it opens, unless the file is opened

Mailing list Digest: Inconvenient format change: no more thread grouping, long message names

Dear all, a couple of months ago there was a change in the Cygwin mailing list Digest: There is no longer an overview in the mail text, sorted by thread, that referenced the mails by number. This is in my opinion a backstep in viewing the digest at least for use with MS Outlook: 1) With the ov

RE: gawk 4.1.4: CR separate char for CRLF files

On Wed, 9 Aug 2017 10:38 +, Jannick wrote: --- snip --- > Now I can see the following *easy* solutions to the very situation here > (input only for now): > > 1 - Inserting the BEGIN section as you suggested into more than 1k scripts > (not feasible due to additional regression test workload)

Re: gawk 4.1.4: CR separate char for CRLF files

Achim Gratz wrote: Vermessung AVT - Wolfgang Rieger writes: > Another solution which we have been using for many years now, though > it might not be feasible for you: Cygwin is, like it or not, a rolling distribution. > We very rarely update Cygwin. We have been using Cygwin fo

Re: gawk 4.1.4: CR separate char for CRLF files

Achim Gratz wrote: Vermessung AVT - Wolfgang Rieger writes: > Another solution which we have been using for many years now, though > it might not be feasible for you: - snip Jannick, another idea I had thought of previously