> >
> > Have we finally lost the AIX tester?  They seem to have vanished from  
> > the trunk report and was just curious what this means about IBM's  
> > (VisualAge) support for Boost?
> >
> > Just curious.
> >
>
> We should still be running the tests. I'll take a look to see what
> is happening.
>

This is taking longer than we expected.  

Walking though the run.py output we can see that run.py successfully downloads the tarballs, builds bjam, configures python then no further output exist in the log file:
...
notice: [python-cfg] include path: "/usr/local/bin/../python/include/python2.4"
notice: [python-cfg] library path: "/usr/local/bin/../python/lib/python2.4/config" "/usr/local/bin/../python/lib"

In a successful run from sometime ago we can see the next step is kicking off bjam to build process_jam_log:

     ...patience...
     ...found 490 targets...
     ...updating 25 targets...
     common.mkdir bin

but this does not show up.

bjam appears fine, I can use the bjam with no issues trying to rule out a bad build of bjam.  It would be helpful if we can get some additional tracing from regression.py.  Is this possible?  Any ideas?  

Chris Cambly
XL C++ Compiler Development