On Jun 21, 2016, at 5:12 PM, Andrey Repin wrote:
>
> Greetings, Warren Young!
>
>> I used 64k and 64M (capitalization is important to dd),
>
> You aren't confusing DD with some other tool?
Try testing with “M”, not “k”.
Technically speaking, if it’s going to be picky
>>I've reproduced this SaVi-can't-talk-with-Geomview-on-64-bit-cygwin problem
>>on multiple installs
> How, exactly? Give me the step-by-step.
Step by step instructions to build Geomview and SaVi are on:
http://sat-net.com/L.Wood/software/SaVi/building-under-Windows/
launch with
geomview
Greetings, Warren Young!
> I used 64k and 64M (capitalization is important to dd),
You aren't confusing DD with some other tool?
$ dd if=/dev/urandom of=/dev/null bs=64K count=1
1+0 records in
1+0 records out
65536 bytes (66 kB, 64 KiB) copied, 0,0183668 s, 3,6 MB/s
$ dd if=/dev/urandom
On Jun 21, 2016, at 4:54 PM,
wrote:
>
> Three years ago, 64-bit OpenGL not yet working at all was simply motivation
> to see how the then-new 64-bit Geomview fleshed out.
Why mention OpenGL at all, then?
This is part of reducing the problem to
Version 2.2.0-1 of expat has been uploaded.
Expat is a stream-based XML parsing library used by many programs.
This release tracks an upstream release, which is mainly a bugfix and security
rollup release. All users of Expat 2.x should upgrade to it.
*** CYGWIN-ANNOUNCE
Version 2.2.0-1 of expat has been uploaded.
Expat is a stream-based XML parsing library used by many programs.
This release tracks an upstream release, which is mainly a bugfix and security
rollup release. All users of Expat 2.x should upgrade to it.
*** CYGWIN-ANNOUNCE
Warren,
this piping problem on 64-bit Cygwin between Geomview and its modules (of which
SaVi is the most used example) is entirely unrelated to OpenGL, and exists when
Geomview is compiled without OpenGL.
Three years ago, 64-bit OpenGL not yet working at all was simply motivation to
see how
On Jun 21, 2016, at 4:40 PM, Warren Young wrote:
>
> On Jun 21, 2016, at 3:57 PM, Warren Young wrote:
>>
>> Here’s what a simple test case looks like:
>>
>> $ dd if=/dev/urandom bs=4k count=4m |
>> gpg -c --force-mdc |
>> gpg -d > /dev/null
>
> I
On Jun 21, 2016, at 3:57 PM, Warren Young wrote:
>
> Here’s what a simple test case looks like:
>
> $ dd if=/dev/urandom bs=4k count=4m |
>gpg -c --force-mdc |
>gpg -d > /dev/null
I seem to have stumbled upon the actual STC. Just increase those values,
launch two
The attached zip file contains the results when I create a directory called
cmaketest64,
put the two files from my previous post (CMakeLists.txt and tutorial.cxx) in
it, and type "cmake ."
I had to change the file extension from .zip to .z__ and remove two .exe files
to get past the spam
Tony Kelman writes:
> I'm at a conference this week so really busy, but it sounds like I may
> need to update cmake to the latest version (which is overdue anyway)
> if something in the latest gcc is unhappy. Can you provide full
> reproduction steps, a source repo or tarball to download? Also
Hans-Bernhard Bröker writes:
> One possibly important difference is that you keep your source tree in the
> Windows user profile directory; I never subscribed to that idea.
I've put the source tree in a number of places with the same result. I'll try
again at any location you suggest.
> What
On Jun 20, 2016, at 10:53 PM, lloyd.w...@yahoo.co.uk wrote:
>
> Yes, it's the same piping problem of three years ago.
…where you were asked to provide a simple test case for the problem, instead of
“compile admittedly difficult-to-build package Geomview and use it against one
of the most
Am 21.06.2016 um 03:43 schrieb Frank Brill:
I am having trouble building an open source project using cmake under
Cygwin64 with the latest tools (setup-x86_64.exe version 2.874).
Well, FWIW, with the CMake-based projects I've been building here
(Windows10 64-bit, Cygwin 64-bit, packages gcc
Marco Atzeri writes:
> what is the content of
> cmake_link_script
> CMakeFiles/cmTC_5d15a.dir/link.txt
None of these files exists after the failed cmake exits. The directory
./CMakeFiles/CMakeTmp is created, but it's empty. The entire directory
structure that is remaining after executing
On 21/06/2016 13:03, Corinna Vinschen wrote:
On Jun 20 16:28, Jon Turney wrote:
[...]
* 'curr', 'prev' and 'test' don't make sense on a per-version basis. So I
suggest a separate file for these version overrides (versions.hint?)
Ideally we wouldn't need something like "prev" at all since
Eric Blake writes:
> Except when upstream version numbers go backwards. We'd have to adopt
> something like Fedora's "epoch" numbering if we want our version numbers
> to always be increasing (by bumping the epoch any time upstream versions
> go backwards).
Oh please not. I've looked into this
The following packages have been updated in the Cygwin distribution:
*** xorg-server-*1.18.3-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.18.2-1:
* In multiwindow mode, enable
The following packages have been updated in the Cygwin distribution:
*** xorg-server-*1.18.3-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.18.2-1:
* In multiwindow mode, enable
On 21/06/2016 16:28, Corinna Vinschen wrote:
On Jun 21 15:49, Marco Atzeri wrote:
On 21/06/2016 14:03, Corinna Vinschen wrote:
On Jun 20 16:28, Jon Turney wrote:
Ideally we wouldn't need something like "prev" at all since the version
number itself is sufficient to specify what's curr
On Jun 21 15:49, Marco Atzeri wrote:
>
> On 21/06/2016 14:03, Corinna Vinschen wrote:
> > On Jun 20 16:28, Jon Turney wrote:
> > >
> > > Currently, the setup.hint file is shared between all versions.
> > >
> > > This means that manual intervention (by the package maintainer, or on
> > >
On Jun 21 08:08, Eric Blake wrote:
> On 06/21/2016 06:03 AM, Corinna Vinschen wrote:
>
> >> * 'curr', 'prev' and 'test' don't make sense on a per-version basis. So I
> >> suggest a separate file for these version overrides (versions.hint?)
> >
> > Ideally we wouldn't need something like "prev"
On 06/21/2016 06:03 AM, Corinna Vinschen wrote:
>> * 'curr', 'prev' and 'test' don't make sense on a per-version basis. So I
>> suggest a separate file for these version overrides (versions.hint?)
>
> Ideally we wouldn't need something like "prev" at all since the version
> number itself is
Oh wow, I didn't expect such quick turnaround. Thanks Corinna!
I've downloaded the snapshot and can confirm that it no longer hangs.
Initially the bug manifested itself while I was using my django server
and uploading files. However, there was no lead since there were no errors
and the multi
On 21/06/2016 03:43, Frank Brill wrote:
I am having trouble building an open source project using cmake under Cygwin64
with the latest tools (setup-x86_64.exe version 2.874).
I was able to successfully build the project with 32-bit Cygwin with the latest
tools: gcc 5.4.0, gnu make 4.2.1, and
On 21/06/2016 14:03, Corinna Vinschen wrote:
On Jun 20 16:28, Jon Turney wrote:
Currently, the setup.hint file is shared between all versions.
This means that manual intervention (by the package maintainer, or on
sourceware) is needed when versions have different dependencies.
To automate
On Jun 21 06:04, RG wrote:
> Hello,
>
> I have encountered unexpected behavior when using flock.
> It will block forever, but to my understanding it should not.
> I've attached a simple program that would trigger the behavior.
>
> Regards,
> Alex
> #include
> #include
> #include
>
> FILE
Hi Cygwin friends and users,
I released a new Cygwin TEST version 2.5.2-0.2.
2.5.2 will be a plain bugfix release, plus a few assorted improvements
under the hood. Please test. Only regressions compared to 2.5.1
are currently on the radar.
Hi Cygwin friends and users,
I released a new Cygwin TEST version 2.5.2-0.2.
2.5.2 will be a plain bugfix release, plus a few assorted improvements
under the hood. Please test. Only regressions compared to 2.5.1
are currently on the radar.
Frank Brill samsung.com> writes:
>
> I am having trouble building an open source project using cmake under
Cygwin64 with the latest tools
> (setup-x86_64.exe version 2.874).
>
> I was able to successfully build the project with 32-bit Cygwin with the
latest tools: gcc 5.4.0, gnu make
>
On Jun 21 09:01, Thomas Wolff wrote:
> I had recently reported that an old network installation problem, that had
> been resolved meanwhile, reappeared:
> https://cygwin.com/ml/cygwin-apps/2015-12/msg00012.html
>
> As an additional observation, on the same machine, there is also a virtual
>
On Jun 20 16:28, Jon Turney wrote:
>
> Currently, the setup.hint file is shared between all versions.
>
> This means that manual intervention (by the package maintainer, or on
> sourceware) is needed when versions have different dependencies.
>
> To automate this problem out of existence, I
https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=94e3a561d053ca1b00f16d81d4ade2884ea45b54
commit 94e3a561d053ca1b00f16d81d4ade2884ea45b54
Author: Corinna Vinschen
Date: Tue Jun 21 13:43:53 2016 +0200
Add release message for commit 2c83227
https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=2c832271127f2ae7eea4245dc940d8a5c1fe7498
commit 2c832271127f2ae7eea4245dc940d8a5c1fe7498
Author: Corinna Vinschen
Date: Tue Jun 21 13:39:35 2016 +0200
Drop useless calls to path_conv.isgood_inode
https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=36d4eb12b5f23093ae1285d0725f4930235a07e5
commit 36d4eb12b5f23093ae1285d0725f4930235a07e5
Author: Corinna Vinschen
Date: Tue Jun 21 13:28:12 2016 +0200
Use new path_conv_handle functions to access file info
https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=4965cdc9ad2753f7aa91711e2862d7e350168bef
commit 4965cdc9ad2753f7aa91711e2862d7e350168bef
Author: Corinna Vinschen
Date: Tue Jun 21 13:39:04 2016 +0200
Use correct file info (especially inode number) for newly
https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=f91865c8cf85c4c4309c64ded42c847a64872b1e
commit f91865c8cf85c4c4309c64ded42c847a64872b1e
Author: Corinna Vinschen
Date: Tue Jun 21 13:24:41 2016 +0200
Improve encapsulation of FS type behind path_conv cover
On 21/06/2016 06:20, Gavin King wrote:
Hello
My apologies if this is a bit verbose, or if the terminology is a bit
wrong; I know enough to get myself into trouble but not enough to
communicate problems well.
Hi Gavin,
nice to hear you.
After updating cygwin, a working script failed,
Sent from my iPhone
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
I had recently reported that an old network installation problem, that
had been resolved meanwhile, reappeared:
https://cygwin.com/ml/cygwin-apps/2015-12/msg00012.html
As an additional observation, on the same machine, there is also a
virtual machine running Windows XP. From that, I can use
40 matches
Mail list logo