unsubscribe

unsubscribe On Sat, Apr 18, 2020 at 3:50 PM wrote: > Send Cygwin mailing list submissions to > cygwin@cygwin.com > > To subscribe or unsubscribe via the World Wide Web, visit > http://cygwin.com/mailman/listinfo/cygwin > or, via email, send a message with subject or body 'help'

Re: Bug with Windows 10 console

On Saturday, April 18, 2020, 10:06:15 AM EDT, Thomas Wolff wrote:  >> So the interrupt handling has changed. >> Who is responsible. > It might help if you tell us *which* program behaves like that. https://cygwin.com/pipermail/cygwin/2020-February/243934.html Kevin -- Problem reports:

Re: Two naive questions

On Thu, Apr 16, 2020 at 08:21:56PM +, Fergus Daly wrote: >2. Since when the new look provided by >https://cygwin.com/pipermail/cygwin/ ? >Is there a way to default to the "legacy" look provided at, say, >https://sourceware.org/legacy-ml/cygwin/2019-04/ >but not obviously available today (even

Re: open write descriptor on named pipe sometime results in ENOENT

On 4/18/2020 5:48 PM, Ken Brown via Cygwin wrote: On 4/18/2020 11:24 AM, sten.kristian.ivars...@gmail.com wrote: Hey all We're trying to nail down some issues with using named pipes The issue we're getting is deterministic (ENXIO) but it is not this one, but we think this issue is worth

Re: open write descriptor on named pipe sometime results in ENOENT

On 4/18/2020 11:24 AM, sten.kristian.ivars...@gmail.com wrote: Hey all We're trying to nail down some issues with using named pipes The issue we're getting is deterministic (ENXIO) but it is not this one, but we think this issue is worth reporting anyway We're using the branch topic/fifo

Re: gfortran 9.3 write format error

Problem solved (probably). When setting out to downgrade gfortran, I found that there was a slight upgrade available - 9.3.0.1 to 9.3.0.2. I upgraded, ran "make clean" and "make test". This time it ran to completion with no error message. Seems unlikely this minor upgrade fixed a major

Re: gfortran 9.3 write format error

There was an error in my last message In fact, the current cygwin gfortran is 9.3.0, the current debian compiler is 8.3.0. I'll have to reflect upon that. -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:

Re: gfortran 9.3 write format error

Error in my last message - the current debian gfortran (8.3.0) is in fact older than the current cygwin fortran (9.3.0). So I'll try downgrading to 8.3.0 in cygwin. -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:

Re: gfortran 9.3 write format error

On 4/18/2020 11:23 AM, Brian Inglis wrote: what compiler version are you using on Debian $ gfortran --version GNU Fortran (Debian 8.3.0-6) 8.3.0 When support ended for g77 I feared for my collection of old fortran code, but it all worked fine under gfortran after a few trivial changes that I

Re: katomic and atomix will not run

On 2020-04-18 10:20, Eliot Moss wrote: > On 4/18/2020 11:40 AM, Phoenix Soul wrote: >> No, I haven't. What is it and how do I run one? >> >> On Fri, Apr 17, 2020 at 3:23 PM Eliot Moss > > wrote: >> >>     On 4/17/2020 5:16 PM, Phoenix Soul via Cygwin wrote: >> > I

Help

Help On Sat, Apr 18, 2020 at 11:42 wrote: > Send Cygwin mailing list submissions to > cygwin@cygwin.com > > To subscribe or unsubscribe via the World Wide Web, visit > http://cygwin.com/mailman/listinfo/cygwin > or, via email, send a message with subject or body 'help' to >

Re: gfortran 9.3 write format error

> As I did not recognize 1p[23]e... as a repeated format, it is possible that > gfortran now requires you to specify that in a more standards compliant manner, > except perhaps if you compile with -std=legacy (and the runtime supports that in > formatted I/O format strings), otherwise you may

Re: gfortran 9.3 write format error (was: segfaulting on valid write statements)

On 2020-04-17 23:16, Charles Russell wrote: > On 4/17/2020 8:01 PM, Brian Inglis wrote: >> On 2020-04-17 17:33, Charles Russell wrote: >>> At line 889 of file cgcrez.f (unit = 6, file = 'stdout') >>> Fortran runtime error: Missing initial left parenthesis in format >>> ^ >>> Here is the indicated

Re: katomic and atomix will not run

On 4/18/2020 11:40 AM, Phoenix Soul wrote: No, I haven't. What is it and how do I run one? On Fri, Apr 17, 2020 at 3:23 PM Eliot Moss mailto:m...@cs.umass.edu>> wrote: On 4/17/2020 5:16 PM, Phoenix Soul via Cygwin wrote: > I decided that I was going to get katomic and atomix for

Re: Cygwin Digest, Vol 2, Issue 48

On Sat, Apr 18, 2020, 8:42 AM wrote: > Send Cygwin mailing list submissions to > cygwin@cygwin.com > > To subscribe or unsubscribe via the World Wide Web, visit > http://cygwin.com/mailman/listinfo/cygwin > or, via email, send a message with subject or body 'help' to >

Re: katomic and atomix will not run

No, I haven't. What is it and how do I run one? On Fri, Apr 17, 2020 at 3:23 PM Eliot Moss wrote: > On 4/17/2020 5:16 PM, Phoenix Soul via Cygwin wrote: > > I decided that I was going to get katomic and atomix for cygwin, and > > selected the most recent version listed. > > atomix refuses to

open write descriptor on named pipe sometime results in ENOENT

Hey all We're trying to nail down some issues with using named pipes The issue we're getting is deterministic (ENXIO) but it is not this one, but we think this issue is worth reporting anyway We're using the branch topic/fifo The program explained in short is: - One main (parent) pipe

Re: setup-x86_64.exe --quiet-mode issues using Management Tools

On 15/04/2020 16:02, KAVALAGIOS Panagiotis (EEAS-EXT) wrote: From: Cygwin On Behalf Of Paul Isaacson Hello Cygwin Support, I am trying to install Cygwin silently through a management tool like SCCM (called Bigfix). I went through the FAQ on your website to see what commands/switches existed.

Re: Bug with Windows 10 console

Am 18.04.2020 um 14:42 schrieb ak...@free.fr: Hi, Bonjour To day, all programs are upgraded permanently. A good and a bad thing. Windows 10, cygwin ... One recent upgrade, I don't target exactly which one, has broken my environment. Current versions as reported by cygcheck :  Windows 10

Updated: neomutt-20200417-1

Version 20200417-1 of neomutt has been uploaded. The command line mail reader neomutt reached version 20200417. On GitHub it is possible to find the changelog for the new release: https://github.com/neomutt/neomutt/releases Federico

[ANNOUNCEMENT] Updated: neomutt-20200417-1

Version 20200417-1 of neomutt has been uploaded. The command line mail reader neomutt reached version 20200417. On GitHub it is possible to find the changelog for the new release: https://github.com/neomutt/neomutt/releases Federico -- Problem reports: https://cygwin.com/problems.html

Bug with Windows 10 console

Hi, To day, all programs are upgraded permanently. A good and a bad thing. Windows 10, cygwin ... One recent upgrade, I don't target exactly which one, has broken my environment. Current versions as reported by cygcheck :  Windows 10 Professional Ver 10.0 Build 18363  cygwin 3.1.4-1 OK