From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.6.0-0.2
Date: Wed, 27 Jul 2016 08:04:00 -0000 [thread overview]
Message-ID: <20160727080356.GB18002@calimero.vinschen.de> (raw)
In-Reply-To: <75F51A2B-FD08-4E6F-8183-07855E6ADD31@Denis-Excoffier.org>
[-- Attachment #1: Type: text/plain, Size: 1160 bytes --]
On Jul 26 22:48, Denis Excoffier wrote:
>
> > On 2016-07-26 16:00, Corinna Vinschen wrote:
> >
> > Hi Cygwin developers and maintainers,
> > Hi everyone else,
> >
> >
> > I uploaded a new Cygwin test release 2.6.0-0.2.
> >
> > Supposed to fix the problems reported in
> > https://cygwin.com/ml/cygwin/2016-07/msg00274.html and followups.
> >
> Hello,
>
> Is this test release expected to work on 32 bits?
>
> I have a CYGWIN_NT-6.1-WOW (W7 + 32bits) and my .bat file (that contains
> ("bash --long -i") breefly opens but immediately closes with
> no text output. Permissions on the cygwin1.dll file are correct.
>
> 2.6.0-0.1 does the same. However, 2.5.2-1 is ok, and
> snapshots dated 20160714 and 20160719 were ok also.
>
> I desactivated my .profile, in order that LC_CTYPE=fr_FR@euro
> does not enter into the picture, but same result.
>
> I also recompiled from the sources, no error, but same result.
WFFM on W10 WOW64. Did you try to git bisect?
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-07-27 8:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-26 14:02 Corinna Vinschen
2016-07-26 15:31 ` Ken Brown
2016-07-26 17:09 ` Jim Reisert AD1C
2016-07-26 17:38 ` Corinna Vinschen
2016-07-26 19:30 ` Ken Brown
2016-07-26 21:37 ` Corinna Vinschen
2016-07-26 20:48 ` Denis Excoffier
2016-07-27 8:04 ` Corinna Vinschen [this message]
2016-07-27 11:56 ` Corinna Vinschen
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=20160727080356.GB18002@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@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).