Vladimir Prus wrote:
> On Monday 18 September 2006 04:22, Rene Rivera wrote:
> I recall I seen this failure before, but I though it's gone. It's related to 
> some differences in print module behaviour on Linux and Windows -- either 
> Windows adds some space somewhere or something like that.

Is there any other info you need to figure out how to fix it?

>> But that's not the interesting problem... Second failure is: 
>>
>> generators_test           :
>> "['c:\\DevRoots\\Boost\\boost\\tools\\build\\v2\\test\\../../../jam/src\\bi
>> n.ntx86\\bjam',
>> '-sBOOST_BUILD_PATH=c:\\DevRoots\\Boost\\boost\\tools\\build\\v2\\test',
>> '-d0', '--quiet', 'gcc']" returned 1
>> STDOUT ============
>> warning: no toolsets are configured.
>> warning: you won't be able to build C++ programs.
>> warning: please consult the documentation at
>> warning:
>> http://boost.org/boost-build2/doc/html/bbv2/advanced/configuration.html
> 
> The testsuite will check for file test-config.jam in the 'test' directory. If 
> present, it will be loaded, and user-config.jam will be ignored. It looks 
> like you have such file, but it does not define anything. Can you check if 
> that's the case?

No such file. I haven't touched the test directory at all, other than 
the pyc files python adds.

-- 
-- Grafik - Don't Assume Anything
-- Redshift Software, Inc. - http://redshift-software.com
-- rrivera/acm.org - grafik/redshift-software.com
-- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build