Re: [gentoo-user] sys-libs/e2fsprogs-libs causing sandbox violation in /root/.ccache?

[Jack <ostroffjh@users.sourceforge.net>]

On 2018.03.29 00:33, P Levine wrote:
> Th
> ​is has been going on for the last few months.  It only seems to  
> happen for
> sys-libs/e2fsprogs-libs.  I haven't filed a bug yet as I'm unsure if  
> there
> is something I'm overlooking on my end.  I can delete /root/.ccache  
> and
> remerge and it seems to be fine after that, but while updating the  
> world a
> few weeks later it sporadically returns.
> 
> The relevant part of the build:
> 
> make[1]: 'compile_et' is up to date.
> > make[1]: Leaving directory
> >  
> '/var/tmp/portage/sys-libs/e2fsprogs-libs-1.44.1/work/e2fsprogs-libs-1.44.1-ab
> > i_x86_64.amd64/lib/et'
> > making all in lib/et
> > * ACCESS DENIED:  utimes:       /root/.ccache
> > * ACCESS DENIED:  mkdir:        /root/.ccache/3
> > make[1]: Entering directory
> >  
> '/var/tmp/portage/sys-libs/e2fsprogs-libs-1.44.1/work/e2fsprogs-libs-1.44.1-a
> > bi_x86_64.amd64/lib/et'
> > make[1]: Nothing to be done for 'all'.
> > make[1]: Leaving directory
> >  
> '/var/tmp/portage/sys-libs/e2fsprogs-libs-1.44.1/work/e2fsprogs-libs-1.44.1-ab
> > i_x86_64.amd64/lib/et'
> 
> 
> ​And the sandbox report:​
> 
> * --------------------------- ACCESS VIOLATION SUMMARY
> > ---------------------------
> > * LOG FILE: "/var/log/sandbox/sandbox-28430.log"
> > *
> > VERSION 1.0
> > FORMAT: F - Function called
> > FORMAT: S - Access Status
> > FORMAT: P - Path as passed to function
> > FORMAT: A - Absolute Path (not canonical)
> > FORMAT: R - Canonical Path
> > FORMAT: C - Command Line
> >
> > F: utimes
> > S: deny
> > P: /root/.ccache
> > A: /root/.ccache
> > R: /root/.ccache
> > C: x86_64-pc-linux-gnu-gcc -x c -v -c /dev/null -o /dev/null
> > F: mkdir
> > S: deny
> > P: /root/.ccache/3
> > A: /root/.ccache/3
> > R: /root/.ccache/3
> > C: x86_64-pc-linux-gnu-gcc -x c -v -c /dev/null -o /dev/null
> > *
> >  
> --------------------------------------------------------------------------------
> 
> 
> Has anyone else run into sporadic build failures like this?
> 
I've had similar issues with various ebuilds, for me most commonly  
nodejs.  It's because of some XDG... environment variable.  Before you  
do the emerge, either do "su -"
  or something else to clear the environment.  It's not really anything  
specific to the ebuild, other than emerge not sanitizing the  
environment first.

Also, what I have sometimes done as a temporary workaround to save  
redoing the compile is to manually go to the build directory and type  
"make" to complete the compile, then complete the remaining ebuild  
steps (install and qmerge, I think - from memory).

Jack