The short version: some auxiliary build commands are trying to touch directories the package manager doesn't want them to touch, resulting in sandbox violation failures of the following format:
===
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: mkdir S: deny P: /root/.trinity A: /root/.trinity R: /root/.trinity C: /usr/trinity/14/bin/tdeconfig_compiler /var/tmp/portage/trinity-base/libkcal-14.0.0/work/tdepim/libkcal/htmlexportsettings.kcfg /var/tmp/portage/trinity-base/libkcal-14.0.0/work/tdepim/libkcal/htmlexportsettings.kcfgc
===
I've attacked a full build log for libtdepim which ends in a couple of failures of the same type.
The long(er) version: Gentoo is a source distribution, so Gentoo packages are more or less glorified build scripts. The package manager creates a per-package sandbox in /var/tmp/portage/ which is used during build and install to keep failures from spewing files all over the system.
For some reason, both tdeconfig_compiler and maketdewidgets are trying to do a mkdir in (probably) ~/.trinity . They don't, as far as I can tell, put anything in the resulting directories. Regardless, this breaks the sandbox and the build can't complete.
This is in 14.0.0, but if there's been a commit that has changed any of this since then, I can't find it.
It's possible that there's an additional CMake variable I need to set, in which case feel free to hit me over the head with it. Otherwise, I need some way of either redirecting those mkdir commands so that they land inside the sandbox, or keeping them from being issued in the first place.
E. Liddell
On 03/12/2016 10:09 PM, E. Liddell wrote:
The short version: some auxiliary build commands are trying to touch directories the package manager doesn't want them to touch, resulting in sandbox violation failures of the following format:
===
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: mkdir S: deny P: /root/.trinity A: /root/.trinity R: /root/.trinity C: /usr/trinity/14/bin/tdeconfig_compiler /var/tmp/portage/trinity-base/libkcal-14.0.0/work/tdepim/libkcal/htmlexportsettings.kcfg /var/tmp/portage/trinity-base/libkcal-14.0.0/work/tdepim/libkcal/htmlexportsettings.kcfgc
===
I've attacked a full build log for libtdepim which ends in a couple of failures of the same type.
The long(er) version: Gentoo is a source distribution, so Gentoo packages are more or less glorified build scripts. The package manager creates a per-package sandbox in /var/tmp/portage/ which is used during build and install to keep failures from spewing files all over the system.
For some reason, both tdeconfig_compiler and maketdewidgets are trying to do a mkdir in (probably) ~/.trinity . They don't, as far as I can tell, put anything in the resulting directories. Regardless, this breaks the sandbox and the build can't complete.
This is in 14.0.0, but if there's been a commit that has changed any of this since then, I can't find it.
It's possible that there's an additional CMake variable I need to set, in which case feel free to hit me over the head with it. Otherwise, I need some way of either redirecting those mkdir commands so that they land inside the sandbox, or keeping them from being issued in the first place.
E. Liddell
Hi E. I have attached a copy of the build log for the whole tdepim on my system (Debian/Stretch). While quite different from Gentoo, I hope this can give you some hints. The part you are probably interested on begins around line 2157. Cheers Michele
2016-03-13 0:09 GMT+03:00 E. Liddell ejlddll@googlemail.com:
The short version: some auxiliary build commands are trying to touch directories the package manager doesn't want them to touch, resulting in sandbox violation failures of the following format:
===
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: mkdir S: deny P: /root/.trinity A: /root/.trinity R: /root/.trinity C: /usr/trinity/14/bin/tdeconfig_compiler /var/tmp/portage/trinity-base/libkcal-14.0.0/work/tdepim/libkcal/htmlexportsettings.kcfg /var/tmp/portage/trinity-base/libkcal-14.0.0/work/tdepim/libkcal/htmlexportsettings.kcfgc
===
I've attacked a full build log for libtdepim which ends in a couple of failures of the same type.
The long(er) version: Gentoo is a source distribution, so Gentoo packages are more or less glorified build scripts. The package manager creates a per-package sandbox in /var/tmp/portage/ which is used during build and install to keep failures from spewing files all over the system.
For some reason, both tdeconfig_compiler and maketdewidgets are trying to do a mkdir in (probably) ~/.trinity . They don't, as far as I can tell, put anything in the resulting directories. Regardless, this breaks the sandbox and the build can't complete.
This is in 14.0.0, but if there's been a commit that has changed any of this since then, I can't find it.
It's possible that there's an additional CMake variable I need to set, in which case feel free to hit me over the head with it. Otherwise, I need some way of either redirecting those mkdir commands so that they land inside the sandbox, or keeping them from being issued in the first place.
E. Liddell
Portage should hook HOME to ${PORTAGE_TMPDIR}/portage/${CATEGORY}/${PF}/homedir. I believe there is something wrong about your configuration... I've just tried — libtdepim-9999 build well for me.
Please provide some common info like "emerge --info '=trinity-base/libtdepim-14.0.0'" and /var/tmp/portage/trinity-base/libkcal-14.0.0/ and what exactly overlay are you using.
2016-03-15 22:25 GMT+03:00 Fat-Zer fatzer2@gmail.com:
2016-03-13 0:09 GMT+03:00 E. Liddell ejlddll@googlemail.com:
The short version: some auxiliary build commands are trying to touch directories the package manager doesn't want them to touch, resulting in sandbox violation failures of the following format:
===
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: mkdir S: deny P: /root/.trinity A: /root/.trinity R: /root/.trinity C: /usr/trinity/14/bin/tdeconfig_compiler /var/tmp/portage/trinity-base/libkcal-14.0.0/work/tdepim/libkcal/htmlexportsettings.kcfg /var/tmp/portage/trinity-base/libkcal-14.0.0/work/tdepim/libkcal/htmlexportsettings.kcfgc
===
I've attacked a full build log for libtdepim which ends in a couple of failures of the same type.
The long(er) version: Gentoo is a source distribution, so Gentoo packages are more or less glorified build scripts. The package manager creates a per-package sandbox in /var/tmp/portage/ which is used during build and install to keep failures from spewing files all over the system.
For some reason, both tdeconfig_compiler and maketdewidgets are trying to do a mkdir in (probably) ~/.trinity . They don't, as far as I can tell, put anything in the resulting directories. Regardless, this breaks the sandbox and the build can't complete.
This is in 14.0.0, but if there's been a commit that has changed any of this since then, I can't find it.
It's possible that there's an additional CMake variable I need to set, in which case feel free to hit me over the head with it. Otherwise, I need some way of either redirecting those mkdir commands so that they land inside the sandbox, or keeping them from being issued in the first place.
E. Liddell
Portage should hook HOME to ${PORTAGE_TMPDIR}/portage/${CATEGORY}/${PF}/homedir. I believe there is something wrong about your configuration... I've just tried — libtdepim-9999 build well for me.
Please provide some common info like "emerge --info '=trinity-base/libtdepim-14.0.0'" and /var/tmp/portage/trinity-base/libkcal-14.0.0/ and what exactly overlay are you using.
Please provide some common info like "emerge --info '=trinity-base/libtdepim-14.0.0'" and /var/tmp/portage/trinity-base/libkcal-14.0.0/temp/environment and what exactly overlay are you using.
Haven't finished the path... Sorry for noise...
On Tue, 15 Mar 2016 22:26:29 +0300 Fat-Zer fatzer2@gmail.com wrote:
2016-03-15 22:25 GMT+03:00 Fat-Zer fatzer2@gmail.com:
2016-03-13 0:09 GMT+03:00 E. Liddell ejlddll@googlemail.com:
The short version: some auxiliary build commands are trying to touch directories the package manager doesn't want them to touch, resulting in sandbox violation failures of the following format:
===
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: mkdir S: deny P: /root/.trinity A: /root/.trinity R: /root/.trinity C: /usr/trinity/14/bin/tdeconfig_compiler /var/tmp/portage/trinity-base/libkcal-14.0.0/work/tdepim/libkcal/htmlexportsettings.kcfg /var/tmp/portage/trinity-base/libkcal-14.0.0/work/tdepim/libkcal/htmlexportsettings.kcfgc
Portage should hook HOME to ${PORTAGE_TMPDIR}/portage/${CATEGORY}/${PF}/homedir. I believe there is something wrong about your configuration... I've just tried — libtdepim-9999 build well for me.
Please provide some common info like "emerge --info '=trinity-base/libtdepim-14.0.0'" and /var/tmp/portage/trinity-base/libkcal-14.0.0/ and what exactly overlay are you using.
Please provide some common info like "emerge --info '=trinity-base/libtdepim-14.0.0'" and /var/tmp/portage/trinity-base/libkcal-14.0.0/temp/environment and what exactly overlay are you using.
Haven't finished the path... Sorry for noise...
Thanks, Fat-Zer--you knocked loose the detail I'd forgotten (the existence of the environment file). It looks like it's trying to write to either TDEHOME or TDEROOTHOME, since setting those lets the build go through.
I clearly haven't been working with ebuilds enough lately.
E. Liddell
2016-03-18 2:18 GMT+03:00 E. Liddell ejlddll@googlemail.com:
On Tue, 15 Mar 2016 22:26:29 +0300 Fat-Zer fatzer2@gmail.com wrote:
Thanks, Fat-Zer--you knocked loose the detail I'd forgotten (the existence of the environment file). It looks like it's trying to write to either TDEHOME or TDEROOTHOME, since setting those lets the build go through.
I clearly haven't been working with ebuilds enough lately.
E. Liddell
I see, you are right, it's a bug in the overlay... I haven't noticed it due to I use sudo that doesn't preserves user env vars. Thanks for reporting, I'll fix it a bit later due to problems with git-2 eclass and recent git...
-
E. Liddell -
Fat-Zer -
Michele Calgaro