On Nov 3, 2017 9:36 PM, "Corinna Vinschen" wrote:
Hi Erik,
why didn't you send this to cygwin-patches? Not much of a problem,
just wondering...
Will follow up more later, but just to clarify on this a bit I thought the
issue was just interesting, and that the question(s) of the upper limit
Am 03.11.2017 um 21:03 schrieb cyg Simple:
On 11/3/2017 3:23 PM, Thomas Wolff wrote:
Am 03.11.2017 um 16:34 schrieb cyg Simple:
On 11/2/2017 3:55 PM, Thomas Wolff wrote:
Am 02.11.2017 um 14:38 schrieb cyg Simple:
On 11/2/2017 2:47 AM, Thomas Wolff wrote:
Thanks, Brian, for the links and the
Hi Erik,
why didn't you send this to cygwin-patches? Not much of a problem,
just wondering...
On Nov 3 15:39, Erik Bray wrote:
> [...]
> After some playing around I found that I could make up to exactly 1365
> sockets and use them without error. At 1366 I get the error. A very
> strange and
Yaakov Selkowitz writes:
>>> If you've confirmed that this is the exact version gcc6 needs, then yes.
>>> Alternatively, Jon could take over the package to sync with any gcc
>>> updates, since I believe gcc is the only user anyway.
>
> Ping?
Are you pinging me or JonY? If you meant me, just
Jon Turney writes:
> The current default package retention policy is: the curr and test
> versions are always kept, also keep the 3 highest versions (this is
> slightly more generous than upset's historical behaviour, as it keeps
> 3 versions even if test isn't being used)
Is there any pressing
On 11/3/2017 3:23 PM, Thomas Wolff wrote:
> Am 03.11.2017 um 16:34 schrieb cyg Simple:
>> On 11/2/2017 3:55 PM, Thomas Wolff wrote:
>>> Am 02.11.2017 um 14:38 schrieb cyg Simple:
On 11/2/2017 2:47 AM, Thomas Wolff wrote:
> Thanks, Brian, for the links and the sample code which will make
I am experiencing a similar situation on a recently reimaged Windows 10
computer in a large corporate environment, namely:
* Either typing "exit" or clicking the Windows close [X] button from a
Cygwin bash terminal (mintty under the hood) results in the process hanging
with it either eventually
Am 03.11.2017 um 16:34 schrieb cyg Simple:
On 11/2/2017 3:55 PM, Thomas Wolff wrote:
Am 02.11.2017 um 14:38 schrieb cyg Simple:
On 11/2/2017 2:47 AM, Thomas Wolff wrote:
Thanks, Brian, for the links and the sample code which will make it
easier.
This is about changing the icon, to get that
The following packages have been uploaded to the Cygwin distribution:
* s2tc-1.0-2.20151227gitf6ec862
S2TC (Super Simple Texture Compression) is a patent-free texture
compression algorithm designed to be compatible with existing S3TC
decompressors.
This release has been rebuilt with the
The following packages have been uploaded to the Cygwin distribution:
* s2tc-1.0-2.20151227gitf6ec862
S2TC (Super Simple Texture Compression) is a patent-free texture
compression algorithm designed to be compatible with existing S3TC
decompressors.
This release has been rebuilt with the
The following packages have been uploaded to the Cygwin distribution:
* libtxc_dxtn-1.0.1-2
* libtxc_dxtn-devel-1.0.1-2
Software implementation of the S3 Texture Compression algorithm, which
is no longer patent encumbered.
Please note that our latest Mesa builds no longer require this library
The following packages have been uploaded to the Cygwin distribution:
* libtxc_dxtn-1.0.1-2
* libtxc_dxtn-devel-1.0.1-2
Software implementation of the S3 Texture Compression algorithm, which
is no longer patent encumbered.
Please note that our latest Mesa builds no longer require this library
The following packages have been uploaded to the Cygwin distribution:
* tigervnc-1.8.0-2
* tigervnc-server-1.8.0-2
* tigervnc-server-module-1.8.0-2
TigerVNC is a high-performance implementation of VNC, a client/server
application that allows users to launch and interact with graphical
The following packages have been uploaded to the Cygwin distribution:
* tigervnc-1.8.0-2
* tigervnc-server-1.8.0-2
* tigervnc-server-module-1.8.0-2
TigerVNC is a high-performance implementation of VNC, a client/server
application that allows users to launch and interact with graphical
The following packages have been uploaded to the Cygwin distribution:
* dri-drivers-17.2.4-1
* libglapi0-17.2.4-1
* libGL1-17.2.4-1
* libGL-devel-17.2.4-1
* libOSMesa8-17.2.4-1
* libOSMesa-devel-17.2.4-1
* libEGL1-17.2.4-1
* libEGL-devel-17.2.4-1
* libGLESv2_2-17.2.4-1
* libGLESv2-devel-17.2.4-1
The following packages have been uploaded to the Cygwin distribution:
* dri-drivers-17.2.4-1
* libglapi0-17.2.4-1
* libGL1-17.2.4-1
* libGL-devel-17.2.4-1
* libOSMesa8-17.2.4-1
* libOSMesa-devel-17.2.4-1
* libEGL1-17.2.4-1
* libEGL-devel-17.2.4-1
* libGLESv2_2-17.2.4-1
* libGLESv2-devel-17.2.4-1
The following packages have been uploaded to the Cygwin distribution:
* cygport-0.25.0-1
cygport is the standard method for building and maintaining packages for
the Cygwin distribution.
This release adds 'package-test' and 'stage' commands, and cygclasses for
Meson and Ninja build systems,
The following packages have been uploaded to the Cygwin distribution:
* cygport-0.25.0-1
cygport is the standard method for building and maintaining packages for
the Cygwin distribution.
This release adds 'package-test' and 'stage' commands, and cygclasses for
Meson and Ninja build systems,
The following packages have been updated in the Cygwin distribution:
*** xorg-server-*1.19.5-1
These packages contain XWin and the other X.Org X11 servers.
In addition to upstream fixes [1], the following cygwin-specific changes
have been made since 1.19.4-1:
* Fix swapped RaiseVolume and
The following packages have been updated in the Cygwin distribution:
*** xorg-server-*1.19.5-1
These packages contain XWin and the other X.Org X11 servers.
In addition to upstream fixes [1], the following cygwin-specific changes
have been made since 1.19.4-1:
* Fix swapped RaiseVolume and
The following packages have been uploaded to the Cygwin distribution:
* urw-base35-fonts-20170801-2
This package, which used to be called "ghostscript-fonts-std",
contains the 35 fonts in the PostScript Level 2 Core Font Set. These
fonts are used by ghostscript and xpdf.
This is a rebuild of
The following packages have been uploaded to the Cygwin distribution:
* urw-base35-fonts-20170801-2
This package, which used to be called "ghostscript-fonts-std",
contains the 35 fonts in the PostScript Level 2 Core Font Set. These
fonts are used by ghostscript and xpdf.
This is a rebuild of
On 11/3/2017 9:11 AM, Ken Brown wrote:
In the meantime, I have another xpdf problem. After my update of the
ghostscript fonts, I get the following errors when starting xpdf:
Config Error: No display font for 'Courier'
Config Error: No display font for 'Courier-Bold'
Config Error: No display
On Fri, 3 Nov 2017 15:26:27 + Jon Turney
wrote:
JT> On 03/11/2017 14:45, Vadim Zeitlin wrote:
JT> > Our build has started on AppVeyor, a continuous integration provider,
JT> > started failing since a couple of days as a makefile command running a
JT> > Python
On 11/2/2017 3:55 PM, Thomas Wolff wrote:
> Am 02.11.2017 um 14:38 schrieb cyg Simple:
>> On 11/2/2017 2:47 AM, Thomas Wolff wrote:
>>> Thanks, Brian, for the links and the sample code which will make it
>>> easier.
>>> This is about changing the icon, to get that sorted out.
>>> I referred to
On 03/11/2017 14:45, Vadim Zeitlin wrote:
Our build has started on AppVeyor, a continuous integration provider,
started failing since a couple of days as a makefile command running a
Python script started failing with exit code 127 without any more
information. This is a strange situation as I
On Fri, Nov 3, 2017 at 3:45 PM, Vadim Zeitlin wrote:
> Hello,
>
> Our build has started on AppVeyor, a continuous integration provider,
> started failing since a couple of days as a makefile command running a
> Python script started failing with exit code 127 without any more
> information. This
Greetings, Wenjie Wu!
> Hi I got an warning message when perform some cpld download and it suggests
> me to contact you guys. Any ideas?
Same as before: Update your Cygwin.
The problem was resolved ages ago.
> 2 [main] od 1424 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer.
> Please
Hello,
Our build has started on AppVeyor, a continuous integration provider,
started failing since a couple of days as a makefile command running a
Python script started failing with exit code 127 without any more
information. This is a strange situation as I can't reproduce the problem
Hi all,
I found a few bugs in Cygwin w.r.t. creating large numbers of sockets.
For example, Cygwin will gladly let you create up to RLIMIT_NOFILE
sockets (examples in Python, where I found this problem):
>>> import resource
>>> import socket
>>> resource.getrlimit(resource.RLIMIT_NOFILE)
(256,
On 09/10/2017 20:32, Jon Turney wrote:
So, thinking about this change some more, I realize that there is a
another way to do this, which doesn't break backwards compatibility with
setup, by having multiple [prev] and [test] sections.
[1] doesn't say that these section names are unique, and
On 11/3/2017 2:52 AM, Yaakov Selkowitz wrote:
On 2017-10-28 13:00, Ken Brown wrote:
On 10/27/2017 5:00 PM, Yaakov Selkowitz wrote:
---
xpdf.cygport | 4
1 file changed, 4 insertions(+)
After making this change I get the following warning when starting xpdf
in an xterm window:
On Thu, Nov 2, 2017 at 6:10 PM, Corinna Vinschen
wrote:
> On Nov 2 16:45, Erik M. Bray wrote:
>> Also updates the fhandler_*::fadvise implementations to adhere to the same
>> semantics.
>
> Both patches pushed.
Thanks!
On 2017-10-28 13:00, Ken Brown wrote:
> On 10/27/2017 5:00 PM, Yaakov Selkowitz wrote:
>> ---
>> xpdf.cygport | 4
>> 1 file changed, 4 insertions(+)
>
> After making this change I get the following warning when starting xpdf
> in an xterm window:
>
> QStandardPaths: XDG_RUNTIME_DIR not
On 2017-07-13 13:49, Achim Gratz wrote:
>> Yaakov Selkowitz writes:
>>> It looks like GCC 6 would benefit from an update of isl to 0.16.1 (but
>>> NOT newer). This would be an ABI bump of libisl to 15, so existing GCC
>>> 5 builds would not be affected, as long as we aren't planning any more
>>>
35 matches
Mail list logo