On Thu, May 02, 2019 at 11:12:02AM +0100, Stuart Henderson wrote:
> There's no reason for www/honk to do anything special with ccache -
> ccache is expected to be transparent and only disabled for exceptional
> cases, normally to break a dependency loop.
> So it seems this is happening because go.port.mk has its own special
> MODGO_ENV instead of using MAKE_ENV like the rest of the tree. Therefore
> it doesn't pass through either the variables to control ccache or the
> standard variables like PATH/HOME/CFLAGS, as a result of this several
> go.port.mk users are having to pass these in by hand.
> I think this is the way to go: switch go.port.mk across and fix up
> the ports using MODGO_ENV. I've built packages for everything using
> MODULES=lang/go, everything is still happy, and run of a sample of
> tests (some work, some fail, but that's not new).
> OK?
I am all for anything that eliminates the proliferation of numerous
brittle variants in the ports tree.
OK kmos
--Kurt
No comments:
Post a Comment