On Sun, 20 Aug 2017 18:57:24, Steven Penny wrote:
Question - is mingw64-x86_64-gcc-g++ still coming? I have come C++ projects I
could test it with.
Correcting myself; looks like the Aug 20 update includes C and C++:
http://cygwin.mirror.constant.com/x86_64/release/mingw64-x86_64-gcc
--
Probl
On Sun, 20 Aug 2017 14:16:07, JonY wrote:
The mingw-w64 cross compilers have been updated:
* mingw64-i686-binutils-2.28.1.12c1f20d
* mingw64-i686-gcc-6.3.0-1
* mingw64-x86_64-binutils-2.28.1.12c1f20d
* mingw64-x86_64-gcc-6.3.0-1
These versions should be considered testing quality.
Looks good,
The following packages have been updated in the Cygwin distribution:
* mkvtoolnix-15.0.0-1
* mkvtoolnix-gui-15.0.0-1
MKVToolNix is a set of tools to create, alter and inspect Matroska
files (*.mkv, *.mka).
This is an update to the latest upstream release.
Dave.
--
Problem reports: http:
The following packages have been updated in the Cygwin distribution:
* libebml4-1.3.5-1
* libebml-devel-1.3.5-1
libebml is a library for reading and writing files with the Extensible
Binary Meta Language, a binary pendant to XML.
This is an update to the latest upstream release.
Dave.
--
Prob
can anybody help?
On Mon, Jul 31, 2017 at 11:40 AM, Beau Kissinger wrote:
> Hi there,
> I found my cygwin x86_64 setup suddenly cannot work in win10, but
> x64 version works fine.
>
> It reports:
> Fatal error: Unexpected windows message 13 received too early in
> window initialization.
>
The mingw-w64 cross compilers have been updated:
* mingw64-i686-binutils-2.28.1.12c1f20d
* mingw64-i686-gcc-6.3.0-1
* mingw64-x86_64-binutils-2.28.1.12c1f20d
* mingw64-x86_64-gcc-6.3.0-1
These versions should be considered testing quality.
Note that ADA/GNAT has been disabled in this release.
On Sun, Aug 20, 2017 at 02:18:45PM +0200, Houder wrote:
> On 2017-08-19 10:01, Noah Misch wrote:
> >What words in those chapters prompted your conclusion? I see nothing in
> >20.10 or 20.13 about contextual restrictions on SIG_SETMASK. Posix
> >mentions no such restrictions in its sigprocmask() p
Both testcases confirm that Cygwin _sometimes_ delivers a signal,
although
the signal mask specifies (verified by the test case) it should not.
Hence, your fixes are not relevant to the issue.
However, they also demonstrate that the signal nesting (at least,
self-esting: the same signal being
On Fri, 18 Aug 2017 18:20:40, Corinna Vinschen wrote:
> On Aug 16 23:22, Houder wrote:
[snip]
> > The alternative testcase in fact consists of 2 testcases (2 files):
> >
> > 1. sigprocmask-exclusion4.c
> > 2. sigprocmask-exclusion5.c
> Thanks for the testcases. This is still a pretty tricky pr
On Wed, 16 Aug 2017 23:22:31, Houder wrote:
>
> Hi,
>
> Please read this post first:
>
> https://cygwin.com/ml/cygwin/2017-08/msg00048.html
> ( Signal delivered while blocked -- by Noah Misch, August 4th 2017 )
>
> This post is not intended to "hijack" the post by Noah Misch; this pos
On 2017-08-19 10:01, Noah Misch wrote:
What words in those chapters prompted your conclusion? I see nothing
in 20.10
or 20.13 about contextual restrictions on SIG_SETMASK. Posix mentions
no such
restrictions in its sigprocmask() page, and Posix does say:
Noah,
My apologies! My command over
11 matches
Mail list logo