Can't update Bash

[spicy]

I've been having trouble updating bash for a while and I can't update portage because it needs bash. I'll upload the emerge log aswell as the "emerge --info bash" log.

"emerge --info bash" log
https://bpa.st/AOIUQ

"emerge --oneshot bash" log
https://bpa.st/BZTFW

[grknight]

Does it work if you disable pgo USE on app-shells/bash?

Also:

Code: Select all

checking whether /dev/fd is available... sudo: The "no new privileges" flag is set, which prevents sudo from running as root.
sudo: If sudo is running in a container, you may need to adjust the container configuration to disable the flag.
sudo: The "no new privileges" flag is set, which prevents sudo from running as root.
sudo: If sudo is running in a container, you may need to adjust the container configuration to disable the flag.
absent
checking whether /dev/stdin stdout stderr are available... sudo: The "no new privileges" flag is set, which prevents sudo from running as root.
sudo: If sudo is running in a container, you may need to adjust the container configuration to disable the flag.
absent

Don't run emerge with sudo, it breaks stuff like above. Become root first with either sudo -i or su --login to avoid build issues.

[Hu]

Why did you put -v (long form: --version) in MAKEOPTS? It looks like you've caused every call to make to just print a version banner, then exit without doing any work.

[spicy]

Why did you put -v (long form: --version) in MAKEOPTS? It looks like you've caused every call to make to just print a version banner, then exit without doing any work.

You are right, I added that when I was trying something else. This error was actually a new for me but my problem still persists, when I update it runs for a while until it just stops at some point. These are the last lines before it stops: https://bpa.st/PSC3I

EDIT: I tried to remove pgo USE like suggested in a different reply and it solved my problem

[spicy]

Does it work if you disable pgo USE on app-shells/bash?

Also:

Code: Select all

checking whether /dev/fd is available... sudo: The "no new privileges" flag is set, which prevents sudo from running as root.
sudo: If sudo is running in a container, you may need to adjust the container configuration to disable the flag.
sudo: The "no new privileges" flag is set, which prevents sudo from running as root.
sudo: If sudo is running in a container, you may need to adjust the container configuration to disable the flag.
absent
checking whether /dev/stdin stdout stderr are available... sudo: The "no new privileges" flag is set, which prevents sudo from running as root.
sudo: If sudo is running in a container, you may need to adjust the container configuration to disable the flag.
absent

Don't run emerge with sudo, it breaks stuff like above. Become root first with either sudo -i or su --login to avoid build issues.

Updating without pgo USE fixed my problem but what you said is new for me. Using sudo never caused problems for me and the wiki also doesn't suggest anything like this.

[Christian99]

Don't run emerge with sudo, it breaks stuff like above. Become root first with either sudo -i or su --login to avoid build issues.

Really? I'm doing this, like, forever. Why wouldn't this work?

[grknight]

Really? I'm doing this, like, forever. Why wouldn't this work?

As stated above, it is causing a build failure by denying access to /dev/fd. The failures are random and not worth the effort to debug. Many times it is environment bleed but sudo emerge here is causing a PGO failure.

Consistency is key and the best way to rule out environment and other issues it to run emerge after becoming root. The risk of wasted time (or potential security breaches) are not worth the effort otherwise. Clean root login environments provide the optimal result.