On 8/10/2010 10:38 PM, Christopher Faylor wrote:
On Tue, Aug 10, 2010 at 02:04:47PM -0700, Rob Walker wrote:
On 8/10/2010 1:21 PM, Christopher Faylor wrote:
On Tue, Aug 10, 2010 at 01:13:41PM -0700, Rob Walker wrote:
On Cygwin, make-3.82 supports DOS paths by default. I'm c
On Tue, Aug 10, 2010 at 09:53:46PM +, John Carey wrote:
>Thanks for the test case for the CreateFile() problem; I used it to
>create the following test, in which Windows 7 CreateFile() fails with
>ERROR_INVALID_HANDLE even when using a stock Cygwin 1.7.5 DLL:
As Corinna said: If you are mixin
On Tue, Aug 10, 2010 at 02:04:47PM -0700, Rob Walker wrote:
>On 8/10/2010 1:21 PM, Christopher Faylor wrote:
>> On Tue, Aug 10, 2010 at 01:13:41PM -0700, Rob Walker wrote:
>>
>>> On Cygwin, make-3.82 supports DOS paths by default. I'm curious about
>>> what work might be involved in re-enablin
Hello. One of the issues fixed under the New Cygwin DLL 1.7.5-1 release is the
memory leak. Does this mean that we wont have any problems ruuning anti virus
software like Symantec anymore?
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.co
The mingw.org folks are developing a new installer, which uses
WININET.dll facilities for d/l support. When I ran the application from
within a cygwin shell, I ended up with the following debris in my
testing /bin dir:
$ pwd
/c/msys-src/__xml/_test/bin
$ ls
libgcc_s_dw2-1.dll mingw-get.exe*
$
On Aug 10 13:44 +0200 Corinna Vinschen wrote:
> > On Aug 10 00:19, John Carey wrote:
...
> > Presumably the issues mentioned in the source comment may
> > also occur, but what I have seen myself is a subsequent call to
> > SetCurrentDirectory() closing, not the current directory handle, but
> > the
On 8/10/2010 5:04 PM, Rob Walker wrote:
On 8/10/2010 1:21 PM, Christopher Faylor wrote:
On Tue, Aug 10, 2010 at 01:13:41PM -0700, Rob Walker wrote:
On Cygwin, make-3.82 supports DOS paths by default. I'm curious about
what work might be involved in re-enabling the --ms-dos option, and I'd
like
On 8/10/2010 1:21 PM, Christopher Faylor wrote:
On Tue, Aug 10, 2010 at 01:13:41PM -0700, Rob Walker wrote:
On Cygwin, make-3.82 supports DOS paths by default. I'm curious about
what work might be involved in re-enabling the --ms-dos option, and I'd
like to help, if I can.
I built my Cygwi
On Tue, Aug 10, 2010 at 10:51:38PM +0200, Matthias Andree wrote:
>Am 10.08.2010, 19:54 Uhr, schrieb Christopher Faylor:
>
>> I wanted to let everyone know that I'm aware of the fact that make-3.82
>> has been released. However, given the number of reported problems in
>> the make bugs mailing list
Am 10.08.2010, 19:54 Uhr, schrieb Christopher Faylor:
I wanted to let everyone know that I'm aware of the fact that make-3.82
has been released. However, given the number of reported problems in
the make bugs mailing list, I don't plan on releasing a new version of
GNU make until the dust has s
On Tue, Aug 10, 2010 at 01:13:41PM -0700, Rob Walker wrote:
>On Cygwin, make-3.82 supports DOS paths by default. I'm curious about
>what work might be involved in re-enabling the --ms-dos option, and I'd
>like to help, if I can.
>
>I built my Cygwin make-3.82 packages directly from the upstream
On 8/10/2010 10:54 AM, Christopher Faylor wrote:
I wanted to let everyone know that I'm aware of the fact that make-3.82
has been released. However, given the number of reported problems in
the make bugs mailing list, I don't plan on releasing a new version of
GNU make until the dust has settled
I wanted to let everyone know that I'm aware of the fact that make-3.82
has been released. However, given the number of reported problems in
the make bugs mailing list, I don't plan on releasing a new version of
GNU make until the dust has settled. That means no new version of make
for at least a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/08/2010 09:57, Andrey Repin wrote:
> Greetings, John Carey!
>
>> After a call to SetCurrentDirectory(), I have seen occasional (< 5%)
>> failures of CreatePipe() with code ERROR_INVALID_HANDLE. I have also seen
>> failure of Cygwin signal handl
Greetings to you as well! I did try to search, but was unsuccessful. Can you
tell me the subject of one of the messages?
Thanks,
John
Subject: Re: 1.7.5: Occasional failure of CreatePipe or signal handing due to
thread-unsafe code in cwdstuff::set
Gre
summary: I've got a version of python that I need for other purposes.
I'm trying to build duplicity to use with that python. I'm getting
m...@cygwinbox ~/bin/duplicity-0.6.09$ python setup.py install
...
> error: Python was built with Visual Studio 2003;
> extensions must be built with a compiler
I've just instituted a block of email which contains certain email
addresses like "cygwin AT ...", "cygwin-owner AT ..." and others.
Since I'm using spamassassin to do that, I suspect that the bounce message
won't be really clear and it will increase my administrative burden but I
thought I'd give
I don't know if this might interest others, but I have found a thread
explaining the UAC problem at
http://social.answers.microsoft.com/Forums/en-US/vistasecurity/thread/67bfc4
b5-faff-4de4-be48-f395bf1c519d. There is an unofficial third-party software
available from http://www.itknowledge24.com/
On 08/10/2010 12:47 AM, James Arlow wrote:
> Too bad you don't have a WEB BASED BUG TRACKING SYSTEM,
> or you all wouldn't have gotten these two pointless emails
To some degree, we have one: http://cygwin.com/ml/cygwin/ This mailing
list IS our bug tracking system, and it DOES have a web archive.
On 10 August 2010 12:41, David Balažic wrote:
> I have a reasonably up to date cygwin installation (did an update a
> week ago or so).
> Today I run the latest setup (v2.708). In Pending I saw a few libX
> packages and minttty 0.8.1.
>
> Then I selected subversion for install.
> On "Next" I got a d
On Aug 9 16:41, Carles Cufi wrote:
> Hi there,
>
> I just found out in the IRC channel that to avoid trouble with
> cygwin's sed turning \r\n into \n one needs to pass the "--binary"
> flag. But this is not documented in the sed man pages, I was wondering
> if it should be.
I think this is an up
On Aug 10 00:19, John Carey wrote:
> After a call to SetCurrentDirectory(), I have seen occasional (< 5%)
> failures of CreatePipe() with code ERROR_INVALID_HANDLE. I have also
> seen failure of Cygwin signal handling because the signal handling
> pipe has mysteriously closed.
Why on earth are yo
Hi!
I have a reasonably up to date cygwin installation (did an update a
week ago or so).
Today I run the latest setup (v2.708). In Pending I saw a few libX
packages and minttty 0.8.1.
Then I selected subversion for install.
On "Next" I got a dialog saying that subversion depended on additional pa
Greetings, John Carey!
> After a call to SetCurrentDirectory(), I have seen occasional (< 5%)
> failures of CreatePipe() with code ERROR_INVALID_HANDLE. I have also seen
> failure of Cygwin signal handling because the signal handling pipe has
> mysteriously closed.
Seems like it was discussed a
24 matches
Mail list logo
