Re: [jamboost] Re: BBv2 tests failing... since when?

From: Vladimir Prus (ghost_at_[hidden])
Date: 2005-01-24 10:42:37

On Friday 21 January 2005 19:47, David Abrahams wrote:

> >> generators_test : File bin/gcc-3.2/debug/a.obj not added as
> >> expected
> >> -------- all changes caused by last build command ----------
> >> Added files : [..........
> >
> > .......
> >
> >> 'bin/gcc-3.2/debug/a.o',
> >
> > Is this some cygwin system?
>
> No. At least, I'm launching the tests through an ordinary Windows NT
> version of Python. I do have Cygwin installed, and many cygwin
> components are in the path. My GCC is a cygwin GCC. If these tests
> only work when "gcc" invokes a mingw GCC it will be very
> inconvenient. It used to work just fine.

This looks strange. The OBJ type is defined like this:

type OBJ : obj : : NT CYGWIN ;
type OBJ : o ;

so on NT or CYGWIN, "obj" suffix should be used. What suffix is used when you 
build "examples/hello"?

> Incidentally, doing
>
> using gcc : : c:/tools/mingw-2.0/bin/gcc.exe ;
>
> yields
>
> generators_test : 
> "['c:\\boost\\tools\\build\\v2\\test\\../../jam_src\\bin.ntx86\\bjam',
> '-sBOOST_BUILD_PATH=c:\\boost\\tools\\build\\v2\\test', '-d0', '--quiet',
> 'gcc']" returned 1 STDOUT ============
> "WD consuming" d.wd
> "Dolphin consuming" bin\gcc\debug\d_lexer.dlp
> "Whale consuming " bin\gcc\debug\d_parser.whl
> "X_PRO: source is " y.x_pro
> "X: source is " bin\gcc\debug\y.x1 bin\gcc\debug\y.x2
> ...skipped <pbin\gcc\debug>a.exe for lack of <pbin\gcc\debug>x.o...
> warning: using independent target <pbin\gcc\debug>e.positions
> "CPP-MARK consuming " e.cpp
> "NM target source consuming " bin\gcc\debug\e.marked.cpp
> ...failed updating 2 targets...
>
> STDERR ============
> bin/gcc/debug/x.c:1: parse error before string constant

Yes, I see this too. A fix was just committed. When testing with borland, only 
"tag" test fails now -- which I'll investigate.

- Volodya