Re: sh script works, zsh script doesn't

>There is nothing wrong with this mail list, although it may not conform to >your personal preference. This list does not dictate to the sender where >replies will go. It leaves that up to the sender. If posters want email >to go to the list rather than to them, it's simply a matter of setting t

Re: sh script works, zsh script doesn't

On 05/26/2006, Vidiot wrote: [Can the listmaster fix the mail list so that it sends the reply back to the list and not to the poster? I sent the e-mail before remembering that this mail list gets it wrong, at least AFAIAC.] There is nothing wrong with this mail list, although it may not confo

How to link

My Cygwin dir is C:\cygwin I got a simple Winsock program & would like to compile it. The libwsock32.a is in \lib\32api\ What's the parameter given to GCC so it links the program with the library in C:\cygwin\lib\w32api ? -- View this message in context: http://www.nabble.com/How+to+link-t16902

Re: sh script works, zsh script doesn't

IT WORKS!!! The original problem with the "-a 0" being a combined value was it. When I separated them, I get the echo into the log correct for the new variable names, but had a typo for for one of them in the actual command launch. Thanks for the pointer/tip. Onward and upward. MB -- e-mail:

Re: Cygwin: texi2dvi stumbles over texinfo.tex [attn texinfo maintainer]

On Fri, May 26, 2006 at 09:33:12PM +, Eric Blake wrote: >cgf wrote: > >> >0022FF88 61005EB3 (, , , ) >> >> That's apparently a call to mktemp, although I can't tell what's causing >> the problem. > >Well, looking at the source to the cygwin distribution of

Re: sh script works, zsh script doesn't

[Can the listmaster fix the mail list so that it sends the reply back to the list and not to the poster? I sent the e-mail before remembering that this mail list gets it wrong, at least AFAIAC.] >Vidiot doesn't really state how zsh fails, so I'd really like more >details as to what he's seeing.

Re: Problems with ssh/scp/sftp on a dual core Dell Latitude D820

Dave Korn artimi.com> writes: > > On 26 May 2006 18:54, Larry Hall (Cygwin) wrote: > > > Samuel Thibault wrote: > >> Chris Richardson, le Fri 26 May 2006 06:22:32 -0700, a écrit : > >>> Does anyone have a fix for this? > >> > >> Disable the second core. Cygwin seems to not work very well with

2003 Installing inetd as a service

What's the best way to install inetd as a service on Windows 2003. I used to use inetd --install-as-service but I'm thinking a cygrunsrv -I inetd style line would be better. Also, since what I want to accomplish is the ability to telnet, rlogin, rsh into the 2003 server running the inetd servi

Re: Cygwin: texi2dvi stumbles over texinfo.tex [attn texinfo maintainer]

cgf wrote: > >0022FF88 61005EB3 (, , , ) > > That's apparently a call to mktemp, although I can't tell what's causing > the problem. Well, looking at the source to the cygwin distribution of texinfo, it is pretty obvious: $ diff -u texindex.c.orig texindex.

RE: sh script works, zsh script doesn't

On Fri, 26 May 2006, Dave Korn wrote: On 26 May 2006 06:29, Vidiot wrote: But, if anyone has a clue as to why starting of a Windblows program from a Z-shell doesn't work, yet from a shell-script, it does, I'd certainly appreciate knowing. Well, isn't it going to be because sh and zsh are di

Re: slow share = slow scripts?

Christopher Faylor wrote: On Fri, May 26, 2006 at 10:37:52AM -0500, mwoehlke wrote: Way way back in the OP, I mentioned that Interix doesn't have this problem, which would imply a "design flaw" in Cygwin. Maybe (probably) it is a *necessary* design flaw, BUT... A "necessary" design flaw? Int

Re: slow share = slow scripts?

Dave Korn wrote: On 26 May 2006 16:38, mwoehlke wrote: [snip] Way way back in the OP, I mentioned that Interix doesn't have this problem, which would imply a "design flaw" in Cygwin. Maybe (probably) it is a *necessary* design flaw, BUT... You are now piling pointless and incorrect speculati

Cygwin ping from restricted acct yields "recvfrom: Invalid argume nt"

Here's a strange problem from Cygwin ver 1.5.19 (0.150/4/2) under Windows2000 (v5.00.2195): If I run a simple ping (even ping localhost) from a Windows account that is classified by Windows as a "Restricted user (Users Group)", I get: ping: recvfrom: Invalid argument repeated over & over

Re: Windows Vista Beta 2

"Robert Pendell" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] Jennifer Smith wrote: I tried to install cygwin on the Windows Vista Beta 2 (build 5308), here are the problems I've run into: 1) During package install bash seems to crash. I get this dialog from windows: Please clos

Cygwin G++ bug? - Python Extension module #including dies before initialization

Hi, I compiled a C++ Python Extension, and found that it caused the Python interpreter process to silently die (with a *zero* exitcode!) when it attempted to load the extension module. I traced the problem to the line: static ios_base::Init __ioinit; in . It seems that when the module is dlope

Re: problem + workaround: system shared memory version mismatch detected

Top-posting reformatted. On Fri, May 26, 2006 at 02:16:31PM -0400, Larry Hall (Cygwin) wrote: Hey, wouldn't it be cool if we had a FAQ entry about this... hey we do! Will wonders never cease? ;-) >noel natnix com wrote:

Re: problem + workaround: system shared memory version mismatch detected

Thanks Larry, Maybe putting the exact error message in the FAQ would make it more google-friendly. My google search search for: site:cygwin.com faq system shared memory version mismatch detected Only turned up a lot of desperate posts with no clear solution. It looks like a fairly common probl

