Created attachment 461898 [details] build.log I found that app-text/dvipng tries to violate sandbox restrictions and operate in user's (root) homedir. See buildlog in attachment.
(In reply to Vadim A. Misbakh-Soloviov (mva) from comment #0) > Created attachment 461898 [details] > build.log Is this the complete build.log? Because it looks like there are no lines from src_compile. Also, please post the output of emerge --info.
(In reply to Ulrich Müller from comment #1) > (In reply to Vadim A. Misbakh-Soloviov (mva) from comment #0) > > Created attachment 461898 [details] > > build.log > > Is this the complete build.log? Because it looks like there are no lines > from src_compile. 1) yes, it is. It is exactly what it printed on the terminal (after keepgoing build finished), and also I just attached the content of /var/log/portage/app-text:dvipng-1.5*2017* (there is only single file for 2017 year). > > Also, please post the output of emerge --info. will add it as second attach...
Created attachment 461900 [details] emerge --info
The issue is with running texi2dvi in src_compile: texi2dvi -I . ./dvipng.texi /usr/bin/texi2dvi: TeX neither supports -recorder nor outputs \openout lines in its log file make: [Makefile:84: dvipng.dvi] Error 1 (ignored) And then it tries to run the command again in src_install, where there is no writeable homedir. So the sandbox violation is just a fallout of the first problem. I cannot reproduce this with TeX Live 2016.
<ulm> aballier: ping, can you reproduce bug 607716? [...] <aballier> ulm: no but it is definitely a broken texlive install; it tries to build tex.fmt installed by texlive-basic <aballier> ulm: toralf had a few broken bugs like this, emerge by default doesnt do -D so deps of deps might not be satisfied... <ulm> aballier: so, close as invalid? <aballier> ulm: from my pov yes
