From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: fflush(NULL) clobbers input streams
Date: Tue, 18 Jul 2017 18:33:00 -0000 [thread overview]
Message-ID: <87o9shlhmj.fsf@Rainer.invalid> (raw)
In-Reply-To: <20170718095456.GC26902@calimero.vinschen.de> (Corinna Vinschen's message of "Tue, 18 Jul 2017 11:54:56 +0200")
Corinna Vinschen writes:
> On Jul 17 19:53, Achim Gratz wrote:
>> It seems that fflush is only supposed to discard buffered input data on
>> seekable files, but not pipes (per POSIX.1-2008), so this looks a
>> regression to me.
>
> Did you try to bisect the issue?
I've had to bin the build environment at work due to the disk running
out of space and the one at home went poof when the SSD it was on
croaked. I haven't had the time yet to get it up again on the
replacement.
Anyway, if my hunch that 5.22.3 was not running into this issue is
correct, then 2.7.0 was the last released Cygwin version this test was
passing for. I might try to get that running on of my home machines
again, but I can't really spend all that much time on it for the
foreseeable future unfortunately.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptation for Waldorf microQ V2.22R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
prev parent reply other threads:[~2017-07-18 18:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-17 17:53 Achim Gratz
2017-07-18 9:55 ` Corinna Vinschen
2017-07-18 10:51 ` Corinna Vinschen
2017-07-18 19:21 ` Achim Gratz
2017-07-18 22:41 ` Ken Brown
2017-07-19 2:16 ` Ken Brown
2017-07-19 8:46 ` Corinna Vinschen
2017-07-19 17:03 ` [GOLDSTAR] " Corinna Vinschen
2017-07-19 17:20 ` Ken Brown
2017-07-19 20:40 ` Andrew Schulman
2017-07-19 17:11 ` Achim Gratz
2017-07-19 17:03 ` Achim Gratz
2017-07-18 18:33 ` Achim Gratz [this message]
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=87o9shlhmj.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=cygwin-apps@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).