Re: [DynInst_API:] Problems with cotire

["Mark W. Krentel" <krentel@xxxxxxxx>]

As we've previously discussed, I've also had problems with cotire.
Something over parallel builds when building both static and dynamic
libraries.

So yes, I'd either like to turn off cotire or else provide an option
to turn it off.  Master has USE_COTIRE, but it's not exposed, so
currently I have to patch the source.

What would be most useful would be to pick one uniform way of
addressing this, some way to disable cotire, commit this to master,
and then let the other branches pick up the same method.  I just don't
want a situation where I set a variable on one branch, patch a
different branch, something else on a third branch, etc.

Thanks,

--Mark


On 12/11/17 17:06, Bill Williams wrote:
> There's an ENABLE_COTIRE or USE_COTIRE in the top-level CMakeLists that can easily be promoted to a visible cache variable if you like.
>
> You can also try make clean_cotire IIRC (check your makefile for the target name) if this is a system upgrade in place and you've not cleaned out PCHes from pre-upgrade. That should get things moving; I presume you've upgraded well past gcc 4.8 now.