[ANNOUNCEMENT] Updated: Cygwin 1.7.15

[ANNOUNCEMENT] Updated: Cygwin 1.7.15

[Corinna Vinschen]

Hi Cygwin friends and users,


I just released 1.7.15.  This is a bugfix release.  Only one new feature
has been added.

Cygwin itself is now packaged using cygport as well.


What's new:
===========

- Add CYGWIN=pipe_byte option to force opening of pipes in byte mode
  rather than message mode.

Bug fixes:
==========

- Fix output of mkpasswd -c option in case $HOME is set at the time.
  Fixes: http://cygwin.com/ml/cygwin/2012-05/msg00094.html

- Fix problem where too much input was attempted to be read from a
  pty slave.  Fixes: http://cygwin.com/ml/cygwin/2012-05/msg00049.html

- Fix problem setting parent pid to 1 when process with children execs
  itself.  Fixes: http://cygwin.com/ml/cygwin/2012-05/msg00009.html

- Fix fesetround and fesetprec to allow all valid input parameters.
  Fixes: http://cygwin.com/ml/cygwin/2012-05/msg00010.html

- Avoid "WARNING: Couldn't compute FAST_CWD pointer." message on
  Windows 8 Customer Preview 32 bit. 
  Fixes: http://cygwin.com/ml/cygwin/2012-04/msg00616.html

- Don't make Cygwin wait for all children of a non-cygwin child program.
  Fixes: http://cygwin.com/ml/cygwin/2012-05/msg00063.html,
	 http://cygwin.com/ml/cygwin/2012-05/msg00075.html


Have fun,
Corinna


    *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO ***

If you want to unsubscribe from the cygwin-announce mailing list, look
at the "List-Unsubscribe: " tag in the email header of this message.
Send email to the address specified there. It will be in the format:

cygwin-announce-unsubscribe-you=yourdomain.com@cygwin.com

If you need more information on unsubscribing, start reading here:

http://sourceware.org/lists.html#unsubscribe-simple

Please read *all* of the information on unsubscribing that is available
starting at this URL.

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: [ANNOUNCEMENT] Updated: Cygwin 1.7.15

[Thomas Wolff]

Am 10.05.2012 08:28, schrieb Corinna Vinschen:
> Hi Cygwin friends and users,
>
>
> I just released 1.7.15.  This is a bugfix release.  Only one new feature
> has been added.
>
> ...
>
> Bug fixes:
> ==========
>
> - Fix ...
>    Fixes: http://cygwin.com/ml/cygwin/2012-05/msg00094.html
It's a great idea (and very professional :) ) to include references to 
the fixed issues in the announcement.
Thanks and keep on...
Thomas

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: [ANNOUNCEMENT] Updated: Cygwin 1.7.15

[Christopher Faylor]

On Thu, May 10, 2012 at 08:51:49AM +0200, Thomas Wolff wrote:
>Am 10.05.2012 08:28, schrieb Corinna Vinschen:
>> Hi Cygwin friends and users,
>>
>>
>> I just released 1.7.15.  This is a bugfix release.  Only one new feature
>> has been added.
>>
>> ...
>>
>> Bug fixes:
>> ==========
>>
>> - Fix ...
>>    Fixes: http://cygwin.com/ml/cygwin/2012-05/msg00094.html
>It's a great idea (and very professional :) ) to include references to 
>the fixed issues in the announcement.
>Thanks and keep on...

FWIW, I've been making an effort to tag fixes with the URL of the
reported bug so you can even find a fix in CVS relatively easily.

The tags go in ChangeLog, the URL in DevNotes.  So, "cvs log" will show
you, indirectly, what patch attempted to fix a reported problem.

cgf

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: [ANNOUNCEMENT] Updated: Cygwin 1.7.15

[Enrico Forestieri]

Corinna Vinschen wrote:
> 
> Hi Cygwin friends and users,
> 
> I just released 1.7.15.  This is a bugfix release.  Only one new feature
> has been added.

This release breaks fifo support in lyx:

$ lyx
LyXComm: Could not open pipe /home/ef/.lyx/lyxpipe.out
Device or resource busy

To reproduce, insert a path for a fifo in the preferences (LyXServer pipe)
and start lyx.

Reverting to 1.7.14 fixes the issue.

-- 
Enrico


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: [ANNOUNCEMENT] Updated: Cygwin 1.7.15

[Christopher Faylor]

On Sat, May 12, 2012 at 11:11:06AM +0000, Enrico Forestieri wrote:
>Corinna Vinschen wrote:
>> 
>> Hi Cygwin friends and users,
>> 
>> I just released 1.7.15.  This is a bugfix release.  Only one new feature
>> has been added.
>
>This release breaks fifo support in lyx:

"This release", indicating that it worked in 1.7.14?  1.7.10?  1.5.9?  B20?

When was this actually working?

cgf

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: [ANNOUNCEMENT] Updated: Cygwin 1.7.15

[Ryan Johnson]

