[Slackbuilds-users] scons and ccache

David Spencer baildon.research at googlemail.com
Wed Aug 10 15:45:27 UTC 2011


On 10 August 2011 15:03, B Watson <yalhcru at gmail.com> wrote:
> For any package that's built with scons, it'd be really polite for the
> maintainer to make a note in the README saying "You must disable ccache
> before building this package". I don't know exactly what the issue is,
> but scons seems to be fundamentally incompatible with ccache...
>
> Eh, or, if anyone has a solution for this, it'd be cool if that were
> mentioned in the README instead. Just a thought.

I don't understand the problem myself, but I know a man who does,
because the gpsd-dev mailing list just had some traffic on this exact
topic.

https://lists.berlios.de/pipermail/gpsd-dev/2011-August/009399.html

"The build system must never ever use a hard-coded
version of gcc or set $PATH to what-it-thinks-is-right, but instead use
$PATH from the environment it was started from. Otherwise neither ccache
nor scan-build (and so on...) will work."

The related patch changed this line in the SConstruct:

-env = Environment(tools=["default", "tar", "textfile"], options=opts)

to this:

+env = Environment(tools=["default", "tar", "textfile"], options=opts,
ENV = {'PATH' : os.environ['PATH']})

As I say, this is not something I understand, but the above
information purports to contain some sort of solution.

-D.


More information about the SlackBuilds-users mailing list