From: Vladimir Prus (ghost_at_[hidden])
Date: 2005-05-12 00:48:28
On Wednesday 11 May 2005 22:09, David Abrahams wrote:
> David Abrahams <dave_at_[hidden]> writes:
> > Maybe someone can shed some light. What I'm trying to do should be
> > simple. The problems are:
> > 1. Project requirements in parent projects are not used in
> > child projects
> Oops; this was wrong. Apparently the problem was due to a bad
> #include in my code.
> > 2. The response to GCC compilation failures is not useful. Where
> > is the command-line of the failed invocation of g++?
> > 3. Apparently it is attempting to build dependent targets (.exe,
> > .test) after their dependency (copy.o) has already failed to
> > build.
> But these two problems are real. What's going on?
The only reason I can imagine is that "g++" is actually some script that fails
to return the exit code. This is particularly likely given that when msvc
compile fails, you do get the text of the failed command.
Probably there's some misconfiguration of gcc itself, but I don't know how it
-- Vladimir Prus http://vladimir_prus.blogspot.com Boost.Build V2: http://boost.org/boost-build2
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