On 2018.06.26 15:44, Christoph Böhmwalder wrote:
On Tue, Jun 26, 2018 at 03:15:09PM -0400, Andrew Udvare wrote:
> It should not be accessing this location in any case. What is the
environment like? What does env show? emerge --config output?
>
> It would almost seem like you have $HOME set to /home/christoph
while Portage is running (as root).
The only thing that stands out about `env` is that XDG_CONFIG_HOME is
set to /home/christoph/.config (running as root). I'm not sure if
it's supposed to be this way, but I didn't find anything in my
dotfiles that would suggest that I'm overwriting it.
That's a normal setting for you. The problem is that when you did sudo
or su to run emerge, it simply stayed in the environment, causing this
problem. When you su or sudo to run emerge (or just log in directly as
root) you need to be sure to do so in a way that cleans out your
environment. I keep thinking to file a bug to request emerge to
sanitize the environment, or at least add an option to make it do so.
I often forget to use them, but I created scripts (cleanemerge and
cleanebuild) to do that for me.
$HOME points to /root.
I'm not sure what you mean by "emerge --config output"? Running
`emerge --config` just gives:
# emerge --config nodejs
Configuring pkg...
Warning: ccache requested but no masquerade dircan be found in
/usr/lib*/ccache/bin
* pkg_config() is not defined: 'nodejs-8.11.1.ebuild'
--
Regards,
Christoph
Jack
