[Boost-testing] regression.py bootstrapping broken on cygwin?

From: Roland Schwarz (roland.schwarz_at_[hidden])
Date: 2007-02-10 11:07:14

The boosttrapping appears to be broken on cygwin.
Al though the bjam.exe process_jam_log.exe and compiler_status.exe
programs are generated the following step is not able to find them.

Could it be, that regression.py is not considering the .exe suffix?

I excerpted a piece of the output:

MkDir1 ../../../dist
MkDir1 ../../../dist/bin
common.copy ../../../dist/bin/process_jam_log.exe
common.copy ../../../dist/bin/compiler_status.exe
...updated 29 targets...
# Searching for "process_jam_log" in "/boost-regression/gcc-d/boost/dist/bin"...
Traceback (most recent call last):
   File "regression.py", line 950, in ?
     commands[ command ]( **accept_args( args ) )
   File "regression.py", line 765, in regression
     v2, [] )
   File "regression.py", line 462, in setup
     build_if_needed( process_jam_log, pjl_toolset, toolsets, v2 )
   File "regression.py", line 409, in build_if_needed
     tool[ 'build_path' ] = tool_path( tool, v2 )
   File "regression.py", line 370, in tool_path
     raise Exception( 'Cannot find "%s" in any of the following locations:\n%s' % (
Exception: Cannot find "process_jam_log" in any of the following locations:
/boost-regression/gcc-d/process_jam_log
/boost-regression/gcc-d/boost/dist/bin

Roland