Re: [Boost-build] Changes to template-depth in qcc.jam not workingfully

Subject: Re: [Boost-build] Changes to template-depth in qcc.jam not workingfully
From: Niklas Angare (li51ckf02_at_[hidden])
Date: 2008-11-25 19:30:16

> I wonder -- how different qcc is from
> gcc? Does it have -fPIC? Does it have threading support?

qcc/QCC is some kind of wrapper for GCC, like cc. You can use -Wc,-fPIC but 
I think the proper way is to use -shared (which when I tried it passed -fpic 
to the compiler). It supports threads but you don't have to specify -pthread 
or anything like that.

> Or rather -- does anyting break if you use the gcc toolset, as opposed to 
> qcc?
> It might be best strategy to make gcc handle both, rather than risk 
> further
> differences in behaviour.

Do you mean with QCC? You'd have to put -Wc, or -Wl, in front of a lot of 
the options to pass them to the compiler and linker.

g++ is available so the gcc toolset sort of works directly and builds some 
parts of Boost. The -pthread option isn't supported or needed though so some 
libraries refuse to compile with the current gcc.jam. I guess that would be 
an easy fix but I don't have much interest in pursuing that at the moment. I 
prefer to use the QNX-recommended QCC with the Dinkumware library.

I ran a regression test with the gcc toolset (g++ compiler) by mistake a few 
weeks ago when I first started messing around with testing and the results 
are on the test summary page for the release branch.