| 1 |
* emake failed |
| 2 |
* |
| 3 |
* If you need support, post the output of `emerge --info '=sys-libs/glibc-2.30-r8::gentoo'`, |
| 4 |
* the complete build log and the output of `emerge -pqv '=sys-libs/glibc-2.30-r8::gentoo'`. |
| 5 |
* The complete build log is located at '/var/tmp/portage/sys-libs/glibc-2.30-r8/temp/build.log'. |
| 6 |
* The ebuild environment file is located at '/var/tmp/portage/sys-libs/glibc-2.30-r8/temp/environment'. |
| 7 |
* Working directory: '/var/tmp/portage/sys-libs/glibc-2.30-r8/work/build-amd64-x86_64-pc-linux-gnu-nptl' |
| 8 |
* S: '/var/tmp/portage/sys-libs/glibc-2.30-r8/work/glibc-2.30' |
| 9 |
/var/tmp/portage/._portage_reinstall_.bpklopl4/bin/isolated-functions.sh: /var/tmp/portage/._portage_reinstall_.bpklopl4/bin/ebuild-ipc: /bin/bash: bad interpreter: No such file or directory |
| 10 |
* The ebuild phase 'install' has exited unexpectedly. This type of |
| 11 |
* behavior is known to be triggered by things such as failed variable |
| 12 |
* assignments (bug #190128) or bad substitution errors (bug #200313). |
| 13 |
* Normally, before exiting, bash should have displayed an error message |
| 14 |
* above. If bash did not produce an error message above, it's possible |
| 15 |
* that the ebuild has called `exit` when it should have called `die` |
| 16 |
* instead. This behavior may also be triggered by a corrupt bash binary or |
| 17 |
* a hardware problem such as memory or cpu malfunction. If the problem is |
| 18 |
* not reproducible or it appears to occur randomly, then it is likely to |
| 19 |
* be triggered by a hardware problem. If you suspect a hardware problem |
| 20 |
* then you should try some basic hardware diagnostics such as memtest. |
| 21 |
* Please do not report this as a bug unless it is consistently |
| 22 |
* reproducible and you are sure that your bash binary and hardware are |
| 23 |
* functioning properly. |
| 24 |
* QA Notice: command not found: |
| 25 |
* |
| 26 |
* /bin/sh: line 2: rm: command not found |
| 27 |
[Errno 2] No such file or directory: b'/usr/bin/sandbox': |
| 28 |
/usr/bin/sandbox /var/tmp/portage/._portage_reinstall_.bpklopl4/bin/misc-functions.sh die_hooks |
| 29 |
Traceback (most recent call last): |
| 30 |
File "/usr/lib64/python3.6/site-packages/portage/process.py", line 389, in spawn |
| 31 |
unshare_flags, cgroup) |
| 32 |
File "/usr/lib64/python3.6/site-packages/portage/process.py", line 736, in _exec |
| 33 |
os.execve(binary, myargs, env) |
| 34 |
File "/usr/lib64/python3.6/site-packages/portage/__init__.py", line 246, in __call__ |
| 35 |
rval = self._func(*wrapped_args, **wrapped_kwargs) |
| 36 |
FileNotFoundError: [Errno 2] No such file or directory: b'/usr/bin/sandbox' |
| 37 |
* The ebuild phase 'die_hooks' has exited unexpectedly. This type of |
| 38 |
* behavior is known to be triggered by things such as failed variable |
| 39 |
* assignments (bug #190128) or bad substitution errors (bug #200313). |
| 40 |
* Normally, before exiting, bash should have displayed an error message |
| 41 |
* above. If bash did not produce an error message above, it's possible |
| 42 |
* that the ebuild has called `exit` when it should have called `die` |
| 43 |
* instead. This behavior may also be triggered by a corrupt bash binary or |
| 44 |
* a hardware problem such as memory or cpu malfunction. If the problem is |
| 45 |
* not reproducible or it appears to occur randomly, then it is likely to |
| 46 |
* be triggered by a hardware problem. If you suspect a hardware problem |
| 47 |
* then you should try some basic hardware diagnostics such as memtest. |
| 48 |
* Please do not report this as a bug unless it is consistently |
| 49 |
* reproducible and you are sure that your bash binary and hardware are |
| 50 |
* functioning properly. |
| 51 |
[Errno 2] No such file or directory: b'/usr/bin/sandbox': |
| 52 |
/usr/bin/sandbox /var/tmp/portage/._portage_reinstall_.bpklopl4/bin/misc-functions.sh die_hooks |
| 53 |
Traceback (most recent call last): |
| 54 |
File "/usr/lib64/python3.6/site-packages/portage/process.py", line 389, in spawn |
| 55 |
unshare_flags, cgroup) |
| 56 |
File "/usr/lib64/python3.6/site-packages/portage/process.py", line 736, in _exec |
| 57 |
os.execve(binary, myargs, env) |
| 58 |
File "/usr/lib64/python3.6/site-packages/portage/__init__.py", line 246, in __call__ |
| 59 |
rval = self._func(*wrapped_args, **wrapped_kwargs) |
| 60 |
FileNotFoundError: [Errno 2] No such file or directory: b'/usr/bin/sandbox' |
| 61 |
* The ebuild phase 'die_hooks' has exited unexpectedly. This type of |
| 62 |
* behavior is known to be triggered by things such as failed variable |
| 63 |
* assignments (bug #190128) or bad substitution errors (bug #200313). |
| 64 |
* Normally, before exiting, bash should have displayed an error message |
| 65 |
* above. If bash did not produce an error message above, it's possible |
| 66 |
* that the ebuild has called `exit` when it should have called `die` |
| 67 |
* instead. This behavior may also be triggered by a corrupt bash binary or |
| 68 |
* a hardware problem such as memory or cpu malfunction. If the problem is |
| 69 |
* not reproducible or it appears to occur randomly, then it is likely to |
| 70 |
* be triggered by a hardware problem. If you suspect a hardware problem |
| 71 |
* then you should try some basic hardware diagnostics such as memtest. |
| 72 |
* Please do not report this as a bug unless it is consistently |
| 73 |
* reproducible and you are sure that your bash binary and hardware are |
| 74 |
* functioning properly. |
| 75 |
* Messages for package sys-apps/portage-2.3.99-r2: |
| 76 |
* Unable to find kernel sources at /usr/src/linux |
| 77 |
* Unable to calculate Linux Kernel version for build, attempting to use running version |
| 78 |
* Messages for package sys-libs/timezone-data-2020a: |
| 79 |
* You do not have TIMEZONE set in /etc/timezone. |
| 80 |
* Skipping auto-update of /etc/localtime. |
| 81 |
* Messages for package sys-process/audit-2.8.4: |
| 82 |
* Unable to find kernel sources at /usr/src/linux |
| 83 |
* Unable to calculate Linux Kernel version for build, attempting to use running version |
| 84 |
* Messages for package app-crypt/gnupg-2.2.19: |
| 85 |
* See https://wiki.gentoo.org/wiki/GnuPG for documentation on gnupg |
| 86 |
* |
| 87 |
* If you wish to use 'gpg-wks-client --send', you must install an MTA! |
| 88 |
* Messages for package sys-apps/util-linux-2.35.1-r2: |
| 89 |
* The mesg/wall/write tools have been disabled due to USE=-tty-helpers. |
| 90 |
* Messages for package dev-lang/python-3.8.2-r2: |
| 91 |
* You have just upgraded from an older version of Python. |
| 92 |
* |
| 93 |
* Please adjust PYTHON_TARGETS (if so desired), and run emerge with the --newuse or --changed-use option to rebuild packages installing python modules. |
| 94 |
* Messages for package sys-libs/glibc-2.30-r8: |
| 95 |
* Applying Gentoo Glibc Patchset 2.30-10 |
| 96 |
* The ebuild phase 'install' has exited unexpectedly. This type of |
| 97 |
* behavior is known to be triggered by things such as failed variable |
| 98 |
* assignments (bug #190128) or bad substitution errors (bug #200313). |
| 99 |
* Normally, before exiting, bash should have displayed an error message |
| 100 |
* above. If bash did not produce an error message above, it's possible |
| 101 |
* that the ebuild has called `exit` when it should have called `die` |
| 102 |
* instead. This behavior may also be triggered by a corrupt bash binary or |
| 103 |
* a hardware problem such as memory or cpu malfunction. If the problem is |
| 104 |
* not reproducible or it appears to occur randomly, then it is likely to |
| 105 |
* be triggered by a hardware problem. If you suspect a hardware problem |
| 106 |
* then you should try some basic hardware diagnostics such as memtest. |
| 107 |
* Please do not report this as a bug unless it is consistently |
| 108 |
* reproducible and you are sure that your bash binary and hardware are |
| 109 |
* functioning properly. |
| 110 |
* ERROR: sys-libs/glibc-2.30-r8::gentoo failed (install phase): |
| 111 |
* emake failed |
| 112 |
* |
| 113 |
* If you need support, post the output of `emerge --info '=sys-libs/glibc-2.30-r8::gentoo'`, |
| 114 |
* the complete build log and the output of `emerge -pqv '=sys-libs/glibc-2.30-r8::gentoo'`. |
| 115 |
* The complete build log is located at '/var/tmp/portage/sys-libs/glibc-2.30-r8/temp/build.log'. |
| 116 |
* The ebuild environment file is located at '/var/tmp/portage/sys-libs/glibc-2.30-r8/temp/environment'. |
| 117 |
* Working directory: '/var/tmp/portage/sys-libs/glibc-2.30-r8/work/build-amd64-x86_64-pc-linux-gnu-nptl' |
| 118 |
* S: '/var/tmp/portage/sys-libs/glibc-2.30-r8/work/glibc-2.30' |
| 119 |
* Messages for package sys-libs/glibc-2.30-r8: |
| 120 |
|
| 121 |
|
| 122 |
|
| 123 |
|
| 124 |
|
| 125 |
|
| 126 |
|
| 127 |
|
| 128 |
|
| 129 |
|
| 130 |
|
| 131 |
|
| 132 |
|
| 133 |
|
| 134 |
|
| 135 |
|
| 136 |
|
| 137 |
!!! existing preserved libs found |
| 138 |
17 May 2020 21:45:03 UTC: ERROR : CatalystError: cmd(['/usr/share/catalyst/targets/stage1/stage1-controller.sh', 'run']) exited 1 |
| 139 |
ERROR:catalyst:CatalystError: cmd(['/usr/share/catalyst/targets/stage1/stage1-controller.sh', 'run']) exited 1 |
| 140 |
17 May 2020 21:45:03 UTC: NOTICE : /release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20200516T183750Z/var/tmp/portage is not a mount point. Skipping |
| 141 |
NOTICE:catalyst:/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20200516T183750Z/var/tmp/portage is not a mount point. Skipping |
| 142 |
17 May 2020 21:45:04 UTC: ERROR : CatalystError: Stage build aborting due to error. |
| 143 |
ERROR:catalyst:CatalystError: Stage build aborting due to error. |
| 144 |
17 May 2020 21:45:04 UTC: ERROR : Exception running action sequence run_local |
| 145 |
Traceback (most recent call last): |
| 146 |
File "/usr/lib64/python3.6/site-packages/catalyst/base/stagebase.py", line 1366, in run_local |
| 147 |
env=self.env) |
| 148 |
File "/usr/lib64/python3.6/site-packages/catalyst/support.py", line 54, in cmd |
| 149 |
print_traceback=False) |
| 150 |
catalyst.support.CatalystError: cmd(['/usr/share/catalyst/targets/stage1/stage1-controller.sh', 'run']) exited 1 |
| 151 |
|
| 152 |
During handling of the above exception, another exception occurred: |
| 153 |
|
| 154 |
Traceback (most recent call last): |
| 155 |
File "/usr/lib64/python3.6/site-packages/catalyst/base/stagebase.py", line 1471, in run |
| 156 |
getattr(self, x)() |
| 157 |
File "/usr/lib64/python3.6/site-packages/catalyst/base/stagebase.py", line 1375, in run_local |
| 158 |
print_traceback=False) |
| 159 |
catalyst.support.CatalystError: Stage build aborting due to error. |
| 160 |
ERROR:catalyst:Exception running action sequence run_local |
| 161 |
Traceback (most recent call last): |
| 162 |
File "/usr/lib64/python3.6/site-packages/catalyst/base/stagebase.py", line 1366, in run_local |
| 163 |
env=self.env) |
| 164 |
File "/usr/lib64/python3.6/site-packages/catalyst/support.py", line 54, in cmd |
| 165 |
print_traceback=False) |
| 166 |
catalyst.support.CatalystError: cmd(['/usr/share/catalyst/targets/stage1/stage1-controller.sh', 'run']) exited 1 |
| 167 |
|
| 168 |
During handling of the above exception, another exception occurred: |
| 169 |
|
| 170 |
Traceback (most recent call last): |
| 171 |
File "/usr/lib64/python3.6/site-packages/catalyst/base/stagebase.py", line 1471, in run |
| 172 |
getattr(self, x)() |
| 173 |
File "/usr/lib64/python3.6/site-packages/catalyst/base/stagebase.py", line 1375, in run_local |
| 174 |
print_traceback=False) |
| 175 |
catalyst.support.CatalystError: Stage build aborting due to error. |
| 176 |
17 May 2020 21:45:04 UTC: NOTICE : Cleaning up... Running unbind() |
| 177 |
NOTICE:catalyst:Cleaning up... Running unbind() |
| 178 |
17 May 2020 21:45:04 UTC: NOTICE : /release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20200516T183750Z/var/cache/binpkgs is not a mount point. Skipping |
| 179 |
NOTICE:catalyst:/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20200516T183750Z/var/cache/binpkgs is not a mount point. Skipping |
| 180 |
17 May 2020 21:45:04 UTC: NOTICE : /release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20200516T183750Z/tmp/stage1root/proc is not a mount point. Skipping |
| 181 |
NOTICE:catalyst:/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20200516T183750Z/tmp/stage1root/proc is not a mount point. Skipping |
| 182 |
17 May 2020 21:45:04 UTC: NOTICE : /release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20200516T183750Z/run is not a mount point. Skipping |
| 183 |
NOTICE:catalyst:/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20200516T183750Z/run is not a mount point. Skipping |
| 184 |
17 May 2020 21:45:04 UTC: NOTICE : /release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20200516T183750Z/dev/shm does not exist. Skipping |
| 185 |
NOTICE:catalyst:/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20200516T183750Z/dev/shm does not exist. Skipping |
| 186 |
17 May 2020 21:45:04 UTC: NOTICE : /release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20200516T183750Z/dev/pts does not exist. Skipping |
| 187 |
NOTICE:catalyst:/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20200516T183750Z/dev/pts does not exist. Skipping |
| 188 |
17 May 2020 21:45:04 UTC: NOTICE : /release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20200516T183750Z/var/tmp/portage is not a mount point. Skipping |
| 189 |
NOTICE:catalyst:/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20200516T183750Z/var/tmp/portage is not a mount point. Skipping |
| 190 |
17 May 2020 21:45:04 UTC: NOTICE : /release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20200516T183750Z/var/cache/distfiles is not a mount point. Skipping |
| 191 |
NOTICE:catalyst:/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20200516T183750Z/var/cache/distfiles is not a mount point. Skipping |
| 192 |
17 May 2020 21:45:04 UTC: NOTICE : /release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20200516T183750Z/var/db/repos/gentoo is not a mount point. Skipping |
| 193 |
NOTICE:catalyst:/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20200516T183750Z/var/db/repos/gentoo is not a mount point. Skipping |
| 194 |
17 May 2020 21:45:04 UTC: NOTICE : /release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20200516T183750Z/dev is not a mount point. Skipping |
| 195 |
NOTICE:catalyst:/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20200516T183750Z/dev is not a mount point. Skipping |
| 196 |
17 May 2020 21:45:04 UTC: NOTICE : /release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20200516T183750Z/proc is not a mount point. Skipping |
| 197 |
NOTICE:catalyst:/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20200516T183750Z/proc is not a mount point. Skipping |
| 198 |
Command exited with non-zero status 2 |
| 199 |
3520.85user 1600.74system 39:50.12elapsed 214%CPU (0avgtext+0avgdata 352288maxresident)k |
| 200 |
527352inputs+8664456outputs (2major+247385457minor)pagefaults 0swaps |
| 201 |
|
| 202 |
|
| 203 |
|
| 204 |
Full build log at /release/tmp/run/catalyst-auto.20200516T183750Z.DLXfhY/log/hardened_stage1-selinux-nomultilib.log |
Archives