|
|
Boost Testing : |
Subject: Re: [Boost-testing] [build] Re: regression tests broken on Trunk + Windows?
From: Barend Gehrels (barend_at_[hidden])
Date: 2011-03-26 07:22:09
On 23-3-2011 11:01, Vladimir Prus wrote:
> On Wednesday, March 23, 2011 10:37:27 Jürgen Hunold wrote:
>> Hi David,
>>
>> On Tuesday, 22. March 2011 23:14:07 David Deakins wrote:
>>> We are also seeing this same problem for the VeecoFTC regression test
>>> system. Has there been update on resolving this?
>> I've discussed this on IRC with volodya yesterday, I CC: him in case he
>> missed this thread.
>>
>>>> looks like the change in changeset #70179 isn't working correctly on
>>>> Windows?
>> Yes, exactly. I've got a workaround for the new MAKEDIR builtin, but the
>> real problem is something else.
>>
>> Volodya, your opinion? Shall I commit the workaround I pasted yesterday?
> I've checked in the real fix. For some crazy reasons, some core Jam code
> written before the start of time, though that "c:" does not exist, whereas
> "c:\" does.
Hmm, since I updated the trunk this morning I'm getting the next message
(on both Windows (MSVC) and MinGW):
$ bjam
c:/_svn/boost/trunk/tools/build/v2/util\path.jam:476: in path.makedirs
rule MAKEDIR unknown in module path.
c:/_svn/boost/trunk/tools/build/v2/build\configure.jam:190: in
configure.set-log-file
c:/_svn/boost/trunk/tools/build/v2\build-system.jam:724: in load
c:\_svn\boost\trunk\tools\build\v2/kernel\modules.jam:283: in import
c:\_svn\boost\trunk\tools\build\v2\kernel\bootstrap.jam:142: in boost-build
c:\_svn\boost\trunk\boost-build.jam:17: in module scope
and this message on Linux:
/home/barend/svn/boost/trunk/tools/build/v2/build/configure.jam:192: in
configure.set-log-file
rule FILE_OPEN unknown in module configure.
/home/barend/svn/boost/trunk/tools/build/v2/build-system.jam:724: in load
/home/barend/svn/boost/trunk/tools/build/v2/kernel/modules.jam:283: in
import
/home/barend/svn/boost/trunk/tools/build/v2/kernel/bootstrap.jam:142: in
boost-build
/home/barend/svn/boost/trunk/boost-build.jam:17: in module scope
So actually I cannot run bjam at this moment.
Did I miss something?
Regards, Barend