public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: P Levine <plevine457@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] sys-libs/e2fsprogs-libs causing sandbox violation in /root/.ccache?
Date: Thu, 29 Mar 2018 00:33:06 -0400	[thread overview]
Message-ID: <CADX8ZBKuUpk2mfRZfAMgh_wA0pXsP3k2+zumx0UTR+z_bY7BwA@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1865 bytes --]

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?

[-- Attachment #2: Type: text/html, Size: 7065 bytes --]

             reply	other threads:[~2018-03-29  4:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-29  4:33 P Levine [this message]
2018-03-29 12:46 ` [gentoo-user] sys-libs/e2fsprogs-libs causing sandbox violation in /root/.ccache? J García
2018-03-29 12:59   ` Rich Freeman
2018-03-29 15:04 ` Jack

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CADX8ZBKuUpk2mfRZfAMgh_wA0pXsP3k2+zumx0UTR+z_bY7BwA@mail.gmail.com \
    --to=plevine457@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox