On 2025-02-22 15:28:13, Mansour Al Akeel wrote: > Michael, > Similar behavior is seen when updating sys-devel/bison. I installed openjdk > instead of graalvm, just in case. Here's the relevant output for emerge: > > checking whether x86_64-pc-linux-gnu-g++ supports POSIXLY_CORRECT=1... yes > checking for dmd... no > checking for -g... no > checking for Java compiler... [31;01m* [0m [31;01mACCESS DENIED [0m: > fopen_wr: /proc/self/coredump_filter > [31;01m* [0m [31;01mACCESS DENIED [0m: fopen_wr:
I didn't know about colm, but in this case it's more obvious what is happening, and it turns out to be the same problem in colm. The ./configure scripts for these packages are testing whether or not your java compiler works, and your java compiler is trying to write to some unusual paths. A workaround for this was introduced in https://bugs.gentoo.org/502280 but if you are using graalvm, you won't have the workaround. Fortunately the entire workaround is to put a SANDBOX_PREDICT entry in a file under /etc/sandbox.d. You should already have a few files there; you can probably copy one and modify it for the paths that are causing issues.
