Re: [ANNOUNCEMENT] New package: mingw64-x86_64-gcc-4.5.1-1

On 14 September 2010 03:13, JonY wrote: > Version 4.5.1-1 of "mingw64-x86_64-gcc" has been uploaded. > > mingw64-x86_64-gcc contains GCC sources used by the 64bit target toolchain. > See mingw64-x86_64-gcc-core, mingw64-x86_64-gcc-objc, > mingw64-x86_64-gcc-ada, mingw64-x86_64-gcc-g++ and > mingw64

[ANNOUNCEMENT] New package: mingw64-x86_64-pthreads-20100619-1

Version 20100619-1 of "mingw64-x86_64-pthreads" has been uploaded. mingw64-x86_64-pthreads provides 64bit pthreads support. It is used by GCC for OpenMP. *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, look at the "List

[ANNOUNCEMENT] New package: mingw64-x86_64-headers-1.0b_svn3433-1

Version 1.0b_svn3433-1 of "mingw64-x86_64-headers" has been uploaded. mingw64-x86_64-headers contains headers for Windows development. This package is specifically for the 64bit target toolchain. *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin

[ANNOUNCEMENT] New package: mingw64-x86_64-runtime-20100809-1

Version 20100809-1 of "mingw64-x86_64-runtime" has been uploaded. mingw64-x86_64-runtime provides library to interface with Windows. This package is specifically for the 64bit target toolchain. *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-a

[ANNOUNCEMENT] New package: mingw64-x86_64-binutils-2.20.51-1

Version 2.20.51-1 of "mingw64-x86_64-binutils" has been uploaded. mingw64-x86_64-binutils provides binutils support for the 64bit target toolchain. *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, look at the "List-Unsub

[ANNOUNCEMENT] New package: mingw64-x86_64-gcc-4.5.1-1

Version 4.5.1-1 of "mingw64-x86_64-gcc" has been uploaded. mingw64-x86_64-gcc contains GCC sources used by the 64bit target toolchain. See mingw64-x86_64-gcc-core, mingw64-x86_64-gcc-objc, mingw64-x86_64-gcc-ada, mingw64-x86_64-gcc-g++ and mingw64-x86_64-gcc-fortran for binaries.

[ANNOUNCEMENT] New package: mingw64-x86_64 cross toolchain

The mingw64-x86_64 cross toolchain set has been uploaded to the Cygwin mirrors. It is used to build 64bit Windows applications and programs. As with all software releases, it may contain bugs, please report bugs to . *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsub

Deletion race in NtSetFileInformation ? (Directory not empty error in rm -r -f)

