Sorry, I can't tell from the other bugs listed if my problem is the same one already listed. This showed up for me when doing and emerge @world with an empty tree. The build log has lots if ACCESS DENIED messages. Reproducible: Always I will attach emerge --info and the build log.
Created attachment 544870 [details] emerge --info
I can't get the build.log or some much smaller part of it to be accepted. So here is a sample of the messages. "/usr/bin/al" -link:policy.2.8.config -version:2.8 -out:policy.2.8.glade-sharp.dll -keyfile:gtk-sharp.snk [31;01m*[0m [31;01mACCESS DENIED[0m: mkdir: /etc/mono/registry ALINK: warning A99999: Path 'policy.2.4.config' in the resource name is not supported. Using just file name 'policy.2.4.config' ALINK: warning A99999: Path 'policy.2.6.config' in the resource name is not supported. Using just file name 'policy.2.6.config' ALINK: warning A99999: Path 'policy.2.8.config' in the resource name is not supported. Using just file name 'policy.2.8.config' "/usr/bin/al" -link:policy.2.10.config -version:2.10 -out:policy.2.10.glade-sharp.dll -keyfile:gtk-sharp.snk
Please recompile and *attach* the *compressed* logfile https://wiki.gentoo.org/wiki/Attach_the_logs_to_the_bug_ticket The logs must be part of the ticket, but not on external websites. Please reopen this ticket (Status:unconfirmed) afterwards.
Trying to follow instructions. I have the build.log.xz file. It won't acceept that file using autodetect, manual using as the type .xz, or as an octet stream. So how do I get the system to accept the file. Compressed it is 12136 bytes.
You can get live support with this via IRC #gentoo for example. This ticket is already messed up. Please create a new, clean short and complete ticket with the support.
Got the build.log off of IRC *** This bug has been marked as a duplicate of bug 659422 ***
