I plan eventually to retire the inetd portion of inetutils, in favor of
this resurrected package. It's been orphaned for years; the last update
was in 2002.
http://cygutils.fruitbat.org/ITP/xinetd-2.3.14-1.tar.bz2
http://cygutils.fruitbat.org/ITP/xinetd-2.3.14-1-src.tar.bz2
It's basically a new
The following package has been updated for Cygwin 1.7:
* xorg-server-1.7.6-2
* xorg-server-1.7.99.902-1 (TEST)
This package contains XWin and the other X.Org X11 servers.
This release fixes an erroneous /tmp mounted in textmode warning. A
new 1.8 release candidate has also been made
CVSROOT:/cvs/src
Module name:src
Changes by: cori...@sourceware.org 2010-03-22 10:47:54
Modified files:
winsup/cygwin : ChangeLog fhandler_socket.cc fhandler.h
Log message:
* fhandler_socket.cc (fhandler_socket::evaluate_events): Make erase
const in
Dear Corinna,
I am using the Cygwin 1.5.19 in Windows XP for a long time without any
issue. Rightnow i am porting the build environvent to Windows Server 2003,
but i am getting the Cygwin Issue continuously.
I have stopped the DEP and Terminal Services in Windows Server 2003 and
tried the build
Hallo,
after this answer, I read all the FAQs that I can see and the documentation
that I could find in Cygwin files and tried several times a new installations...
First of all, before an installation I deleted all the Cygwin inforamtion from
the registery (if I understand the FAQ correctly
On Sun, Mar 21, 2010 at 6:10 PM, computer tech wrote:
I have a .bat file, that is scheduled to run as NT Authority\System
every morning. The schedule tasks calls the run.bat file. The script
is running at the schedule time, but when I check the files in the
morning the only output is from
P.S.: I presume the fix will show up in the next Cygwin release.
Nope. It's just for you. No one else is privileged enough to get the
fix. :-)
:-))
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation:
On Mar 22 02:04, Charles Wilson wrote:
I've been tracking down a problem in xinetd. It appears to be an issue
with using MSG_PEEK in recvfrom() on UDP sockets.
Yes, that's a bug in Cygwin. The socket event handling got messed up
when MSG_PEEK was used. I fixed that in CVS so it will be in
On Mar 19 15:13, Matthew Kidd wrote:
I upgraded to Cygwin 1.7.1 on a (64-bit) Windows Server 2003 and
immediately ran into trouble. It seems that Perl can no longer
shutdown
pipes related to Cygwin executables. Here is some example code:
#!/usr/bin/perl
use strict;
# my
Jason Pyeron wrote:
We currently use Symantec Antivirus Corporate Edition v10.1.5.5000.
I have not notices any false positives on our machines (25+) with Cygwin
installed over the past several years.
I don't have that many machines but with McAfee Corporate edition on
my PCs I don't remember
On Mar 17 14:33, Roe, Kevin L. wrote:
It is a netapp, nfs
Here are the results of the command /usr/lib/csih/getVolInfo
/cygdrive/$drive
Device Type: 7
Characteristics: 10
Max Filenamelength : 255
Filesystemname : NTFS
Flags : 4004f
-Original Message-
From: Damon Register
Sent: Monday, March 22, 2010 7:30
Subject: Re: Cygwin Virus
Jason Pyeron wrote:
We currently use Symantec Antivirus Corporate Edition v10.1.5.5000.
I have not notices any false positives on our machines (25+) with
Cygwin installed
On 3/22/2010 7:03 AM, Corinna Vinschen wrote:
On Mar 22 02:04, Charles Wilson wrote:
I've been tracking down a problem in xinetd. It appears to be an issue
with using MSG_PEEK in recvfrom() on UDP sockets.
Yes, that's a bug in Cygwin. The socket event handling got messed up
when MSG_PEEK was
My code use strupr func which is defined in string.h.
But with
$ gcc -std=c99 -c -o grid.o grid.c
I got
grid.c:236: warning: implicit declaration of function 'strupr'.
This is because with -std=c99 gcc define __STRICT_ANSI__:
$ gcc -std=c99 -dM -E - /dev/null | grep __STRICT_ANSI__
On 3/22/2010 6:03 AM, Oleksandr Gavenko wrote:
Current workaround is undefine __STRICT_ANSI__:
$ gcc -std=c99 -U__STRICT_ANSI__ -c -o grid.o grid.c
Where is proper place to report issue?
If you want c99 plus gcc extensions without warnings, how about
-std=gnu99? It seems this may become
On 2010-03-22 13:03Z, Oleksandr Gavenko wrote:
$ gcc -std=c99 -c -o grid.o grid.c
[...]
grid.c:236: warning: implicit declaration of function 'strupr'.
I'd expect that warning, because C99 defines no strupr() function.
--
Problem reports: http://cygwin.com/problems.html
FAQ:
On 2010.03.22 15:30, Tim Prince wrote:
On 3/22/2010 6:03 AM, Oleksandr Gavenko wrote:
Current workaround is undefine __STRICT_ANSI__:
$ gcc -std=c99 -U__STRICT_ANSI__ -c -o grid.o grid.c
Where is proper place to report issue?
If you want c99 plus gcc extensions without warnings, how about
On 2010.03.22 15:34, Greg Chicares wrote:
On 2010-03-22 13:03Z, Oleksandr Gavenko wrote:
$ gcc -std=c99 -c -o grid.o grid.c
[...]
grid.c:236: warning: implicit declaration of function 'strupr'.
I'd expect that warning, because C99 defines no strupr() function.
Ok.
But that the way
On 3/22/2010 7:03 AM, Corinna Vinschen wrote:
On Mar 22 02:04, Charles Wilson wrote:
I've been tracking down a problem in xinetd. It appears to be an issue
with using MSG_PEEK in recvfrom() on UDP sockets.
Yes, that's a bug in Cygwin. The socket event handling got messed up
when MSG_PEEK
I want execute .bat file. I think easy way to do this is
invoke $COMSPEC to do that. Like this
$(subst \,/,$(COMSPEC)) /c file.bat
from Makefile.
But cmd fail with error:
bash# cat 1.bat
@echo off
echo xxx
bash# cmd.exe /c 1.bat
bash: /cygdrive/c/WINDOWS/system32/cmd.exe: Bad address
I
On 3/22/2010 5:33 AM, Mehmet Salgar wrote:
Hallo,
after this answer, I read all the FAQs that I can see and the
documentation that I could find in Cygwin files and tried several times a
new installations...
First of all, before an installation I deleted all the Cygwin inforamtion
from the
On 3/22/2010 11:31 AM, Oleksandr Gavenko wrote:
But where can I get fixed official version of cygwin1.dll?
Or how long wait for release?
As soon as it's ready, you'll see the release announcement here.
If you're looking for time-frames, there's nothing official.
Probably sometime after
On Mar 22 10:56, Charles Wilson wrote:
On 3/22/2010 7:03 AM, Corinna Vinschen wrote:
On Mar 22 02:04, Charles Wilson wrote:
I've been tracking down a problem in xinetd. It appears to be an issue
with using MSG_PEEK in recvfrom() on UDP sockets.
Yes, that's a bug in Cygwin. The socket
Gregg Levine gregg.drw...@gmail.com writes:
Hello! I brought up the Cygwin prompt with the intentions of checking
on a program I had written, and I saw this stuff surface amongst the
fortune program output: 2 [main] bash 2648 child_copy: linked dll data
write copy failed, 0x33D000
On Mon, Mar 22, 2010 at 1:05 PM, J. David Boyd wrote:
Gregg Levine writes:
Hello! I brought up the Cygwin prompt with the intentions of checking
on a program I had written, and I saw this stuff surface amongst the
fortune program output: 2 [main] bash 2648 child_copy: linked dll data
On Mon, Mar 22, 2010 at 11:58:09AM -0400, Larry Hall (Cygwin) wrote:
On 3/22/2010 11:31 AM, Oleksandr Gavenko wrote:
But where can I get fixed official version of cygwin1.dll?
Or how long wait for release?
As soon as it's ready, you'll see the release announcement here.
If you're looking for
On Mon, Mar 22, 2010 at 05:01:00PM +0100, Corinna Vinschen wrote:
On Mar 22 10:56, Charles Wilson wrote:
On 3/22/2010 7:03 AM, Corinna Vinschen wrote:
On Mar 22 02:04, Charles Wilson wrote:
I've been tracking down a problem in xinetd. It appears to be an issue
with using MSG_PEEK in
On 3/22/2010 1:37 PM, Christopher Faylor wrote:
On Mon, Mar 22, 2010 at 05:01:00PM +0100, Corinna Vinschen wrote:
On Mar 22 10:56, Charles Wilson wrote:
On 3/22/2010 7:03 AM, Corinna Vinschen wrote:
On Mar 22 02:04, Charles Wilson wrote:
I've been tracking down a problem in xinetd. It
On Mar 22 13:40, Eliot Moss wrote:
On 3/22/2010 1:37 PM, Christopher Faylor wrote:
On Mon, Mar 22, 2010 at 05:01:00PM +0100, Corinna Vinschen wrote:
On Mar 22 10:56, Charles Wilson wrote:
On 3/22/2010 7:03 AM, Corinna Vinschen wrote:
On Mar 22 02:04, Charles Wilson wrote:
I've been tracking
Gregg Levine gregg.drw...@gmail.com writes:
On Mon, Mar 22, 2010 at 1:05 PM, J. David Boyd wrote:
Gregg Levine writes:
Hello! I brought up the Cygwin prompt with the intentions of checking
on a program I had written, and I saw this stuff surface amongst the
fortune program output: 2
On 3/22/2010 1:54 PM, Corinna Vinschen wrote:
On Mar 22 13:40, Eliot Moss wrote:
On 3/22/2010 1:37 PM, Christopher Faylor wrote:
On Mon, Mar 22, 2010 at 05:01:00PM +0100, Corinna Vinschen wrote:
On Mar 22 10:56, Charles Wilson wrote:
On 3/22/2010 7:03 AM, Corinna Vinschen wrote:
On Mar 22
On 3/22/2010 5:03 AM, Corinna Vinschen wrote:
The last time I had problems with MSG_PEEK was back in 2006. Curious
how seldomly it's used, apparently.
Peeking is evil:
http://tangentsoft.net/wskfaq/newbie.html#peeking
The extra kernel context switch problem isn't Windows-specific,
I upgraded to Cygwin 1.7.1 on a (64-bit) Windows Server 2003
and immediately ran into trouble. It seems that Perl can no
longer shutdown pipes related to Cygwin executables. Here is
some example code:
#!/usr/bin/perl
use strict;
# my $fname = 'Y:\path\to\ratherbigfile.gz';
My text cursor is not being positioned correctly. This is a fresh
install of 1.7.1-1 onto Microsoft Windows XP Professional, Service Pack
2.
In the bash shell the backspace key doesn't back up and overwrite the
last character, same with ctrl-U, the line remains on the screen, with
the cursor at
When running bash under cygwin on Vista 64bit, I get different behavior if I
precede a command with a '\'.
For example, this works fine ($ is the bash prompt),
$ 'C:\cygwin\bin/gcc.exe' -help
Usage: gcc [options] file...
Options:...
However, this fails.
$ 'C:\cygwin\bin\gcc.exe' --help
bash:
I plan eventually to retire the inetd portion of inetutils, in favor of
this resurrected package. It's been orphaned for years; the last update
was in 2002.
http://cygutils.fruitbat.org/ITP/xinetd-2.3.14-1.tar.bz2
http://cygutils.fruitbat.org/ITP/xinetd-2.3.14-1-src.tar.bz2
It's basically a new
On 3/22/2010 7:56 PM, csw wrote:
When running bash under cygwin on Vista 64bit, I get different behavior if I
precede a command with a '\'.
For example, this works fine ($ is the bash prompt),
$ 'C:\cygwin\bin/gcc.exe' -help
Usage: gcc [options] file...
Options:...
However, this fails.
$
37 matches
Mail list logo