On 12/05/2012 11:46 AM, Christopher Faylor wrote:
> On Sat, May 12, 2012 at 11:11:06AM +0000, Enrico Forestieri wrote:
>> Corinna Vinschen wrote:
>>> Hi Cygwin friends and users,
>>>
>>> I just released 1.7.15.  This is a bugfix release.  Only one new feature
>>> has been added.
>> This release breaks fifo support in lyx:
> "This release", indicating that it worked in 1.7.14?  1.7.10?  1.5.9?  B20?
>
> When was this actually working?

Quoting from his original post: "Reverting to 1.7.14 fixes the issue."

Ryan

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: [ANNOUNCEMENT] Updated: Cygwin 1.7.15

[Christopher Faylor]

On Sat, May 12, 2012 at 11:50:51AM -0600, Ryan Johnson wrote:
>On 12/05/2012 11:46 AM, Christopher Faylor wrote:
>> On Sat, May 12, 2012 at 11:11:06AM +0000, Enrico Forestieri wrote:
>>> Corinna Vinschen wrote:
>>>> Hi Cygwin friends and users,
>>>>
>>>> I just released 1.7.15.  This is a bugfix release.  Only one new feature
>>>> has been added.
>>> This release breaks fifo support in lyx:
>> "This release", indicating that it worked in 1.7.14?  1.7.10?  1.5.9?  B20?
>>
>> When was this actually working?
>
>Quoting from his original post: "Reverting to 1.7.14 fixes the issue."

Sorry about that.  Poor reading skills.

cgf

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: [ANNOUNCEMENT] Updated: Cygwin 1.7.15

[Christopher Faylor]

On Sat, May 12, 2012 at 02:30:27PM -0400, Christopher Faylor wrote:
>On Sat, May 12, 2012 at 11:50:51AM -0600, Ryan Johnson wrote:
>>On 12/05/2012 11:46 AM, Christopher Faylor wrote:
>>> On Sat, May 12, 2012 at 11:11:06AM +0000, Enrico Forestieri wrote:
>>>> Corinna Vinschen wrote:
>>>>> Hi Cygwin friends and users,
>>>>>
>>>>> I just released 1.7.15.  This is a bugfix release.  Only one new feature
>>>>> has been added.
>>>> This release breaks fifo support in lyx:
>>> "This release", indicating that it worked in 1.7.14?  1.7.10?  1.5.9?  B20?
>>>
>>> When was this actually working?
>>
>>Quoting from his original post: "Reverting to 1.7.14 fixes the issue."
>
>Sorry about that.  Poor reading skills.

Should be fixed in the next snapshot.

cgf

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: [ANNOUNCEMENT] Updated: Cygwin 1.7.15

[Enrico Forestieri]

Christopher Faylor wrote:
> 
> Should be fixed in the next snapshot.

Confirmed. Thanks.

-- 
Enrico


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

RE: [ANNOUNCEMENT] Updated: Cygwin 1.7.15

[James Johnston]

> - Add CYGWIN=pipe_byte option to force opening of pipes in byte mode
>   rather than message mode.

I can confirm that setting this fixes the test cases I was having problems with.  Thanks! :)

A suggestion: maybe modify the documentation to state why one would set this?  Current documentation has no clues for why this new pipe_byte option exists, and what problems it might solve.  For example, on http://cygwin.com/cygwin-ug-net/using-cygwinenv.html maybe adding something like:

"By default, Cygwin uses message mode pipes, which more closely emulates UNIX pipe behavior.  Byte mode is required when redirecting standard input for non-Cygwin programs that are not compatible with message mode pipes.  For example, Visual C++ runtime libraries and the .NET Framework are not compatible with message mode pipes."

Maybe add something in the FAQ too, although I'm not sure if this is a frequently asked question yet that is worthy of addition!  I would imagine it could be, given that other people use non-Cygwin programs from Cygwin and probably most of these are affected due to usage of Microsoft runtimes.  I know the FAQ is one of the places I look when troubleshooting.  I don't know if this is worthy to go in there, but perhaps an entry might look like:

"Q:  Why do some programs fail to fully process redirected standard input?

A:  By default, Cygwin uses message mode pipes when redirecting standard file handles, because this more closely emulates UNIX pipes.  Non-Cygwin programs sometimes use runtimes that are not compatible with message mode pipes, so they break under some conditions.  Example runtimes that break include Visual C++ runtime libraries and the .NET Framework.  To work around this issue, set the CYGWIN environment variable option 'pipe_byte'.

An example of a condition that breaks these runtimes is a null write.  For example, if a write of zero bytes is written to a message mode pipe, the receiving program will read zero bytes.  Many runtimes incorrectly assume this is end-of-file, and they no longer correctly read standard input as a result.  Byte mode pipes do not pass through these zero byte writes."

The one thing missing from all this discussion is why you'd want message mode pipes, other than that it more closely emulates UNIX.  For example, are there some packages that break when presented with byte mode pipes?  It could be useful to add some examples of negative real-world consequences to using byte mode pipes.


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple