Dear list,
Recently we are investigating a Wine (Wine Staging) bug encountered by
Cygwin/MSYS2, which also suggest a potential bug in Cygwin.
When running xz on Cygwin/MSYS2 on Wine to decompress data and write
to a pipe, we found data corruption in the final result. This is
reported as Wine Stag
Hi Qian,
On Aug 15 19:11, Qian Hong wrote:
> Dear list,
>
> Recently we are investigating a Wine (Wine Staging) bug encountered by
> Cygwin/MSYS2, which also suggest a potential bug in Cygwin.
> [...]
thanks for the detailed report and your efforts to reproduce the issue.
As discussed on IRC, I'
Hi Cygwin friends and users,
I released a new TEST version of Cygwin. The version number is 2.2.1-0.1.
This test release needs some good old-fashioned testing. 2.2.1 will be
a bugfix release only:
- Revert the follo
On Aug 14 22:20, Corinna Vinschen wrote:
> On Aug 14 17:48, Corinna Vinschen wrote:
> > On Aug 14 06:49, mku wrote:
> > > I hope, not to follow a red herring again, but found some interesting.
> > >
> > > I did a fresh cygwin installation again but made an error not to copy my
> > > old
> > > .ba
works
now.
$ sha1sum cygwin1-20150815.dll
929cd14b16bad6e00f4f51f61b9105756cfab8f6 cygwin1-20150815.dll
$ file cygwin1-20150815.dll
cygwin1-20150815.dll: PE32 executable (DLL) (console) Intel 80386
(stripped to external PDB), for MS Windows
Will update if there is anything interesting.
--
Rega
Hi Achim:
Regarding run 1.3.3-1, if the command
C:\cygwin64\bin\run.exe --quote /usr/bin/bash.exe -l -c "cd; /usr/bin/startxwin"
is issued from the Windows command shell cmd, then C:\cygwin64\run.exe.stackdump is either not generated or not reproducibly generated (it happened just once in a lon
Corinna Vinschen writes:
> Btw., can you please also check /proc/cpuinfo?
The output is correct now for a SandyBridge dual-core CPU with
logical processors (aka HT) and an IvyBridge dual-core CPU w/o HT.
I've also tried to find out why the L3 cache is not reported for AMD in
cpuinfo. It seems th
Jaakov Jaakov writes:
> Regarding run 1.3.3-1,
Is there any reason why you're still bothering with 1.3.3 and not trying 1.3.4?
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Samples for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#Blofe
On 14/08/2015 15:45, Corinna Vinschen wrote:
Marco, please see below in terms of L3 cache info. Thanks,
[cut]
Btw., can you please also check /proc/cpuinfo?
As discussed, Cygwin's emulation fell short on L3 cache info. I now
added code to fetch L3 cache info as well as correct processor to
On 15/08/2015 17:25, Achim Gratz wrote:
Jaakov Jaakov writes:
Regarding run 1.3.3-1,
Is there any reason why you're still bothering with 1.3.3 and not trying 1.3.4?
Regards,
Achim.
May be as 1.3.4 is test and 1.3.3 is current ?
Regards
Marco
--
Problem reports: http://cygwin.com
Jaakov Jaakov writes:
> Regarding run 1.3.3-1,
Is there any reason why you're still bothering with 1.3.3 and not trying 1.3.4?
Hi Achim and Jon:
Several minites ago I've tried run 1.3.4-1. (Previously, I expected getting and
using a test version to be much harder than it actually turned out
On Aug 15 17:11, Achim Gratz wrote:
> Corinna Vinschen writes:
> > Btw., can you please also check /proc/cpuinfo?
>
> The output is correct now for a SandyBridge dual-core CPU with
> logical processors (aka HT) and an IvyBridge dual-core CPU w/o HT.
Thanks!
> I've also tried to find out why the
On Aug 15 17:41, Marco Atzeri wrote:
> On 14/08/2015 15:45, Corinna Vinschen wrote:
> >Marco, please see below in terms of L3 cache info. Thanks,
> >
> [cut]
> >
> >Btw., can you please also check /proc/cpuinfo?
> >
> >As discussed, Cygwin's emulation fell short on L3 cache info. I now
> >added c
Corinna Vinschen writes:
>> I've also tried to find out why the L3 cache is not reported for AMD in
>> cpuinfo. It seems the reason is that it is logically part of the
>> northbridge system, even if it is on-die and gets reported via CPUID.
>
> Ok, interesting. Still strange, isn't it?
In any ca
Jaakov Jaakov writes:
> Several minites ago I've tried run 1.3.4-1. (Previously, I expected
> getting and using a test version to be much harder than it actually
> turned out to be.)
OK, that explains it.
> And, voilà, starting XWin from the shortcut
> succeeded. Also starting from mintty and cmd
> On Aug 15, 2015, at 7:52 AM, Achim Gratz wrote:
>
> [Cygwin Perl maintainer here]
>
> Ivan Pozdeev writes:
>> Currently, g++ is specified in hints/cygwin.sh
>> It is quite a weighty install - approaches 100M with dependencies -
>> and since it isn't really needed (see below), requiring it is
16 matches
Mail list logo
