jan.kolar wrote:
>
> If you do not succeed with snapshots (I'm curious to know),
>
Thanks for your help, and sorry to disappoint you:
I cannot afford in the current situation to invest the time and
effort to learn to install snapshots, build debuggable versions,
and actively compare fixes.
I
Christopher Faylor-8 wrote:
>
> On Sun, Oct 02, 2011 at 03:12:39AM -0700, Marc Girod wrote:
>>marco atzeri-4 wrote:
>>> My experience is that using the standard "problem report" improve the
>>> chance to correctly identify the root cause and reduce the number of
>>> guess that everyone could hav
On Sun, Oct 02, 2011 at 03:12:39AM -0700, Marc Girod wrote:
>marco atzeri-4 wrote:
>> My experience is that using the standard "problem report" improve the
>> chance to correctly identify the root cause and reduce the number of
>> guess that everyone could have.
>>
>One problem I have is that I us
Marc Girod wrote:
>
> Hello,
>
> I keep my installation up-to-date on a weekly basis, and never fail to
> rebaseall/peflagsall as many times as needed to be able to start emacs
> in an X session without fork errors. Then I do a perlrebase.
>
> However, I eventually get STATUS_ACCESS_VIOLATION
Marc Girod wrote:
>
>
> marco atzeri-4 wrote:
>>
>> Problem reports: http://cygwin.com/problems.html
>> so at least we have an idea of your system
>>
>> in addition, have you checked
>> http://cygwin.com/faq/faq.using.html#faq.using.bloda
>>
>> Antivirus and driver are the most likely
marco atzeri-4 wrote:
>
> My experience is that using the standard "problem report" improve the
> chance to correctly identify the root cause and reduce the number of
> guess that everyone could have.
>
One problem I have is that I use this list via the (old) nabble web site,
and this one doesn
On 9/30/2011 5:33 PM, Marc Girod wrote:
marco atzeri-4 wrote:
Problem reports: http://cygwin.com/problems.html
so at least we have an idea of your system
in addition, have you checked
http://cygwin.com/faq/faq.using.html#faq.using.bloda
Antivirus and driver are the most likely culprit
marco atzeri-4 wrote:
>
> Problem reports: http://cygwin.com/problems.html
> so at least we have an idea of your system
>
> in addition, have you checked
> http://cygwin.com/faq/faq.using.html#faq.using.bloda
>
> Antivirus and driver are the most likely culprits.
>
Yes, I know both page
On 9/30/2011 12:04 PM, Marc Girod wrote:
Hello,
I keep my installation up-to-date on a weekly basis, and never fail to
rebaseall/peflagsall as many times as needed to be able to start emacs
in an X session without fork errors. Then I do a perlrebase.
However, I eventually get STATUS_ACCESS_VIO
/bin/rebaseall worked. Great, thanks man!
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
On 11/6/2010 4:57 PM, Joshua Hudson wrote:
78995859 [main] bash 996 child_copy: linked dll data write copy failed, 0x33D000
..0x3414A4, done 0, windows pid 996, Win32 error 487
This indicates one of two things:
1. You need to rebase your system. Install the 'rebase' package and
read th
I am sorry, this was completely my fault.
I made a stupid syntax mistake while changing the source to configure
the program and that was the cause of the problem.
Sorry again.
On Wed, 02 Jun 2010 10:04 -0400, "Christopher Faylor"
wrote:
> On Wed, Jun 02, 2010 at 03:46:11PM +0200, c...@tocaido
cw wrote:
> I am trying to compile the latest release of uw-imapd under Cygwin and
> Windows XP but the program crash after the first command.
>
> This is with the vanilla source from upstream. I know that it is not
> supposed to work very well but yesterday I did the same thing on a
> Windows Se
On Wed, Jun 02, 2010 at 03:46:11PM +0200, c...@tocaido.net wrote:
>Hello,
>
>I am trying to compile the latest release of uw-imapd under Cygwin and
>Windows XP but the program crash after the first command.
>
>This is with the vanilla source from upstream. I know that it is not
>supposed to work ve
On Thu, Mar 21, 2002 at 11:48:51AM -0500, Christopher Faylor wrote:
>On Thu, Mar 21, 2002 at 09:43:31AM +0100, Kandziora Jan wrote:
>>Mark wrote:
>>>mpeg2enc.exe works fine on the build machine (Win98SE with 64MB), but
>>>bombs out with a STATUS_ACCESS_VIOLATION error on another machine
>>>(Win2K
At 11:48 AM 3/21/2002, Christopher Faylor wrote:
>On Thu, Mar 21, 2002 at 09:43:31AM +0100, Kandziora Jan wrote:
> >Mark wrote:
> >>mpeg2enc.exe works fine on the build machine (Win98SE with 64MB), but
> >>bombs out with a STATUS_ACCESS_VIOLATION error on another machine
> >>(Win2K with 256MB). T
On Thu, Mar 21, 2002 at 09:43:31AM +0100, Kandziora Jan wrote:
>Mark wrote:
>>mpeg2enc.exe works fine on the build machine (Win98SE with 64MB), but
>>bombs out with a STATUS_ACCESS_VIOLATION error on another machine
>>(Win2K with 256MB). This machine does not have the Cygwin environment
>>install
Mark wrote:
>
> mpeg2enc.exe works fine on the build machine (Win98SE with 64MB), but
bombs out with a STATUS_ACCESS_VIOLATION error on another machine (Win2K
with 256MB). This machine
> does not have the Cygwin environment installed, but I did (of course) copy
the DLL across. I don't believe ther
18 matches
Mail list logo
