And here's number 5 (or 6, depending on how you count). This one adds
the ability to call cygport functions (in addition to the usual
prep/compile/install/ and friends).
It works this way:
cygport cvs-1.11.22-1 custom0-cvs_check_local_known_fail
will invoke cvs_check_local_known_fail() with
A new test version of cvs should hit the mirrors soon. I believe that
the "disappearing 'C'onflicts" problem described here:
http://cygwin.com/ml/cygwin/2006-01/msg01385.html
has been corrected upstream in this release. Also, numerous bug fixes
since 1.11.21-1 (and especially so compared t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Eric Blake on 12/8/2006 1:53 PM:
> It looks like you are picking up the cygwin version of grep/gawk, so I'm not
> sure why you are getting a failure.
As it is, I think there might be a regression in cygwin's handling of
arbitrary length
It's a little more complicated than the subject suggests, the output
vanishes after the first command in a new bash. Have a look at the
following recipe:
1. Start cygwin.bat (no prior setting of the CYGWIN environment
variable)
See the transcript of an example session:
[EMAIL PROTECTED] ~
$ e
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Dave Silvia on 12/8/2006 10:16 AM:
> The list you gave above has an ellipsis, usually denoting there are more. Is
> there a place where this list is kept?
The mailing list archives. The list of problem drivers is ad hoc; it
continues to
Albert Vos writes:
at home and at work I have the same problem with octave under
cygwin. In
both cases I octave just quits without giving any output, no prompt, no
error messages.
Check also that your PATH includes /usr/lib/lapack, as octave appears
to need the dlls found there. My default pat
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Larry Hall (Cygwin)
> Sent: Friday, December 08, 2006 07:20
> To: cygwin@cygwin.com
> Subject: Re: Binaries Don't Execute SOLVED (sort of)
...
> Unless you're referring to something else, this is fixed
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Dave Korn
> Sent: Friday, December 08, 2006 06:54
> To: cygwin@cygwin.com
> Subject: RE: Binaries Don't Execute SOLVED (sort of)
...
> It's worth mentioning that cygcheck can be used to verify
> the
$ mount -m
mount -f -u -b -o managed "C:/cygwin/home/eblake/managed" "/home/eblake/managed"
mount -f -s -b "C:/cygwin/bin" "/usr/bin"
mount -f -s -b "C:/cygwin/lib" "/usr/lib"
mount -f -s -b "C:/cygwin" "/"
mount -s -b --change-cygdrive-prefix "/cygdrive"
$ mkdir managed/dir
$ touch managed/dir
Buchbinder, Barry (NIH/NIAID) [E] niaid.nih.gov> writes:
>
> I get the following error message:
> xargs: grep: Argument list too long
> I've also gotten an equivalent error from xargs/gawk.
It looks like you are picking up the cygwin version of grep/gawk, so I'm not
sure why you are gett
Hi,
I've experienced problem with %view{ascii} mode in Midnight Commander's
bindings. I use enca-like encoding autodetector to tell w3m or another
program what the correct input encoding is:
View=%view{ascii} w3m -dump -I `enca`'
Everything works fine in Linux, but not in Cygwin environment.
In
Steeve Juair wrote:
Hello,
I currently have a problem about rsync and long file name
limit in RSYNC. I used rsync+ssh for backup remote windows server. The
problem that I would like to know if you have new version or a path
avaible to solve this problem about the max length 260 characte
Hello,
I currently have a problem about rsync and long file name
limit in RSYNC. I used rsync+ssh for backup remote windows server. The
problem that I would like to know if you have new version or a path
avaible to solve this problem about the max length 260 characters.
For this error :
I get the following error message:
xargs: grep: Argument list too long
I've also gotten an equivalent error from xargs/gawk.
Of course, the whole idea of xargs is to avoid this error. If I'm doing
something wrong, I'd appreciate some hints of what I am doing wrong or
how to avoid this (ot
Dave Silvia wrote:
-- On Thu, 07 Dec 2006 06:36:05 -0700 Eric Blake wrote --
Are you SURE you don't have a buggy driver installed? Known
culprits include Agnitum outpust, Mcafee virus scanners, Logitech
webcam, ... In other words, the leak is not caused by cygwin, but
by your buggy driver lea
On 08 December 2006 17:36, Voss, Douglas C @ CSW-SLC wrote:
> I'm not sure how this works to put up a reply,
People don't usually bother replying to 5-year old problem reports!
> but having the same problem,
You probably don't have the same problem. The OP's problem was having the
backslas
Cary Jamison wrote:
Matthew Woehlke wrote:
Steve Boyd wrote:
I'm a Cygwin newbie; spent the last 15 years in the tender clutches
of hp-ux. Currently making the jump to Cygwin. I'm looking for a
place to start when it comes to using things I was familiar with on
hp-ux; rlogin, remsh, ftp, etc.
I'm not sure how this works to put up a reply, but having the same problem, I
found a solution not included in the followups:
Try it without the \ before the ;
c:\cygwin\bin\find.exe . -name "files to search pattern" -exec
c:\cygwin\bin\grep.exe "search string" '{}' \; -print
/usr/bin/find: m
Matthew Woehlke wrote:
> Steve Boyd wrote:
>> I'm a Cygwin newbie; spent the last 15 years in the tender clutches
>> of hp-ux. Currently making the jump to Cygwin. I'm looking for a
>> place to start when it comes to using things I was familiar with on
>> hp-ux; rlogin, remsh, ftp, etc. Can anybo
> -- On Thu, 07 Dec 2006 06:36:05 -0700 Eric Blake wrote --
>
>> Are you SURE you don't have a buggy driver installed? Known
>> culprits include Agnitum outpust, Mcafee virus scanners, Logitech
>> webcam, ... In other words, the leak is not caused by cygwin, but
>> by your buggy driver leaking me
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to tbrowder on 12/8/2006 3:51 AM:
>
> I removed the entire installtion and started anew. Everything works now,
> but the command line response gives extra characters sometime. Perhaps the
> latest bash update has something to do with that.
Dave Korn wrote:
On 08 December 2006 10:51, tbrowder wrote:
I removed the entire installtion and started anew. Everything works now,
but the command line response gives extra characters sometime. Perhaps the
latest bash update has something to do with that.
Known bug in libreadline vs. p
Albert Vos wrote:
On 07 December 2006 14:22, Tony Richardson wrote:
Albert Vos hotmail.com> writes:
at home and at work I have the same problem with octave under
cygwin. In
both cases I octave just quits without giving any output, no prompt, no
error messages. One computer runs on win2000 S
On 08 December 2006 10:51, tbrowder wrote:
> I removed the entire installtion and started anew. Everything works now,
> but the command line response gives extra characters sometime. Perhaps the
> latest bash update has something to do with that.
Known bug in libreadline vs. prompts with non
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Dave Korn
> Sent: Wednesday, December 06, 2006 15:56
> To: cygwin@cygwin.com
> Subject: RE: Binaries Don't Execute
...
> WAG[*]: When setup.exe tells you that you have to reboot
> so it can replace
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Lucas Charron
> Sent: Thursday, December 07, 2006 13:21
> To: cygwin@cygwin.com
> Subject: Winsock
...
> I'm using C::B(http://www.codeblocks.org) over cygwin. I'm
> that windows is reporting. This is
> -Original Message-
> From: Igor Peshansky [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, December 05, 2006 21:51
> To: tbrowder
> Cc: cygwin@cygwin.com
> Subject: Re: Binaries Don't Execute
>
> On Tue, 5 Dec 2006, tbrowder wrote:
>
> > I have upgraded my cygwin installation and now some bi
On 07 December 2006 14:22, Tony Richardson wrote:
Albert Vos hotmail.com> writes:
at home and at work I have the same problem with octave under cygwin. In
both cases I octave just quits without giving any output, no prompt, no
error messages. One computer runs on win2000 Sp4 on which I'm no
a
28 matches
Mail list logo
