On Mon, Sep 19, 2022 at 07:54:11PM -0400, Ken Brown wrote:
>
> On 9/19/2022 6:05 PM, Enrico Forestieri wrote:
> > Ken Brown wrote:
> > >
> > > I did an internet search on this issue and found the following, which
> > > describes the
> > >
> > > situation we're discussing:
> > >
> > > https://s
> It seems that there's an exception: If no process has ever had the FIFO open
> for
> writing since it was opened for reading, then the FIFO is not considered to be
> at end-of-file.
IMO, when a virgin FIFO is read with a blocking read (of just one byte), it
will block -- it will not return 0.
On 9/19/2022 6:05 PM, Enrico Forestieri wrote:
Ken Brown wrote:
> I did an internet search on this issue and found the following, which
describes the
> situation we're discussing:
https://stackoverflow.com/questions/14594508/fifo-pipe-is-always-readable-in-select
> According to that po
Ken Brown wrote:
> I did an internet search on this issue and found the following, which
describes the
> situation we're discussing:
https://stackoverflow.com/questions/14594508/fifo-pipe-is-always-readable-in-select
> According to that post, select on Linux will wait for a writer the
fi
On 9/19/2022 5:25 PM, Ken Brown wrote:
You're probably not calling select to check for read ready on
non-blocking FIFOs that have no writers.
Exactly what I was thinking (while on the bus).
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq
On 9/19/2022 3:53 PM, Norton Allen wrote:
On 9/19/2022 3:50 PM, Norton Allen wrote:
On 9/19/2022 3:15 PM, Ken Brown wrote:
On 9/18/2022 5:45 PM, Enrico Forestieri wrote:
Hi,
I think I am experiencing a problem with fifos on cygwin. The attached
C source (fifocomm.c) creates two pipes (/tmp/p
We're running into this same issue on my project. We're trying to
shorten path names to get around Visual Studio limitations in path
lengths, which are unfortunately very long for us since we're
generating filenames based on package names and the like.
If subst won't work to let us shorten path n
On 9/19/2022 3:50 PM, Norton Allen wrote:
On 9/19/2022 3:15 PM, Ken Brown wrote:
On 9/18/2022 5:45 PM, Enrico Forestieri wrote:
Hi,
I think I am experiencing a problem with fifos on cygwin. The attached
C source (fifocomm.c) creates two pipes (/tmp/pipe.{in,out}), expecting
to receive inputs
On 9/19/2022 3:15 PM, Ken Brown wrote:
On 9/18/2022 5:45 PM, Enrico Forestieri wrote:
Hi,
I think I am experiencing a problem with fifos on cygwin. The attached
C source (fifocomm.c) creates two pipes (/tmp/pipe.{in,out}), expecting
to receive inputs from /tmp/pipe.in and replying to /tmp/pipe
On 9/19/2022 4:23 AM, Rony Ross wrote:
I've been using the USO feature and it works well. Thanks!
Was this feature officially released?
No, it will be in the next major release (3.4.0), probably before the end of the
year.
Ken
--
Problem reports: https://cygwin.com/problems.html
FAQ:
On 9/18/2022 5:45 PM, Enrico Forestieri wrote:
Hi,
I think I am experiencing a problem with fifos on cygwin. The attached
C source (fifocomm.c) creates two pipes (/tmp/pipe.{in,out}), expecting
to receive inputs from /tmp/pipe.in and replying to /tmp/pipe.out.
Compiling this source on linux and
The following packages have been uploaded to the Cygwin distribution:
* cygport-0.35.3-1
cygport is the standard method for building and maintaining
packages for the Cygwin distribution.
Highlights of this release:
* cygport now warns if HOMEPAGE (which should contain a URL) or LICENSE
(whi
I've been using the USO feature and it works well. Thanks!
Was this feature officially released?
Regards,
Rony
On Tue, 24 May 2022 at 08:50, wrote:
>
> Could you please make such test version? I should be able to verify it.
>
>
>
> Regard,
>
> Rony
--
Problem reports: https://cygwin.com/p
13 matches
Mail list logo
