From: Vladimir Prus (ghost_at_[hidden])
Date: 2006-10-07 15:33:34
Rene Rivera wrote:
> 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?
Not sure. I'm not quite up-to-speed with printing code. It's possible to run
just one test with the --preserve option and it will put the failing setup
in dir 'failed_test'.
>>> But that's not the interesting problem... Second failure is:
>>> generators_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
>> 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.
Then it's probably some Windows-specific issue with search paths. For a
start, can you create test/test-config.jam and add
using gcc ;
there? If that works out, and there are no further issues, we can
investigate why your user-config.jam is not found.
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk