This is the mail archive of the
mailing list for the Cygwin project.
Re: Piping on 64-bit Cygwin was Re: [ANNOUNCEMENT] llvm 3.7.1-2
- From: Warren Young <wyml at etr-usa dot com>
- To: The Cygwin Mailing List <cygwin at cygwin dot com>
- Date: Tue, 21 Jun 2016 15:57:47 -0600
- Subject: Re: Piping on 64-bit Cygwin was Re: [ANNOUNCEMENT] llvm 3.7.1-2
- Authentication-results: sourceware.org; auth=none
- References: <1989991589 dot 1040675 dot 1465521483978 dot JavaMail dot yahoo dot ref at mail dot yahoo dot com> <1989991589 dot 1040675 dot 1465521483978 dot JavaMail dot yahoo at mail dot yahoo dot com> <6ecc2a84-449f-01f1-0ef7-440e97a9b850 at dronecode dot org dot uk> <1341561944 dot 11163115 dot 1466484828091 dot JavaMail dot yahoo at mail dot yahoo dot com>
On Jun 20, 2016, at 10:53 PM, email@example.com wrote:
> Yes, it's the same piping problem of three years ago.
âwhere you were asked to provide a simple test case for the problem, instead of âcompile admittedly difficult-to-build package Geomview and use it against one of the most complicated packages in Cygwin, OpenGL.â
Hereâs what a simple test case looks like:
$ dd if=/dev/urandom bs=4k count=4m |
gpg -c --force-mdc |
gpg -d > /dev/null
Type the same passphrase three times: twice to verify it for encryption, and once for decryption. The fact that this runs without errors proves that Cygwin 64 is capable of reliably transporting 16 GiB of data through a pipe without corruption.
Try it on your system. If it gives an error, it shows that the problem is system-specific, and thus possibly BLODA or some other platform issue.
If not, then please explain how your problem differs from the demonstration here.
Have you ruled out Cygwinâs OpenGL package, such as by running it over X11 to a remote system running a different implementation?
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple