Windows 2008 64-bit install

I'm trying to install Cygwin on a stock Amazon EC2 Windows 2008 64-bit image. At the end of setup, I get a dialog that says "Postinstall script errors" with the following information in it: Package: Unknown package 000-cygwin-post-install.sh exit code -1073741819 base-files-mket

Re: After installing 1.7.7 command ls is null --now with cygcheck.out

On 01/31/2011 04:50 PM, Larry Hall (Cygwin) wrote: > On 1/31/2011 4:42 PM, Gerry Reno wrote: >> On 01/31/2011 04:16 PM, Gerry Reno wrote: >>> On 01/31/2011 04:14 PM, Larry Hall (Cygwin) wrote: >>> On 1/31/2011 3:49 PM, Gerry Reno wrote: > On 01/31/2011 03:00 PM, Larry Hall (Cygwin) wr

Re: After installing 1.7.7 command ls is null --now with cygcheck.out

On 1/31/2011 4:42 PM, Gerry Reno wrote: On 01/31/2011 04:16 PM, Gerry Reno wrote: On 01/31/2011 04:14 PM, Larry Hall (Cygwin) wrote: On 1/31/2011 3:49 PM, Gerry Reno wrote: On 01/31/2011 03:00 PM, Larry Hall (Cygwin) wrote: This is why you got the complaint about cygwin1.dll being busy

Re: After installing 1.7.7 command ls is null --now with cygcheck.out

On 01/31/2011 04:16 PM, Gerry Reno wrote: > On 01/31/2011 04:14 PM, Larry Hall (Cygwin) wrote: > >> On 1/31/2011 3:49 PM, Gerry Reno wrote: >> >>> On 01/31/2011 03:00 PM, Larry Hall (Cygwin) wrote: >>> >> >> >> This is why you got the complaint about cygwin1.dll being busy

Re: After installing 1.7.7 command ls is null --now with cygcheck.out

On 1/31/2011 4:16 PM, Gerry Reno wrote: On 01/31/2011 04:14 PM, Larry Hall (Cygwin) wrote: On 1/31/2011 3:49 PM, Gerry Reno wrote: On 01/31/2011 03:00 PM, Larry Hall (Cygwin) wrote: This is why you got the complaint about cygwin1.dll being busy. When you did the upgrade, did you download

Re: After installing 1.7.7 command ls is null --now with cygcheck.out

On 01/31/2011 04:14 PM, Larry Hall (Cygwin) wrote: > On 1/31/2011 3:49 PM, Gerry Reno wrote: >> On 01/31/2011 03:00 PM, Larry Hall (Cygwin) wrote: > > > >>> >>> This is why you got the complaint about cygwin1.dll being busy. >>> >>> When you did the upgrade, did you download the current 'setup.exe

Re: 1.7.7: Localization does not follow the language of the OS

Replying to : >> I think that doing setlocale(LC_ALL, ""); on application initialization >> should do the trick. > > Yes it does - assuming you use a libintl from gettext version >= 0.18, > and assuming that you have a #include in the source

Re: After installing 1.7.7 command ls is null --now with cygcheck.out

On 1/31/2011 3:49 PM, Gerry Reno wrote: On 01/31/2011 03:00 PM, Larry Hall (Cygwin) wrote: This is why you got the complaint about cygwin1.dll being busy. When you did the upgrade, did you download the current 'setup.exe' from cygwin.com? Yes. Hm. There was an issue with 'setup.exe' n

Re: After installing 1.7.7 command ls is null --now with cygcheck.out

On 01/31/2011 03:00 PM, Larry Hall (Cygwin) wrote: > On 1/31/2011 2:16 PM, Gerry Reno wrote: >> On 01/31/2011 01:55 PM, Gerry Reno wrote: >>> In my case, I installed cygwin a few months ago and yesterday I went to >>> upgrade it and install several packages. >>> >>> As it was going along it said th

Re: After installing 1.7.7 command ls is null --now with cygcheck.out

On 1/31/2011 2:16 PM, Gerry Reno wrote: On 01/31/2011 01:55 PM, Gerry Reno wrote: In my case, I installed cygwin a few months ago and yesterday I went to upgrade it and install several packages. As it was going along it said that cygwin1.dll was busy so I pressed Continue and at the end it said

Re: After installing 1.7.7 command ls is null --now with cygcheck.out

On 01/31/2011 01:55 PM, Gerry Reno wrote: > In my case, I installed cygwin a few months ago and yesterday I went to > upgrade it and install several packages. > > As it was going along it said that cygwin1.dll was busy so I pressed > Continue and at the end it said a reboot was required. And so I

Re: After installing 1.7.7 command ls is null --now with cygcheck.out

In my case, I installed cygwin a few months ago and yesterday I went to upgrade it and install several packages. As it was going along it said that cygwin1.dll was busy so I pressed Continue and at the end it said a reboot was required. And so I rebooted the machine. When I logged back in, cygw

Re: 16-bit wchar_t on Windows and Cygwin

On Jan 31 09:58, Eric Blake wrote: > > 2) Code that uses mbrtowc() or wcrtomb() is also likely to malfunction. > > On Cygwin >= 1.7 mbrtowc() and wcrtomb() is implemented in an > > intelligent > > but somewhat surprising way: wcrtomb() may return 0, that is, produce > > no > > ou

Re: Issue with socket SO_REUSEADDR when a client is connected.

On 1/31/2011 11:12 AM, jdzstz - gmail dot com wrote: The Cygwin workaround to fix the WinSock SO_REUSEADDR behaviour from back in 2006 was not so nifty after all. I just fixed that in CVS. I'm going to generate a new developer snapshot right now. Should be up in a couple of minutes. Using

Re: 16-bit wchar_t on Windows and Cygwin

[adding cygwin and coreutils for a wc issue] On 01/30/2011 07:04 PM, Bruno Haible wrote: > Hi, > > It is known for a long time that on native Windows, the wchar_t[] encoding on > strings is UTF-16. [1] Now, Corinna Vinschen has confirmed that it is the same > for Cygwin >= 1.7. [2] POSIX require

Re: Issue with socket SO_REUSEADDR when a client is connected.

> > The Cygwin workaround to fix the WinSock SO_REUSEADDR behaviour from > back in 2006 was not so nifty after all.  I just fixed that in CVS.  I'm > going to generate a new developer snapshot right now.  Should be up in a > couple of minutes. > Using cygwin snapshot, the testcase and varnishtest

Re: After installing 1.7.7 command ls is null --now with cygcheck.out

On 01/31/2011 10:15 AM, Jørgen Steensgaard wrote: > Hi > > I have just installed 1.7.7 after several unsuccessful attempts. > Several auxiliary libraries were not included in the installation > after setup finished. OK -- so I had to locate and rerun setup > repeatedly. > > At some point I succeed

Re: After installing 1.7.7 command ls is null --now with cygcheck.out

On 2011-01-31 15:15Z, Jørgen Steensgaard wrote: > > I have just installed 1.7.7 after several unsuccessful attempts. Several > auxiliary libraries were not included in the installation after setup > finished. OK -- so I had to locate and rerun setup repeatedly. cygcheck output indicates versio

Re: On "write" command

On Jan 31 13:28, Dave Korn wrote: > I still think that utmp_data macro is going to return > &utmp_data_buf[nutdbuf] at some point, though. Shouldn't it be "if (utix >= > nutdbuf)"? Indeed. Thanks for catching. I fixed it in CVS. Corinna -- Corinna Vinschen Please, send ma

Re: On "write" command

On 31/01/2011 11:49, Corinna Vinschen wrote: > The utmp file is in the old utmp format for backward compatibility. The > utx functions are available and return a ut_tv field, but it's just > extracted from the utmp ut_time field at function call time. The right > thing to do for write is to have

Re: On "write" command

On Jan 31 11:54, Dave Korn wrote: > On 31/01/2011 01:52, Larry Hall (Cygwin) wrote: > > No, that's the correct place to search. If it's not showing up, none of > > the current packages provide 'write'. > > It's part of util-linux, but it's configured out of the build on Cygwin, > because it rel

Re: On "write" command

On 31/01/2011 01:52, Larry Hall (Cygwin) wrote: > On 1/29/2011 8:20 AM, Angelo Graziosi wrote: >> I would ask if on Cygwin I can use the 'write' command: >> >> write - send a message to another user >> >> $ write USER [ttyname] >> >> I remember I have used it some years ago, but not remember if it

Re: [ANNOUNCEMENT] Updated: OpenSSH-5.7p1-1

On Jan 30 21:13, totaltransaction wrote: > Corinna Vinschen wrote: > > > I've just updated the Cygwin version of OpenSSH to 5.7p1-1. > > Routine create_host_keys of script ssh-host-config has not been > modified to create ECDSA host key files. Perhaps this is intentional, > during an intro peri

Re: 1.7.7: Bash interactive login takes very long (> 1 min)

Le 31/01/2011 10:41, martin.schu...@gmx.de a écrit : Hello, this is a fresh installation on a pc in a corporate domain environment. Cygwin has been installed for all users using a domain user account with local admin privileges. When I start cygwin.bat (wether as privileged user or as normal

Re: 1.7.7: Bash interactive login takes very long (> 1 min)

Am 31.01.2011 10:41, schrieb martin.schu...@gmx.de: > Hello, > > this is a fresh installation on a pc in a corporate domain environment. > Cygwin has been installed for all users using a domain user account with > local admin privileges. ... can you please stop reposting over and over again? Th

Re: 1.7.7: Bash interactive login takes very long (> 1 min)

Am 31.01.2011 10:17, schrieb Schulze, Martin: > Hello, > > this is a fresh installation on a pc in a corporate domain environment. > Cygwin has been installed for all users using a domain user account with > local admin privileges. > > When I start cygwin.bat (wether as privileged user or as no