Re: sh script works, zsh script doesn't

>I think that the problem is the difference between ZSH's parameter >expansion and sh's parameter expansion. I think that your $MUX gets >expanded into single parameter "-a 0", instead of two parameters "-a" >and "0", that you expect. I separated MUX into two separate variables. Believe it or not

Re: problem + workaround: system shared memory version mismatch detected

[EMAIL PROTECTED] wrote: Problem: Running an older cygwin app can cause newer cygwin apps to fail with "system shared memory version mismatch detected" To Reproduce: 1) start a newer cygwin bash shell. I tested cygwin version 1.5.19-4. 2) run an app that uses an older cygwin1.dll. My app us

problem + workaround: system shared memory version mismatch detected

Problem: Running an older cygwin app can cause newer cygwin apps to fail with "system shared memory version mismatch detected" To Reproduce: 1) start a newer cygwin bash shell. I tested cygwin version 1.5.19-4. 2) run an app that uses an older cygwin1.dll. My app used cygwin1.dll. File->P

RE: Problems with ssh/scp/sftp on a dual core Dell Latitude D820

On 26 May 2006 18:54, Larry Hall (Cygwin) wrote: > Samuel Thibault wrote: >> Chris Richardson, le Fri 26 May 2006 06:22:32 -0700, a écrit : >>> Does anyone have a fix for this? >> >> Disable the second core. Cygwin seems to not work very well with SMP >> systems. > > > That's a sweeping statem

Re: Problems with ssh/scp/sftp on a dual core Dell Latitude D820

Samuel Thibault wrote: Chris Richardson, le Fri 26 May 2006 06:22:32 -0700, a écrit : Does anyone have a fix for this? Disable the second core. Cygwin seems to not work very well with SMP systems. That's a sweeping statement that doesn't hold up to scrutiny. Plenty of folks use Cygwin qui

Re: Problems with ssh/scp/sftp on a dual core Dell Latitude D820

Chris Richardson, le Fri 26 May 2006 06:22:32 -0700, a écrit : > Does anyone have a fix for this? Disable the second core. Cygwin seems to not work very well with SMP systems. Samuel -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/prob

Problems with ssh/scp/sftp on a dual core Dell Latitude D820

Hi, I also am having problems with scp, sftp, and ssh on my dual core latitude D820. Trying to use sftp and scp with large files results in a stack dump: Exception: STATUS_ACCESS_VIOLATION at eip=00D049B9 eax=0013 ebx=002298AC ecx=717D9EA7 edx=00229900 esi=7C809BF5 edi=717D9EA7 ebp=0022B920

Cygwin c++ vs windows or unix socket layer

Hi all, I've stumbled across a small problem. As you may know, cygwin attempts to give the user a free choice of using the winsock API, with SOCKETs being handles not fds, and ioctlsocket and closesocket and so on, or using the posix sockets API, and having sockets being fds just like a

RE: slow share = slow scripts?

On 26 May 2006 16:38, mwoehlke wrote: > Like... what? Inode information? Looking at the man page for 'stat' (on > Linux, anyway; apparently I don't have the libc man pages installed on > Cygwin), I don't see anything that I would expect to need to *open* the > file to retrieve. That goes to sho

Re: stdio.h

On Fri, May 26, 2006 at 08:55:23AM -0700, David A. Case wrote: >On Fri, May 26, 2006, Brian Dessent wrote: >> >> 2. In current versions of Cygwin getline and getdelim are only defined >> if the user defines _GNU_SOURCE - this is the same way it's done on >> linux. > >This change doesn't seem(?) to

Re: slow share = slow scripts?

On Fri, May 26, 2006 at 10:37:52AM -0500, mwoehlke wrote: >Gary R. Van Sickle wrote: >>>From: mwoehlke >>[snip] >>> Also, why *is* >>>fstat() so inefficient? >> >>Short answer: because it gets a bunch of information about the file that >>isn't necessarily available without hitting (open()ing) the

Re: stdio.h

On Fri, May 26, 2006, Brian Dessent wrote: > > 2. In current versions of Cygwin getline and getdelim are only defined > if the user defines _GNU_SOURCE - this is the same way it's done on > linux. This change doesn't seem(?) to be in /usr/include/sys/stdio.h from Cygwin DLL 1.5.19-4. So I think

Re: slow share = slow scripts?

Gary R. Van Sickle wrote: From: mwoehlke [snip] Also, why *is* fstat() so inefficient? Short answer: because it gets a bunch of information about the file that isn't necessarily available without hitting (open()ing) the file itself. Like... what? Inode information? Looking at the man page

Re: stdio.h

Wynfield Henman wrote: > > I have run into problems with getline being defined in stdio.h > > I understand that a GNU system has it defined there but not any other system. > > Please look into where "getline" should be defined in stdio.h or not. 1. This issue has already been thoroughly discus

RE: stdio.h

On 26 May 2006 06:14, Wynfield Henman wrote: > I have run into problems with getline being defined in stdio.h That's a really imprecise description of the situation. Could mean anything. > I understand that a GNU system has it defined there but not any other > system. > > Please look into

RE: sh script works, zsh script doesn't

On 26 May 2006 06:29, Vidiot wrote: > But, if anyone has a clue as to why starting of a Windblows program from > a Z-shell doesn't work, yet from a shell-script, it does, I'd certainly > appreciate knowing. Well, isn't it going to be because sh and zsh are different shells with different syntax