>>> Extracting info
* Package: sys-devel/gcc-10.3.0-r2
* Repository: gentoo
* USE: objc pgo multilib userland_GNU sanitize nptl nls pch cxx graphite openmp amd64 kernel_linux fortran zstd abi_x86_64 ssp pie elibc_glibc
* FEATURES: network-sandbox preserve-libs sandbox usersandbox
>>> Extracting sys-devel/gcc-10.3.0-r2
[sys-devel/gcc-10.3.0-r2] sandbox: /lib64/libc.so.6: version `GLIBC_2.33' not found (required by [sys-devel/gcc-10.3.0-r2] sandbox)
* The ebuild phase 'instprep' has exited unexpectedly. This type of
* behavior is known to be triggered by things such as failed variable
* assignments (bug #190128) or bad substitution errors (bug #200313).
* Normally, before exiting, bash should have displayed an error message
* above. If bash did not produce an error message above, it's possible
* that the ebuild has called `exit` when it should have called `die`
* instead. This behavior may also be triggered by a corrupt bash binary or
* a hardware problem such as memory or cpu malfunction. If the problem is
* not reproducible or it appears to occur randomly, then it is likely to
* be triggered by a hardware problem. If you suspect a hardware problem
* then you should try some basic hardware diagnostics such as memtest.
* Please do not report this as a bug unless it is consistently
* reproducible and you are sure that your bash binary and hardware are
* functioning properly.
[sys-devel/gcc-10.3.0-r2] sandbox: /lib64/libc.so.6: version `GLIBC_2.33' not found (required by [sys-devel/gcc-10.3.0-r2] sandbox)
* The ebuild phase 'die_hooks' has exited unexpectedly. This type of
* behavior is known to be triggered by things such as failed variable
* assignments (bug #190128) or bad substitution errors (bug #200313).
* Normally, before exiting, bash should have displayed an error message
* above. If bash did not produce an error message above, it's possible
* that the ebuild has called `exit` when it should have called `die`
* instead. This behavior may also be triggered by a corrupt bash binary or
* a hardware problem such as memory or cpu malfunction. If the problem is
* not reproducible or it appears to occur randomly, then it is likely to
* be triggered by a hardware problem. If you suspect a hardware problem
* then you should try some basic hardware diagnostics such as memtest.
* Please do not report this as a bug unless it is consistently
* reproducible and you are sure that your bash binary and hardware are
* functioning properly.
!!! instprep failed
[sys-devel/gcc-10.3.0-r2] sandbox: /lib64/libc.so.6: version `GLIBC_2.33' not found (required by [sys-devel/gcc-10.3.0-r2] sandbox)
* The ebuild phase 'other' has exited unexpectedly. This type of behavior
* is known to be triggered by things such as failed variable assignments
* (bug #190128) or bad substitution errors (bug #200313). Normally, before
* exiting, bash should have displayed an error message above. If bash did
* not produce an error message above, it's possible that the ebuild has
* called `exit` when it should have called `die` instead. This behavior
* may also be triggered by a corrupt bash binary or a hardware problem
* such as memory or cpu malfunction. If the problem is not reproducible or
* it appears to occur randomly, then it is likely to be triggered by a
* hardware problem. If you suspect a hardware problem then you should try
* some basic hardware diagnostics such as memtest. Please do not report
* this as a bug unless it is consistently reproducible and you are sure
* that your bash binary and hardware are functioning properly.
Text paste