RE: Windows build error(s)
-Original Message- From: Martin Sebor [mailto:[EMAIL PROTECTED] Sent: Friday, June 22, 2007 3:42 AM To: stdcxx-dev@incubator.apache.org Subject: Re: Windows build error(s) I've found how to handle this error here: http://msdn2.microsoft.com/en-us/library/ms228772(vs.80).aspx Unfortunately, jscript don't present the possibility to install COM message filter, so I've just perform the call in a loop with sleep: http://svn.apache.org/viewvc?view=revrev=548682 This looks like an infinite loop. It might fix the problem with the build but I worry that it could cause trouble under some other error conditions. The MSDN fix also looks quite different (not to mention much more complicated). Isn't there some middle ground between the two approaches? Yes. The both approaches performs retry the call. E.g., could we loop only a limited number of times and only when the error was caused by the timing issue discussed on the MSDN page (if we can reliably detect it)? Perhaps that will help: http://svn.apache.org/viewvc?view=revrev=549748 Unfortunately I can't check how this patch works. Farid.
Re: Windows build error(s)
Farid Zaripov wrote: -Original Message- From: Martin Sebor [mailto:[EMAIL PROTECTED] Sent: Friday, June 22, 2007 3:42 AM To: stdcxx-dev@incubator.apache.org Subject: Re: Windows build error(s) I've found how to handle this error here: http://msdn2.microsoft.com/en-us/library/ms228772(vs.80).aspx Unfortunately, jscript don't present the possibility to install COM message filter, so I've just perform the call in a loop with sleep: http://svn.apache.org/viewvc?view=revrev=548682 This looks like an infinite loop. It might fix the problem with the build but I worry that it could cause trouble under some other error conditions. The MSDN fix also looks quite different (not to mention much more complicated). Isn't there some middle ground between the two approaches? Yes. The both approaches performs retry the call. E.g., could we loop only a limited number of times and only when the error was caused by the timing issue discussed on the MSDN page (if we can reliably detect it)? Perhaps that will help: http://svn.apache.org/viewvc?view=revrev=549748 Unfortunately I can't check how this patch works. Okay, this makes me feel better. Thanks Martin
Re: Windows build error(s)
Farid Zaripov wrote: -Original Message- From: Martin Sebor [mailto:[EMAIL PROTECTED] On Behalf Of Martin Sebor Sent: Saturday, June 16, 2007 7:44 PM To: stdcxx-dev@incubator.apache.org Subject: Windows build error(s) Looks like we're having some problems in Intel C++ builds on Windows (see the error below). Farid, do you know about this? [...] ### Building solution / Creating HTML log Solution build script Checking arguments... Loading solution... D:\bman5\builds\33687223\source-buildspace\etc\config\windows\ build.wsf(226, 10) (null): Call was rejected by callee. I've found how to handle this error here: http://msdn2.microsoft.com/en-us/library/ms228772(vs.80).aspx Unfortunately, jscript don't present the possibility to install COM message filter, so I've just perform the call in a loop with sleep: http://svn.apache.org/viewvc?view=revrev=548682 This looks like an infinite loop. It might fix the problem with the build but I worry that it could cause trouble under some other error conditions. The MSDN fix also looks quite different (not to mention much more complicated). Isn't there some middle ground between the two approaches? E.g., could we loop only a limited number of times and only when the error was caused by the timing issue discussed on the MSDN page (if we can reliably detect it)? Martin