I have a Makefile which performs "rm -f -r" as part of a clean target. On Win7 with 1.7.5-1 this can fail with: rm -f -r win32 rm: cannot remove directory `win32': Directory not empty I tried 1.7.7-1 but the problem still seems to be there. Doing a little digging, I find that /bin/rm calls unl

RE: 1.7.5: Occasional failure of CreatePipe or signal handing due to thread-unsafe code in cwdstuff::set

On Sep 13, John Carey wrote: > It's not one of those, or even the subroutine that those share. I don't know > how they relate. ... (incorrect quotation omitted) My apologies for using the wrong quotation format. Sorry! -- John -- Problem reports: http://cygwin.com/problems.html FAQ:

Re: Cygwin instabilities

> > Can't really parse that, especially given that I'm a developer and you're > obviously not. > lol Al -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.

RE: 1.7.5: Occasional failure of CreatePipe or signal handing due to thread-unsafe code in cwdstuff::set

On Sep 13 12:47, John Carey wrote: > On Sep 11 03:30, Corinna Vinschen: > > Can't we find Cwd by scanning the .data segment of ntdll.h for the > > address we inferred from the Params.CurrentDirectoryName.Buffer value? > > Nice; that might work. But there would need to be some kind of rule > to pi

Re: Cygwin instabilities

On Mon, Sep 13, 2010 at 09:48:49PM +0200, Al wrote: >> It depends on what is meant by "become". ?If it means will there be a >> concerted >> effort to "harden" Cygwin for a server then the answer is likely "not unless >> someone pays for it." >> >> That points back to paying Red Hat for support. >

Re: Cygwin instabilities

> It depends on what is meant by "become".  If it means will there be a > concerted > effort to "harden" Cygwin for a server then the answer is likely "not unless > someone pays for it." > > That points back to paying Red Hat for support. I think you use the term support in the wrong field. It is

RE: 1.7.5: Occasional failure of CreatePipe or signal handing due to thread-unsafe code in cwdstuff::set

On Sep 11 03:30, Corinna Vinschen: > On Sep 11 00:12, John Carey wrote: > > The proof-of-concept code follows (and is also attached). It includes > > an analysis of what is going on--to the extent that I know what is going > > on, of course. Please let me know what you think. > > First of all, I

Re: Cygwin instabilities

On 13/09/2010 20:23, Christopher Faylor wrote: > You've included a patch here but, FYI, I have no idea why. FTR only. It might be useful to others following the list. cheers, DaveK -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/fa

Re: Cygwin instabilities

On 9/13/2010 12:34 PM, Dave Korn wrote: Even when I submit make check-c make check-fortran and make check-c++ in separate windows, occasionally an instance of expect will hang and fail to time out, so has to be killed to complete the check. More often than not, it's possible to complete the w

Re: Cygwin instabilities

On Mon, Sep 13, 2010 at 08:34:42PM +0100, Dave Korn wrote: >On 13/09/2010 17:35, Christopher Faylor wrote: > >> You seem to be approaching this problem as if people will say "Ah! >> Stability issues! Right. Well, ok, here's what you need to know." >> >> If we knew of stability issues they would b

Re: Cygwin instabilities

On Mon, Sep 13, 2010 at 03:52:55PM -0300, Ramiro Polla wrote: >On Mon, Sep 13, 2010 at 10:19 AM, Al wrote: >> Others report that they don't use Cygwin because of instablilities, >> especially in the server context. > >I've also been having "instabilities" in my "server context" (Windows >Server 20

Re: Cygwin instabilities

On 13/09/2010 17:35, Christopher Faylor wrote: > You seem to be approaching this problem as if people will say "Ah! > Stability issues! Right. Well, ok, here's what you need to know." > > If we knew of stability issues they would be fixed. Well, I know of one, but haven't had time to fix it y

Re: Cygwin instabilities

On Mon, Sep 13, 2010 at 10:19 AM, Al wrote: > Others report that they don't use Cygwin because of instablilities, > especially in the server context. I've also been having "instabilities" in my "server context" (Windows Server 2008 R2), but I have a few more concrete details: I had 1.7.5 install

Re: Cygwin instabilities

> You seem to be approaching this problem as if people will say "Ah! > Stability issues! Right.  Well, ok, here's what you need to know." > It's not me thinking in the bug -> solution pattern here. I don't ask for a solution. > > If you think that asking a group of strangers for help with a nebul

Re: Cygwin instabilities

On Mon, Sep 13, 2010 at 05:57:08PM +0200, Al wrote: >>These two things are related. Remember that Cygwin is an open source > >Sure it is related, but that doesn't answer my question. > >>Who would keep counters of stable or instable setups? These number are >>exceptionally hard to come by. Even

Re: Cygwin instabilities

Al was heard to say: No that is not the way to go. I think there are people which run Cygwin on more than 1 machine, so they have a personal estimation and experience. Yes, and this is where the Cygwin archives come in handy. If there are users running Cygwin on lots of machines, they are

Re: Cygwin instabilities

On 9/13/2010 11:57 AM, Al wrote: These two things are related. Remember that Cygwin is an open source Sure it is related, but that doesn't answer my question. Who would keep counters of stable or instable setups? These number are exceptionally hard to come by. Even if this list is now flooded

Re: Cygwin instabilities

> These two things are related. Remember that Cygwin is an open source Sure it is related, but that doesn't answer my question. > Who would keep counters of stable or instable setups? These number are > exceptionally hard to come by. Even if this list is now flooded with "my > setup works" and "m

Re: Cygwin instabilities

On 9/13/10, Markus Hoenicka wrote: > Al was heard to say: > >> I am not asking this to debug my own setup. I am rather ask for an >> overall estimation of Cygwins current and future usability and >> stability. >> > > These two things are related. Remember that Cygwin is an open source > project,

Re: Cygwin instabilities

Al was heard to say: I am not asking this to debug my own setup. I am rather ask for an overall estimation of Cygwins current and future usability and stability. These two things are related. Remember that Cygwin is an open source project, and that it does not employ dozens of developers w

Re: Cygwin instabilities

Hello Larry, >> What are the reasons? Will this be better with Windows 7? Can Cygwin >> become "server stable"? > > You'll need to be more specific about the issues you're encountering > and your configuration.  See . I am not asking this to debug my own setup. I

Re: {lp,cb}Reserved2 under Windows 7 and file descriptors

On Mon, Sep 13, 2010 at 07:11:06AM +0100, Andy Koppe wrote: >Fair enough. Would a standalone utility implementing this hack be >welcome though? Yes. That would help alleviate my concerns about dropping this into Cygwin itself. If we don't see strange problems after a few months of use, I might b

Re: Cygwin instabilities

On 9/13/2010 9:19 AM, Al wrote: Hello, I run Cygwin on a double core machine with Vista. I estimate that 1 of 20 of my compilations break and need to be repeated. One weak point is the compression of man pages. Others report that they don't use Cygwin because of instablilities, especially in th

Cygwin instabilities

Hello, I run Cygwin on a double core machine with Vista. I estimate that 1 of 20 of my compilations break and need to be repeated. One weak point is the compression of man pages. Others report that they don't use Cygwin because of instablilities, especially in the server context. What are the re

Re: malloc-bzero and /proc/pid/statm reading bug

On Sep 12 20:38, Marco Atzeri wrote: > on the ngspice development list one of the developer > find a likely cygwin bug, see description an test case > > --- Dom 12/9/10, Robert Larice ha scritto: > > > Hello All, > > > >   I need some help with a cygwin Problem. > >   Trying to find a bug repor

can't make setup.exe --untrusted-keys to work

I have a custom public key for my repo. This works: setup.exe --keep-untrusted-keys -K basinilya.pub Then I can see that something was added to the end of /etc/setup.rc extrakeys (public-key (dsa (p #00E03CE0...41FD#) ) ) Next time I invoke setup.exe like this: setup.exe --untruste

Re: Question marks in localized man pages

On 12.09.2010 08:51, Ilya Basin wrote: AK> On 11 September 2010 18:48, Ilya Basin wrote: AK> On Saturday, September 11, 2010, Ilya Basin wrote: Hi. My default LANG is C.UTF-8. If I change it to ru.UTF-8, all non-ascii characters in man pages are displayed as question marks.

Re: Oddities with file deletion on CIFS drive

On Sep 12 15:08, Quanah Gibson-Mount wrote: > --On Sunday, September 12, 2010 2:21 PM -0700 Quanah Gibson-Mount wrote: > > >Hi Corinna, > > > >I will give the snapshot a test. Here is the output of attrib: > > > >bu...@zre-win-002 > >/cygdrive/z/current/WINDOWS/ZDESKTOP-608/20100912050101_ZDESKTO