From: Vladimir Prus (ghost_at_[hidden])
Date: 2006-02-22 05:02:26
> Having spent some time trying to get your version of qcc.jam working I
> have taken the executive decision to revert to my original plan and
> produce qcc.jam as a sibling of gcc.jam and, not as a child if gcc.jam.
> Although qcc is based on gcc the command sets are *so* different and I
> found myself overloading almost every statement. In addition I would
> have needed to modify some of the platform conditional logic in gcc.jam
> which I did not want to do. I trust you will not be offended at this
No problem. If you end up overriding everything single option from gcc.jam,
then there's no point in inheriting from gcc.
> The file is attached and it runs the hello & libraries test but there
> are errors with test_all.py.
If you send me the output of test_all.py, I'll take a look.
> I have also started a run of the regression tests but I stopped when I
> saw that there is a problem with qcc.link. I need to add 'libm' to each
> of the linking rules because it has been omitted from the default search
> list on this platform. I have tried adding this as FINDLIBS and
> FINDLIBS-SA but it does not always show up in the right places.
When I run "bjam -n qcc" on the hello example, I get this:
QCC -o "bin/qcc/debug/main" "bin/qcc/debug/main.o" "bin/qcc/debug/a.o"
That is, the "-lm" is there. Is that right? Do you get "-lm" when building
"hello"? And "libraries"?
Or "-lm" is incorrect and something else should be placed? Or you get problem
only when running regressions?
In fact, if -lm should always be added, you can hardcode it in the qcc.link
and qcc.link.dll actions.
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