On Thu, Aug 16, 2012 at 11:53 AM, Branko Čibej <brane_at_wandisco.com> wrote:
> From IRC:
>
> brane: hm … i don't really understand. it does look like i'll have to install vcexpress 2008 if i want to check what's going on. buildbot logs are less than useful. sigh.
> [1:58pm] danielsh: philipm: moderating you through to announce@
> [1:59pm] philipm: thanks!
> [2:01pm] philipm: brane: the buildbots are not complaining about being unable to find the file so I guess the #include is finding some file
> [2:01pm] philipm: but the file that is found doesn't have the right content.
> [2:03pm] philipm: I'd have expected some sort of "no such file" error if it was an include path problem.
> [2:04pm] philipm: Perhaps the buildbot has an empty version of the file somewhere in the include paths?
>
>
> I managed to test the build with VS2008 (that the WIndows buildbots use)
> and it works. I looked into the possibility that there's an empty
> svn_private_config.h file in the builder's include path; however, the
> intermediate directory is first in the list of inclulde paths, so unless
> the buildbot scripts do something evil, that's not the problem.
I build with VCExpress 2008 as well (and sometimes with VC 2010, but
still mostly with the old one). After your last fix in r1372102,
everything went fine again.
> I think it's now up to the build slave maintainer(s) to figure out
> what's happening. Last I looked, both svn-silk-win42 slaves were offline.
Yup. Maybe it's some subtle difference, like the python version or
something (causing problems during svn_private.h generation) ... (I
have python 2.7.3 from python.org, the buildbots have ActiveState
Python 2.7.1). But that's just a very wild guess.
--
Johan
Received on 2012-08-16 13:39:15 CEST