A new release of wget, 1.19.1-2, will be available soon for download
from your favorite mirror, leaving 1.19.1-1 as previous.
NEWS:
=
This is a rebuild, in order to fix CVE-2017-6508 as well as build
against libidn2. See also the package documentation in
/usr/share/doc/wget/.
DESCRIPTION:
==
On 6/29/2017 7:16 AM, JonY wrote:
gcc-6.3.0-2 has been uploaded for Cygwin. It is marked as a test version.
JonY,
I assume you want some feedback on this.
I've been testing gcc-6.3.0-2 with binutils-2.28-3, on both x86 and
x86_64, by rebuilding several of my packages. So far I've built
tex
[revisiting this thread]
On 03/29/2017 08:45 PM, Eric Blake wrote:
> On 03/29/2017 08:30 PM, Andrew Schulman wrote:
>> Recently, I guess since wget was upgraded to 1.19, whenever I run wget I get
>> a
>> bonus message on the console:
>>
>> Redirecting output to ‘wget-log’.
>>
>> And sure enough
On 04/14/2017 11:33 PM, Steven Penny wrote:
> On Thu, 13 Apr 2017 13:48:04, Eric Blake wrote:
>> Is it still a problem with pselect, where rebuilding with the same
>> configuration as 7.0.1-2 fixes things?
I've got some time today to look at building readline, but for the life
of me, I can't figu
On 07/27/2017 12:08 PM, Eric Blake wrote:
> So I'm back to cmd to try and debug things. Next, I tried:
>
> c:\cygwin\bin> .\dash
>
>
> and again got Ω; pressing complains that ./dash: 1: Ω: not found
To double check things, I started .\dash, typed 'echo $$', then in a
second terminal, typed
On Thu, 27 Jul 2017 12:08:53, Eric Blake wrote:
I've got some time today to look at building readline, but for the life
of me, I can't figure out what I'm supposed to be debugging. You have
so many emails saying "see this earlier URL" that I am lost in what you
are saying is wrong or how to repr
On 2017-07-28 02:49, Ken Brown wrote:
On 6/29/2017 7:16 AM, JonY wrote:
gcc-6.3.0-2 has been uploaded for Cygwin. It is marked as a test version.
JonY,
I assume you want some feedback on this.
I've been testing gcc-6.3.0-2 with binutils-2.28-3, on both x86 and
x86_64, by rebuilding several
On 27/07/2017 23:04, Ross Smith wrote:
On 2017-07-28 02:49, Ken Brown wrote:
On 6/29/2017 7:16 AM, JonY wrote:
gcc-6.3.0-2 has been uploaded for Cygwin. It is marked as a test
version.
JonY,
I assume you want some feedback on this.
I've been testing gcc-6.3.0-2 with binutils-2.28-3, on both
On 07/27/2017 01:56 PM, Steven Penny wrote:
> On Thu, 27 Jul 2017 12:08:53, Eric Blake wrote:
>> I've got some time today to look at building readline, but for the life
>> of me, I can't figure out what I'm supposed to be debugging. You have
>> so many emails saying "see this earlier URL" that I a
On 2017-07-28 09:19, Marco Atzeri wrote:
On 27/07/2017 23:04, Ross Smith wrote:
gcc 6.3 works fine for me unless I use threads. Any C++ program that
uses std::thread (and worked with the previous gcc) will fail. Simple
example:
#include
#include
void payload() {
std::cout
On 7/27/2017 5:39 PM, Ross Smith wrote:
On 2017-07-28 09:19, Marco Atzeri wrote:
On 27/07/2017 23:04, Ross Smith wrote:
gcc 6.3 works fine for me unless I use threads. Any C++ program that
uses std::thread (and worked with the previous gcc) will fail. Simple
example:
#include
#includ
On 2017-07-28 09:45, Ken Brown wrote:
On 7/27/2017 5:39 PM, Ross Smith wrote:
On 2017-07-28 09:19, Marco Atzeri wrote:
On 27/07/2017 23:04, Ross Smith wrote:
gcc 6.3 works fine for me unless I use threads. Any C++ program that
uses std::thread (and worked with the previous gcc) will fail. Sim
On Thu, 27 Jul 2017 16:37:45, Eric Blake wrote:
I still don't know your environment (it's really hard to reproduce
issues if I don't know the steps to reproduce them). This looks like a
bash prompt, but are you running bash inside mintty, or directly in a
cmd window?
1. Clean Cygwin install
2
13 matches
Mail list logo
