| 1 |
>>> '/var/tmp/portage/app-crypt/gnupg-2.2.20/temp/build.log' |
| 2 |
>>> Failed to emerge sys-apps/gawk-4.2.1-r1, Log file: |
| 3 |
>>> '/var/tmp/portage/sys-apps/gawk-4.2.1-r1/temp/build.log' |
| 4 |
>>> Failed to emerge net-misc/wget-1.20.3-r3, Log file: |
| 5 |
>>> '/var/tmp/portage/net-misc/wget-1.20.3-r3/temp/build.log' |
| 6 |
* Messages for package sys-libs/timezone-data-2020a: |
| 7 |
* You do not have TIMEZONE set in /etc/timezone. |
| 8 |
* Skipping auto-update of /etc/localtime. |
| 9 |
* Messages for package net-misc/wget-1.20.3-r3: |
| 10 |
* The ebuild phase 'configure' 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 |
* ERROR: net-misc/wget-1.20.3-r3::gentoo failed (configure phase): |
| 25 |
* econf failed |
| 26 |
* |
| 27 |
* Call stack: |
| 28 |
* , line 125: Called src_configure |
| 29 |
* , line 2603: Called econf '--disable-assert' '--disable-pcre' '--disable-rpath' '--without-included-libunistring' '--without-libunistring-prefix' '--disable-debug' '--disable-iri' '--enable-ipv6' '--enable-nls' '--disable-ntlm' '--enable-pcre2' '--enable-digest' '--enable-opie' '--without-libpsl' '--without-libidn' '--without-metalink' '--with-ssl=openssl' '--without-libuuid' '--with-zlib' |
| 30 |
* , line 681: Called __helpers_die 'econf failed' |
| 31 |
* isolated-functions.sh, line 112: Called die |
| 32 |
* The specific snippet of code: |
| 33 |
* |
| 34 |
* If you need support, post the output of `emerge --info '=net-misc/wget-1.20.3-r3::gentoo'`, |
| 35 |
* the complete build log and the output of `emerge -pqv '=net-misc/wget-1.20.3-r3::gentoo'`. |
| 36 |
* The complete build log is located at '/var/tmp/portage/net-misc/wget-1.20.3-r3/temp/build.log'. |
| 37 |
* The ebuild environment file is located at '/var/tmp/portage/net-misc/wget-1.20.3-r3/temp/environment'. |
| 38 |
* Working directory: '/var/tmp/portage/net-misc/wget-1.20.3-r3/work/wget-1.20.3' |
| 39 |
* S: '/var/tmp/portage/net-misc/wget-1.20.3-r3/work/wget-1.20.3' |
| 40 |
* Messages for package app-crypt/gnupg-2.2.20: |
| 41 |
* The ebuild phase 'configure' has exited unexpectedly. This type of |
| 42 |
* behavior is known to be triggered by things such as failed variable |
| 43 |
* assignments (bug #190128) or bad substitution errors (bug #200313). |
| 44 |
* Normally, before exiting, bash should have displayed an error message |
| 45 |
* above. If bash did not produce an error message above, it's possible |
| 46 |
* that the ebuild has called `exit` when it should have called `die` |
| 47 |
* instead. This behavior may also be triggered by a corrupt bash binary or |
| 48 |
* a hardware problem such as memory or cpu malfunction. If the problem is |
| 49 |
* not reproducible or it appears to occur randomly, then it is likely to |
| 50 |
* be triggered by a hardware problem. If you suspect a hardware problem |
| 51 |
* then you should try some basic hardware diagnostics such as memtest. |
| 52 |
* Please do not report this as a bug unless it is consistently |
| 53 |
* reproducible and you are sure that your bash binary and hardware are |
| 54 |
* functioning properly. |
| 55 |
* ERROR: app-crypt/gnupg-2.2.20::gentoo failed (configure phase): |
| 56 |
* econf failed |
| 57 |
* |
| 58 |
* Call stack: |
| 59 |
* , line 125: Called src_configure |
| 60 |
* , line 1638: Called econf '--enable-symcryptrun' '--enable-bzip2' '--enable-nls' '--enable-scdaemon' '--enable-gnutls' '--disable-tofu' '--disable-ccid-driver' '--disable-wks-tools' '--without-ldap' '--with-readline' '--with-mailprog=/usr/libexec/sendmail' '--disable-ntbtls' '--enable-all-tests' '--enable-gpg' '--enable-gpgsm' '--enable-large-secmem' 'CC_FOR_BUILD=i686-pc-linux-gnu-gcc' 'GPG_ERROR_CONFIG=/usr/bin/i686-pc-linux-gnu-gpg-error-config' 'KSBA_CONFIG=/usr/bin/ksba-config' 'LIBASSUAN_CONFIG=/usr/bin/libassuan-config' 'LIBGCRYPT_CONFIG=/usr/bin/i686-pc-linux-gnu-libgcrypt-config' 'NPTH_CONFIG=/usr/bin/npth-config' '--without-libiconv-prefix' '--without-libintl-prefix' |
| 61 |
* , line 681: Called __helpers_die 'econf failed' |
| 62 |
* isolated-functions.sh, line 112: Called die |
| 63 |
* The specific snippet of code: |
| 64 |
* |
| 65 |
* If you need support, post the output of `emerge --info '=app-crypt/gnupg-2.2.20::gentoo'`, |
| 66 |
* the complete build log and the output of `emerge -pqv '=app-crypt/gnupg-2.2.20::gentoo'`. |
| 67 |
* The complete build log is located at '/var/tmp/portage/app-crypt/gnupg-2.2.20/temp/build.log'. |
| 68 |
* The ebuild environment file is located at '/var/tmp/portage/app-crypt/gnupg-2.2.20/temp/environment'. |
| 69 |
* Working directory: '/var/tmp/portage/app-crypt/gnupg-2.2.20/work/gnupg-2.2.20' |
| 70 |
* S: '/var/tmp/portage/app-crypt/gnupg-2.2.20/work/gnupg-2.2.20' |
| 71 |
* Messages for package sys-apps/gawk-4.2.1-r1: |
| 72 |
* The ebuild phase 'configure' has exited unexpectedly. This type of |
| 73 |
* behavior is known to be triggered by things such as failed variable |
| 74 |
* assignments (bug #190128) or bad substitution errors (bug #200313). |
| 75 |
* Normally, before exiting, bash should have displayed an error message |
| 76 |
* above. If bash did not produce an error message above, it's possible |
| 77 |
* that the ebuild has called `exit` when it should have called `die` |
| 78 |
* instead. This behavior may also be triggered by a corrupt bash binary or |
| 79 |
* a hardware problem such as memory or cpu malfunction. If the problem is |
| 80 |
* not reproducible or it appears to occur randomly, then it is likely to |
| 81 |
* be triggered by a hardware problem. If you suspect a hardware problem |
| 82 |
* then you should try some basic hardware diagnostics such as memtest. |
| 83 |
* Please do not report this as a bug unless it is consistently |
| 84 |
* reproducible and you are sure that your bash binary and hardware are |
| 85 |
* functioning properly. |
| 86 |
* ERROR: sys-apps/gawk-4.2.1-r1::gentoo failed (configure phase): |
| 87 |
* econf failed |
| 88 |
* |
| 89 |
* Call stack: |
| 90 |
* , line 125: Called src_configure |
| 91 |
* , line 1056: Called econf '--libexec=$(libdir)/misc' '--without-mpfr' '--enable-nls' '--with-readline' |
| 92 |
* , line 681: Called __helpers_die 'econf failed' |
| 93 |
* isolated-functions.sh, line 112: Called die |
| 94 |
* The specific snippet of code: |
| 95 |
* |
| 96 |
* If you need support, post the output of `emerge --info '=sys-apps/gawk-4.2.1-r1::gentoo'`, |
| 97 |
* the complete build log and the output of `emerge -pqv '=sys-apps/gawk-4.2.1-r1::gentoo'`. |
| 98 |
* The complete build log is located at '/var/tmp/portage/sys-apps/gawk-4.2.1-r1/temp/build.log'. |
| 99 |
* The ebuild environment file is located at '/var/tmp/portage/sys-apps/gawk-4.2.1-r1/temp/environment'. |
| 100 |
* Working directory: '/var/tmp/portage/sys-apps/gawk-4.2.1-r1/work/gawk-4.2.1' |
| 101 |
* S: '/var/tmp/portage/sys-apps/gawk-4.2.1-r1/work/gawk-4.2.1' |
| 102 |
* Messages for package app-crypt/gnupg-2.2.20: |
| 103 |
* Messages for package sys-apps/gawk-4.2.1-r1: |
| 104 |
* Messages for package net-misc/wget-1.20.3-r3: |
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
|
| 109 |
|
| 110 |
|
| 111 |
|
| 112 |
|
| 113 |
|
| 114 |
|
| 115 |
|
| 116 |
|
| 117 |
|
| 118 |
|
| 119 |
* |
| 120 |
* The following 3 packages have failed to build, install, or execute |
| 121 |
* postinst: |
| 122 |
* |
| 123 |
* (app-crypt/gnupg-2.2.20:0/0::gentoo, ebuild scheduled for merge), Log file: |
| 124 |
* '/var/tmp/portage/app-crypt/gnupg-2.2.20/temp/build.log' |
| 125 |
* (sys-apps/gawk-4.2.1-r1:0/0::gentoo, ebuild scheduled for merge), Log file: |
| 126 |
* '/var/tmp/portage/sys-apps/gawk-4.2.1-r1/temp/build.log' |
| 127 |
* (net-misc/wget-1.20.3-r3:0/0::gentoo, ebuild scheduled for merge), Log file: |
| 128 |
* '/var/tmp/portage/net-misc/wget-1.20.3-r3/temp/build.log' |
| 129 |
* |
| 130 |
|
| 131 |
!!! existing preserved libs found |
| 132 |
25 May 2020 21:45:03 UTC: ERROR : CatalystError: cmd(['/usr/share/catalyst/targets/stage1/stage1-controller.sh', 'run']) exited 1 |
| 133 |
ERROR:catalyst:CatalystError: cmd(['/usr/share/catalyst/targets/stage1/stage1-controller.sh', 'run']) exited 1 |
| 134 |
25 May 2020 21:45:04 UTC: NOTICE : /release/buildroot/x86-dev/tmp/default/stage1-i686-systemd-20200525T185525Z/var/tmp/portage is not a mount point. Skipping |
| 135 |
NOTICE:catalyst:/release/buildroot/x86-dev/tmp/default/stage1-i686-systemd-20200525T185525Z/var/tmp/portage is not a mount point. Skipping |
| 136 |
25 May 2020 21:45:04 UTC: NOTICE : /release/buildroot/x86-dev/tmp/default/stage1-i686-systemd-20200525T185525Z/dev does not exist. Skipping |
| 137 |
NOTICE:catalyst:/release/buildroot/x86-dev/tmp/default/stage1-i686-systemd-20200525T185525Z/dev does not exist. Skipping |
| 138 |
25 May 2020 21:45:04 UTC: NOTICE : /release/buildroot/x86-dev/tmp/default/stage1-i686-systemd-20200525T185525Z/proc does not exist. Skipping |
| 139 |
NOTICE:catalyst:/release/buildroot/x86-dev/tmp/default/stage1-i686-systemd-20200525T185525Z/proc does not exist. Skipping |
| 140 |
25 May 2020 21:45:04 UTC: ERROR : CatalystError: Stage build aborting due to error. |
| 141 |
ERROR:catalyst:CatalystError: Stage build aborting due to error. |
| 142 |
25 May 2020 21:45:04 UTC: ERROR : Exception running action sequence run_local |
| 143 |
Traceback (most recent call last): |
| 144 |
File "/usr/lib64/python3.6/site-packages/catalyst/base/stagebase.py", line 1366, in run_local |
| 145 |
env=self.env) |
| 146 |
File "/usr/lib64/python3.6/site-packages/catalyst/support.py", line 54, in cmd |
| 147 |
print_traceback=False) |
| 148 |
catalyst.support.CatalystError: cmd(['/usr/share/catalyst/targets/stage1/stage1-controller.sh', 'run']) exited 1 |
| 149 |
|
| 150 |
During handling of the above exception, another exception occurred: |
| 151 |
|
| 152 |
Traceback (most recent call last): |
| 153 |
File "/usr/lib64/python3.6/site-packages/catalyst/base/stagebase.py", line 1471, in run |
| 154 |
getattr(self, x)() |
| 155 |
File "/usr/lib64/python3.6/site-packages/catalyst/base/stagebase.py", line 1375, in run_local |
| 156 |
print_traceback=False) |
| 157 |
catalyst.support.CatalystError: Stage build aborting due to error. |
| 158 |
ERROR:catalyst:Exception running action sequence run_local |
| 159 |
Traceback (most recent call last): |
| 160 |
File "/usr/lib64/python3.6/site-packages/catalyst/base/stagebase.py", line 1366, in run_local |
| 161 |
env=self.env) |
| 162 |
File "/usr/lib64/python3.6/site-packages/catalyst/support.py", line 54, in cmd |
| 163 |
print_traceback=False) |
| 164 |
catalyst.support.CatalystError: cmd(['/usr/share/catalyst/targets/stage1/stage1-controller.sh', 'run']) exited 1 |
| 165 |
|
| 166 |
During handling of the above exception, another exception occurred: |
| 167 |
|
| 168 |
Traceback (most recent call last): |
| 169 |
File "/usr/lib64/python3.6/site-packages/catalyst/base/stagebase.py", line 1471, in run |
| 170 |
getattr(self, x)() |
| 171 |
File "/usr/lib64/python3.6/site-packages/catalyst/base/stagebase.py", line 1375, in run_local |
| 172 |
print_traceback=False) |
| 173 |
catalyst.support.CatalystError: Stage build aborting due to error. |
| 174 |
25 May 2020 21:45:04 UTC: NOTICE : Cleaning up... Running unbind() |
| 175 |
NOTICE:catalyst:Cleaning up... Running unbind() |
| 176 |
25 May 2020 21:45:04 UTC: NOTICE : /release/buildroot/x86-dev/tmp/default/stage1-i686-systemd-20200525T185525Z/tmp/kerncache does not exist. Skipping |
| 177 |
NOTICE:catalyst:/release/buildroot/x86-dev/tmp/default/stage1-i686-systemd-20200525T185525Z/tmp/kerncache does not exist. Skipping |
| 178 |
25 May 2020 21:45:04 UTC: NOTICE : /release/buildroot/x86-dev/tmp/default/stage1-i686-systemd-20200525T185525Z/var/cache/binpkgs is not a mount point. Skipping |
| 179 |
NOTICE:catalyst:/release/buildroot/x86-dev/tmp/default/stage1-i686-systemd-20200525T185525Z/var/cache/binpkgs is not a mount point. Skipping |
| 180 |
25 May 2020 21:45:04 UTC: NOTICE : /release/buildroot/x86-dev/tmp/default/stage1-i686-systemd-20200525T185525Z/tmp/stage1root/proc does not exist. Skipping |
| 181 |
NOTICE:catalyst:/release/buildroot/x86-dev/tmp/default/stage1-i686-systemd-20200525T185525Z/tmp/stage1root/proc does not exist. Skipping |
| 182 |
25 May 2020 21:45:04 UTC: NOTICE : /release/buildroot/x86-dev/tmp/default/stage1-i686-systemd-20200525T185525Z/run does not exist. Skipping |
| 183 |
NOTICE:catalyst:/release/buildroot/x86-dev/tmp/default/stage1-i686-systemd-20200525T185525Z/run does not exist. Skipping |
| 184 |
25 May 2020 21:45:04 UTC: NOTICE : /release/buildroot/x86-dev/tmp/default/stage1-i686-systemd-20200525T185525Z/dev/shm does not exist. Skipping |
| 185 |
NOTICE:catalyst:/release/buildroot/x86-dev/tmp/default/stage1-i686-systemd-20200525T185525Z/dev/shm does not exist. Skipping |
| 186 |
25 May 2020 21:45:04 UTC: NOTICE : /release/buildroot/x86-dev/tmp/default/stage1-i686-systemd-20200525T185525Z/dev/pts does not exist. Skipping |
| 187 |
NOTICE:catalyst:/release/buildroot/x86-dev/tmp/default/stage1-i686-systemd-20200525T185525Z/dev/pts does not exist. Skipping |
| 188 |
25 May 2020 21:45:04 UTC: NOTICE : /release/buildroot/x86-dev/tmp/default/stage1-i686-systemd-20200525T185525Z/var/tmp/portage is not a mount point. Skipping |
| 189 |
NOTICE:catalyst:/release/buildroot/x86-dev/tmp/default/stage1-i686-systemd-20200525T185525Z/var/tmp/portage is not a mount point. Skipping |
| 190 |
25 May 2020 21:45:04 UTC: NOTICE : /release/buildroot/x86-dev/tmp/default/stage1-i686-systemd-20200525T185525Z/var/cache/distfiles is not a mount point. Skipping |
| 191 |
NOTICE:catalyst:/release/buildroot/x86-dev/tmp/default/stage1-i686-systemd-20200525T185525Z/var/cache/distfiles is not a mount point. Skipping |
| 192 |
25 May 2020 21:45:04 UTC: NOTICE : /release/buildroot/x86-dev/tmp/default/stage1-i686-systemd-20200525T185525Z/var/db/repos/gentoo is not a mount point. Skipping |
| 193 |
NOTICE:catalyst:/release/buildroot/x86-dev/tmp/default/stage1-i686-systemd-20200525T185525Z/var/db/repos/gentoo is not a mount point. Skipping |
| 194 |
25 May 2020 21:45:04 UTC: NOTICE : /release/buildroot/x86-dev/tmp/default/stage1-i686-systemd-20200525T185525Z/dev does not exist. Skipping |
| 195 |
NOTICE:catalyst:/release/buildroot/x86-dev/tmp/default/stage1-i686-systemd-20200525T185525Z/dev does not exist. Skipping |
| 196 |
25 May 2020 21:45:04 UTC: NOTICE : /release/buildroot/x86-dev/tmp/default/stage1-i686-systemd-20200525T185525Z/proc does not exist. Skipping |
| 197 |
NOTICE:catalyst:/release/buildroot/x86-dev/tmp/default/stage1-i686-systemd-20200525T185525Z/proc does not exist. Skipping |
| 198 |
Command exited with non-zero status 2 |
| 199 |
878.43user 351.26system 10:56.90elapsed 187%CPU (0avgtext+0avgdata 362956maxresident)k |
| 200 |
572024inputs+4239392outputs (1major+53699787minor)pagefaults 0swaps |
| 201 |
|
| 202 |
|
| 203 |
|
| 204 |
Full build log at /release/tmp/run/catalyst-auto.20200525T185525Z.NXwVsD/log/i686_stage1-systemd.log |
Archives