On 01/12/2008, Lee D. Rothstein wrote:
P.S. Cygwin folk say Vista is not supported. That's only because they're
spoiled sports. They expect things to work. ;-)
We do expect things to work but the Cygwin project does (begrudgingly? ;-) )
support Vista. I know. cygcheck output says otherw
Marc/MDPI314 wrote:
Hi,
It has been a long time since I last used Cygwin but these past
days I did my come back ;-)
and I noticed that many processes stops without any message ("joe"
editor, the "make" program,
"configure" script while I were compiling Videolan VLC, the "cd" command
(y
Joel Braverman wrote:
I first encountered this problem months ago while trying to add the xwindows
packages to my cygwin isntall - the installer would hang in the middle. I
deleted all the cygwin files a few days ago and tried again, with the same
problem. It doesn't matter which host I pick to d
Has anyone gotten gm[.exe] to work on Vista?
I keep getting pop-up Windows boxes saying gm has stopped working ...
with of course Vistas favorite non-functioning toggle switch line about
trying to find a solution, blah, blah, blah, blah.
Thanks,
Lee
P.S. Cygwin folk say Vista is not support
Hello,
Sorry, I reactivate this thread
(http://cygwin.com/ml/cygwin/2007-03/msg00029.html) but I have exactly the same
error with process make.
bash: cannot duplicate fd 31 to fd 0: Bad file descriptor
I ran my process make under strace (strace -ostrace.out bash -c make) and got
this (have a l
Hi,
It has been a long time since I last used Cygwin but these past
days I did my come back ;-)
and I noticed that many processes stops without any message ("joe"
editor, the "make" program,
"configure" script while I were compiling Videolan VLC, the "cd" command
(yes, it fails !) and m
Eric Blake byu.net> writes:
>
>
> According to Dave Korn on 1/11/2008 9:38 AM:
> | I believe what is needed is 1) outer double-quotes, for cmd's benefit, 2)
> | inner single-quotes, for bash's benefit, 3) double up the slashes /as well/,
> | because there's one more level of quoting being str
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Dave Korn on 1/11/2008 9:38 AM:
| I believe what is needed is 1) outer double-quotes, for cmd's benefit, 2)
| inner single-quotes, for bash's benefit, 3) double up the slashes /as well/,
| because there's one more level of quoting being
I first encountered this problem months ago while trying to add the xwindows
packages to my cygwin isntall - the installer would hang in the middle. I
deleted all the cygwin files a few days ago and tried again, with the same
problem. It doesn't matter which host I pick to download from, the result
hi, retrieve&send mail by cygwin I know fetchmail and mutt are needed
to get and view the mails. But I am not sure about the sending tool in
cygwin, could you please advise?
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Do
On 11 January 2008 15:51, Phil Betts wrote:
> If you absolutely MUST have backslashes, from cmd.exe, you need to
> double each backslash:
>
> H:\>C:\cygwin\bin\bash -v -c 'UNC_PATH\\Dir'
>
That doesn't work for me. Adding the '-x' option to bash is very handy for
debugging these sorts of
Dear Greg,
Thanks for replying. I ran "cygcheck -s -v -r >cygcheck.out" as requested
and the output is enclosed.
Best Regards,
Rade
==
Innoval Technology Limited
Registration Number: 4583982 in England and Wales
VAT Number: GB 811 9811 35
cygcheck.o
> H:\>C:\cygwin\bin\bash -v -c 'UNC_PATH\\Dir'
>
> (actually only the first really needs to be doubled, because \ has
> no special meaning if it's followed by a letter)
>
> Phil
>
>
I'm getting the path from the registry via a right click menu and passing it
into the bash -c command.
But
On Fri, 11 Jan 2008, Igor Peshansky wrote:
> On Fri, 11 Jan 2008, Corinna Vinschen wrote:
>
> > On Jan 11 10:11, Igor Peshansky wrote:
> > > So, what was the reason, then, to remove "si.wShowWindow = SW_HIDE" from
> > > spawn_guts in CVS? Having it makes it much easier to fix run.exe
> > > approp
On Fri, 11 Jan 2008, Corinna Vinschen wrote:
> On Jan 11 10:11, Igor Peshansky wrote:
> > So, what was the reason, then, to remove "si.wShowWindow = SW_HIDE" from
> > spawn_guts in CVS? Having it makes it much easier to fix run.exe
> > appropriately...
>
> I would be somewhat surprised if this co
Jay wrote on Friday, January 11, 2008 3:14 PM::
>> That's still somewhat wasteful, starting bash just to get a vim
>> alias - why not use the full name gvim, and bypass the bash process
>> to begin with?
>
> you right, i'm going to remove it, thanks.
>
> My main problem now is that for some rea
On Jan 11 10:11, Igor Peshansky wrote:
> So, what was the reason, then, to remove "si.wShowWindow = SW_HIDE" from
> spawn_guts in CVS? Having it makes it much easier to fix run.exe
> appropriately...
I would be somewhat surprised if this code would have any effect in
the trunk. The code in quest
> That's still somewhat wasteful, starting bash just to get a vim alias -
> why not use the full name gvim, and bypass the bash process to begin with?
you right, i'm going to remove it, thanks.
My main problem now is that for some reason the leading backslash on UNC names
is getting dropped when
On Fri, 11 Jan 2008, Corinna Vinschen wrote:
> On Jan 10 23:57, Igor Peshansky wrote:
> > On Fri, 11 Jan 2008, Sven Köhler wrote:
> > > So the question is: who does all the checks (shebang, etc.)?
> > > - the execve implementation? (which is cygwin, right?)
> > > - the shell?
> > > - both?
> >
> >
- Original Message -
From: "Saurabh Tendulkar" <>
To:
Sent: Thursday, January 10, 2008 11:26 PM
Subject: cron does not work: no error message
| Hi,
|
| I upgraded my cygwin recently to the latest cron (4.1-6), and it seems to have
| stopped working. I did a cygrunsrv -E cron when the
-- Rade.Ognjanovic ha scritto:
> Dear Marco,
>
> Thanks for your quick reply. I simplified the path
> variable to just
> path=/usr/bin. That did not solve the problem. I
> also ran "cygcheck -c"
> and the reported status on make is "OK". The
> xorg-x11-bin was
> "incomplete". All other pa
On 2008-01-11 13:53Z, [EMAIL PROTECTED] wrote:
>
> Thanks for your quick reply. I simplified the path variable to just
> path=/usr/bin. That did not solve the problem. I also ran "cygcheck -c"
> and the reported status on make is "OK". The xorg-x11-bin was
> "incomplete". All other package
Dear Marco,
Thanks for your quick reply. I simplified the path variable to just
path=/usr/bin. That did not solve the problem. I also ran "cygcheck -c"
and the reported status on make is "OK". The xorg-x11-bin was
"incomplete". All other packages were "OK".
Best Regards,
Rade
==
--- [EMAIL PROTECTED] ha scritto:
> Hello,
>
> I cannot make the "make" command to work in cygwin.
> When I type "make -v"
> to get its version number it returns nothing, it
> simply goes back to the
> command prompt as shown below.
>
> bash-3.2$ make -v
> bash-3.2$
>
>
> Not Found: awk
>
Hello,
I cannot make the "make" command to work in cygwin. When I type "make -v"
to get its version number it returns nothing, it simply goes back to the
command prompt as shown below.
bash-3.2$ make -v
bash-3.2$
I would appreciate any suggestion on what I can do to get it to work
please. I
On 11 January 2008 08:42, Thorsten Kampe wrote:
> * Rakun (Thu, 10 Jan 2008 11:57:46 -0800 (PST))
>> When I start Cygwin bash shell, I get the folowing message:
>>
>> C:\cygwin\bin\bash.exe (740): *** couldn't allocate cygwin heap, Win32
>> error 0, base 0xA1, top 0xA19000, reserve_size 36864
On Jan 10 23:57, Igor Peshansky wrote:
> On Fri, 11 Jan 2008, Sven Köhler wrote:
> > So the question is: who does all the checks (shebang, etc.)?
> > - the execve implementation? (which is cygwin, right?)
> > - the shell?
> > - both?
>
> The shell.
> Igor
Cygwin's exec(3) calls have shebang
* Rakun (Thu, 10 Jan 2008 11:57:46 -0800 (PST))
> When I start Cygwin bash shell, I get the folowing message:
>
> C:\cygwin\bin\bash.exe (740): *** couldn't allocate cygwin heap, Win32 error
> 0,
> base 0xA1, top 0xA19000, reserve_size 36864, allocsize 36864, page_const
> 409
> 6
> 4 [ma
28 matches
Mail list logo