From: Vladimir Prus (ghost_at_[hidden])
Date: 2004-10-05 03:10:27
Vincent Jamart wrote:
> > https://extranet.fft.be/boost/bjamv2-linux2.4.18_x86SMP-icc80.log
> > seems like gcc is still used. Did you use "python test_all.py
> > intel-linux" when running the test?
> I modified the script to force it. We'll see tomorrow if this works.
The current results still have the same problem. In fact, they are 4 days
> > https://extranet.fft.be/boost/bjamv2-solaris9_64-gcc331.log
> > the problems with 64-bit mode are still there. Did you configure gcc
> > with
> > using gcc : : : -m64 -mcpu=v9 : -m64 ;
> > ?
> Yes, using site-config.jam. I can build hello & gettext examples using
> the current setup.
Can you build "libraries" example? Do you have "test-config.jam" in
tools/build/v2/test? If present, that file overrides settings in
> > https://extranet.fft.be/boost/bjamv2-aix51_64-vacpp6.log
> > I think you'd need to run "python test_all.py vacpp" (not the toolset
> > name)
> I check it now
Still uses gcc.
> > https://extranet.fft.be/boost/bjamv2-aix51_64-vacpp7.log
> > Same problem
> > https://extranet.fft.be/boost/bjamv2-irix65_64-mipspro74.log
> > The tests just crash. Maybe, I'm wrong with bjam bin dir detection
> > again. Could you run the 'unit_tests.py' test manually.
> Traceback (most recent call last):
> File "./boost/tools/build/v2/test/unit_tests.py", line 5, in ?
> t = Tester(pass_toolset=0)
> "/disk2/home/qa/cvsboost/boost/tools/build/v2/test/BoostBuild.py", line
> 102, in __init__
> raise "Don't know directory where jam is build for this system: " +
> os.name + "/" + os.uname()
> Don't know directory where jam is build for this system: posix/IRIX64
Wierd. Line 103 of tools/build/v2/test/BoostBuild.py explicitly checks for
this name. Are you sure you've the current version? Is the line there?
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