Re: Create file fails on network drives in cygwin-1.7.9-1

2011-11-23 Thread keith-kube
I had the same problem, and the suggested solution below worked. Failing a permanent fix, it would be great if a future version of cygwin allowed me to specify (via a config file) that I need to mount (some or all) of the /cygdrive directories with noacl option (or even better - pointers on how to

[ANNOUNCEMENT] Updated: astyle-2.02.1-1

2011-11-23 Thread Chris Sutcliffe
I've uploaded a new version astyle, 2.02.1-1, in keeping with the current upstream release. For a list of changes check out http://astyle.sourceforge.net/notes.html. *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, look at the

[ANNOUNCEMENT] Updated: vim-7.3.353-1

2011-11-23 Thread Yaakov (Cygwin/X)
The following packages have been updated for the Cygwin distribution: *** vim-7.3.353-1 *** vim-common-7.3.353-1 *** gvim-7.3.353-1 *** xxd-7.3.353-1 Vim is an advanced text editor that seeks to provide the power of the de-facto Unix editor 'Vi', with a more complete feature set and a choice of t

Re: chere, mksh and pdksh

2011-11-23 Thread Dave Kilroy
On 23/11/2011 08:12, Ronald Fischer wrote: It's been a while since I last refreshed the package, so I'll have a look and see if I can get something done ASAP. Is there a technical reason, why chere needs to know a predefined set of "keys" for the shell to install? If I recall, this was to mak

Re: An AWK-ward problem...

2011-11-23 Thread Christopher Faylor
On Wed, Nov 23, 2011 at 03:21:36PM -0500, Flint, Paul wrote: >Greetings List lurkers, > >I have been troubleshooting some new bash script that I wrote and wanted (for >some reason :^) to run on an NT box. > >So the struggle began... > >Anyway I get the oddest error: > > >/cygdrive/c/Program Files/

An AWK-ward problem...

2011-11-23 Thread Flint, Paul
Greetings List lurkers, I have been troubleshooting some new bash script that I wrote and wanted (for some reason :^) to run on an NT box. So the struggle began... Anyway I get the oddest error: /cygdrive/c/Program Files/Git/bin/awk: line 7: $'\r': command not found /cygdrive/c/Program Files/

Re: cygwin dlls needed to run binutils

2011-11-23 Thread Ryan Johnson
On 23/11/2011 11:47 AM, Surrounder wrote: Larry Hall (Cygwin) wrote: A cygcheck on 'ld' shows cyggcc_s-1.dll is pulled in as a result of a dependency on cygintl-8.dll. I don't see a dependency on cygz.dll but perhaps another tool from the package pulls that one in. I found out that the needed

Re: cygwin dlls needed to run binutils

2011-11-23 Thread Surrounder
I found out that the needed dll´s depend on the .\configure I do, is there a way to find out what options were used makeing binutils last time out of the binaries? I tried searching a list where I can maybe find info about what cygwin dll is used for what function in binutils. Larry Hall (Cygw

Re: cygwin dlls needed to run binutils

2011-11-23 Thread Larry Hall (Cygwin)
On 11/23/2011 10:37 AM, Surrounder wrote: I compiled binutils within cygwin 1.7.9-1 and was wondering why I not only need the cygwin1.dll to run them under windows, I also need the cygz.dll and the cyggcc_s-1.dll Last time I compiled only cagwin1.dll was necessary. Anybody knows if I do sth. wr

cygwin dlls needed to run binutils

2011-11-23 Thread Surrounder
I compiled binutils within cygwin 1.7.9-1 and was wondering why I not only need the cygwin1.dll to run them under windows, I also need the cygz.dll and the cyggcc_s-1.dll Last time I compiled only cagwin1.dll was necessary. Anybody knows if I do sth. wrong or did I miss sth.? Thanks for any resp

cygwin dlls needed to run binutils

2011-11-23 Thread Surrounder
I compiled binutils within cygwin 1.7.9-1 and was wondering why I not only need the cygwin1.dll to run them under windows, I also need the cygz.dll and the cyggcc_s-1.dll Last time I compiled only cagwin1.dll was necessary. Anybody knows if I do sth. wrong or did I miss sth.? Thanks for any resp

Re: "Couldn't allocate heap" - tried rebasing

2011-11-23 Thread Jesse Ziser
On 11/22/2011 10:24 PM, Larry Hall (Cygwin) wrote: On 11/22/2011 8:08 PM, Jon Clugston wrote: Actually, I just noticed this remark: "In summary, current Windows implementations make it impossible to implement a perfectly reliable fork, and occasional fork failures are inevitable." in winsup/d

Re: [ANNOUNCEMENT] Updated: setup.exe (Release 2.761)

2011-11-23 Thread Jon TURNEY
On 23/11/2011 08:48, Eric Lilja wrote: > On 2011-11-21 16:06, Corinna Vinschen wrote: >> A new version of setup.exe, release 2.761, has been uploaded to >> http://cygwin.com/setup.exe. > [snip] >> >> - In unattended mode, if packages were selected on command line, >>install only those, don't al

Cygwin cron does not wake-up the system

2011-11-23 Thread gabier
Hi, I am testing the cron utility, and I created a task which writes the date in a file evry 10 minutes. After a few problems it runs now, but I have noticed that the task was not executed when the computer is sleeping, even if it is not deep sleep (power state is S1 to S3 but deeper sleeping stat

Re: problem with GNU screen solved

2011-11-23 Thread Andrew Schulman
> I just wanted to pass this along... I was having problems with screen > a couple months ago. I would get an error saying "chown tty: No such > file or directory" and then it would fail (see > http://cygwin.com/ml/cygwin/2011-06/msg00222.html). > > Paul Hebble was kind enough to write me off-li

Re: [ANNOUNCEMENT] Updated: setup.exe (Release 2.761)

2011-11-23 Thread Eric Lilja
On 2011-11-21 16:06, Corinna Vinschen wrote: A new version of setup.exe, release 2.761, has been uploaded to http://cygwin.com/setup.exe. [snip] - In unattended mode, if packages were selected on command line, install only those, don't also upgrade all installed packages. Is there some sw

Re: chere, mksh and pdksh

2011-11-23 Thread Ronald Fischer
> It's been a while since I last refreshed the package, so I'll have a > look and see if I can get something done ASAP. Is there a technical reason, why chere needs to know a predefined set of "keys" for the shell to install? For instance, would it not be sufficient to pass the path to the shell?