[gentoo-user] Re: Ebuild with scons and sandbox

[Andreas Fredriksson <deplinenoise@gmail.com>]

On 8/16/05, Nagatoro <nagatoro@gmail.com> wrote:
> Hi,
> 
> First off, I'm sorry if this is the wrong place to ask!
> 
> I'm trying to write an ebuild for linuxdcpp (a gtk port of DC++). This 
> nice app uses scons and not make as the build tool. When I build it 
> manually it works just fine, but when I try to build it with emerge (or 
> ebuild) I get this:
> Code:
> 
> scons: done building targets.
> ACCESS DENIED  open_wr:   /usr/include/gtk-2.0/gtk/.scons25064

[ SNIP ]

> it seems to me like scons is littering the filesystem with somesort of 
> lock files but I've been unable to find any information on this. Does 
> anyone know how I can prevent scons from trying to make these files or 
> how I can fool scons into thinking that it could?

I'm a SCons user so maybe I can shed some light on the issue. SCons
uses content signatures rather than time stamps by default, that is it
detects file changes by accumulating MD5 signatures of preprocessed
data (i.e. with dependencies).

This doesn't work very well on directories such as /usr, but SCons
suppresses these errors by default since it's a normal situation on
UNIX-like systems.

The usual way is to move the include paths from SCons' CPPPATH
construction variable to the CXXFLAGS (or CCFLAGS). This way SCons
doesn't get to see the directories and therefore ignores the files
during the dependency scan.

You can also change the target signatures method to use time stamps
ranther than content stamps.

A good resource for making these modifications would be the scons site
at www.scons.org and the wiki on the same site which has lots of
information.

Regards,
Andreas
-- 
And I hate redundancy, and having different functions for the same thing.
        - Linus Torvalds on linux-kernel

-- 
gentoo-user@gentoo.org mailing list