Re: Cygwin-1.7.0-3 problem (wet paint version)

Corinna Vinschen wrote: On Apr 20 14:52, Trevor Forbes wrote: I access my windows XP PC either via rdesktop or ssh on a Linux Gentoo PC. (Note I use using XPUnlimited to get multiple rdesktops) Using Cygwin-1.7.0-3 I found I can run Cygwin application via ssh or rdesktop but not both at

Cygwin-1.7.0-3 problem (wet paint version)

I access my windows XP PC either via rdesktop or ssh on a Linux Gentoo PC. (Note I use using XPUnlimited to get multiple rdesktops) Using Cygwin-1.7.0-3 I found I can run Cygwin application via ssh or rdesktop but not both at the same time. In the rdesktop session I get the following error

RE: How to delete rogue nul files

I just use a freeware tool... http://www.purgeie.com/delinv.htm Trevor -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/

RE: setup change this year?

One of your local mirror files is corrupt. Trevor > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf > Of Rutten, Mark > Sent: Friday, 30 January 2004 9:09 AM > To: '[EMAIL PROTECTED]' > Subject: setup change this year? > > > Is there something

RE: Please try the latest snapshot -- it is close to cygwin 1.5.6

I was running the open_posix_testsuite against the current "homebuilt" cygwin1.dll but I get the same error if I use the new dll to build itself. It only happens randomly to gcc.exe but it always errors at the same location "0x61085fba". I run the testsuite when I built the dll which gives: FAIL

RE: Please try the latest snapshot -- it is close to cygwin 1.5.6

Using a CVS Head version, I get a popup with: The instruction at "0x61085fba" referenced memory at "0x61002f90". The memory could not be "written" $ addr2line -e /bin/cygwin1.dll 61085fba /src/cygwin/obj/obj-org/i686-pc-cygwin/winsup/cygwin/../../../../../src/ winsup/cygwin/shm.cc:331 /* Try

RE: printf "\n"|perl -pe '1;'|od -a #perl 5.8 converts to *DOS* text :-

> -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf > Of Gerrit P. Haase > > Since Cygwin runs on Windows and Windows is a DOS system the PERLIO > layer crlf is default. > Gerrit, FYI. The new perl DOS default mode is breaking things such as au

RE: binmode() workaround; non ":raw" default- is this a bug or by design?

It's a bug that has a workaround.. Trevor -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/

cygwin symlink? bug

I am having problem with some of my build scripts and the following demonstrates the problem: If run the following (as a script) I get -- /tmp/foo/bar # !/bin/bash cd /tmp; mkdir -p foo/bar; ln -f -s foo/bar bar; cd bar; pwd; cd .. If I type the line in a shell then I get what I expected -- /tmp

missing winsock2.h definitions

Microsoft has a copy of winsock2.h at ftp.microsoft.com/bussys/winsock/winsock2 It has the following copyright: /* Winsock2.h -- definitions to be used with the WinSock 2 DLL and * WinSock 2 applications. * * This header file corresponds to version 2.2.x of the WinSock API * spe

RE: problem with "more" under cygwin-1.3.13-1

> > The newest snapshot should fix this "problem". > > cgf > (who wonders why he even bothers to release snapshots since no one > actually > tries them) > Test Run By trevor on Tue Oct 15 20:48:19 2002 Native configuration is i686-pc-cygwin === winsup tests === Schedule of va