| 1 |
Catalyst, version 2.0.19 |
| 2 |
Copyright 2003-2008 Gentoo Foundation |
| 3 |
Copyright 2008-2012 various authors |
| 4 |
Distributed under the GNU General Public License version 2.1 |
| 5 |
|
| 6 |
Using command line specified Catalyst configuration file, /etc/catalyst/release/amd64-auto.conf |
| 7 |
Setting sharedir to config file value "/usr/lib64/catalyst/" |
| 8 |
Setting snapshot_cache to config file value "/release/tmp/snapshots" |
| 9 |
Setting hash_function to config file value "crc32" |
| 10 |
Setting storedir to config file value "/release/buildroot/amd64-dev" |
| 11 |
Setting portdir to config file value "/release/trees/portage-auto" |
| 12 |
Setting distdir to config file value "/release/tmp/distfiles/" |
| 13 |
Setting options to config file value "autoresume bindist pkgcache preserve_libs seedcache snapcache" |
| 14 |
Autoresuming support enabled. |
| 15 |
Binary redistribution enabled |
| 16 |
Package cache support enabled. |
| 17 |
Preserving libs during unmerge. |
| 18 |
Seed cache support enabled. |
| 19 |
Snapshot cache support enabled. |
| 20 |
Envscript support enabled. |
| 21 |
Using target: stage4 |
| 22 |
Building natively for amd64 |
| 23 |
Source path set to /release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened-latest.tar.bz2 |
| 24 |
Caching snapshot to /release/tmp/snapshots/20170928/ |
| 25 |
The autoresume path is /release/buildroot/amd64-dev/tmp/hardened/.autoresume-stage4-amd64-hardened+minimal-20170928/ |
| 26 |
Location of the package cache is /release/buildroot/amd64-dev/packages/hardened/stage4-amd64-hardened+minimal-20170928/ |
| 27 |
Checking for processes running in chroot and killing them. |
| 28 |
Removing AutoResume Points: ... |
| 29 |
Emptying directory /release/buildroot/amd64-dev/tmp/hardened/.autoresume-stage4-amd64-hardened+minimal-20170928/ |
| 30 |
>>> Waiting 10 seconds before starting... |
| 31 |
>>> (Control-C to abort)... |
| 32 |
Purging Caches ... in: 10 9 8 7 6 5 4 3 2 1 |
| 33 |
clearing autoresume ... |
| 34 |
Removing AutoResume Points: ... |
| 35 |
Emptying directory /release/buildroot/amd64-dev/tmp/hardened/.autoresume-stage4-amd64-hardened+minimal-20170928/ |
| 36 |
clearing chroot ... |
| 37 |
Emptying directory /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20170928/ |
| 38 |
clearing package cache ... |
| 39 |
purging the pkgcache ... |
| 40 |
clearing kerncache ... |
| 41 |
--- Running action sequence: unpack |
| 42 |
Referenced SEEDCACHE does not appear to be a directory, trying to untar... |
| 43 |
No Valid Resume point detected, cleaning up... |
| 44 |
Removing AutoResume Points: ... |
| 45 |
Emptying directory /release/buildroot/amd64-dev/tmp/hardened/.autoresume-stage4-amd64-hardened+minimal-20170928/ |
| 46 |
Emptying directory /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20170928/ |
| 47 |
|
| 48 |
Starting tar extract from /release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened-latest.tar.bz2 |
| 49 |
to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20170928/ (This may take some time) ... |
| 50 |
|
| 51 |
tar: SELinux support is not available |
| 52 |
--- Running action sequence: unpack_snapshot |
| 53 |
Valid snapshot cache, skipping unpack of portage tree... |
| 54 |
--- Running action sequence: config_profile_link |
| 55 |
Configuring profile link... |
| 56 |
--- Running action sequence: setup_confdir |
| 57 |
Configuring /etc/portage... |
| 58 |
--- Running action sequence: portage_overlay |
| 59 |
--- Running action sequence: bind |
| 60 |
--- Running action sequence: chroot_setup |
| 61 |
Setting up chroot... |
| 62 |
|
| 63 |
Warning!!!! |
| 64 |
Overriding certain env variables may cause catastrophic failure. |
| 65 |
If your build fails look here first as the possible problem. |
| 66 |
Catalyst assumes you know what you are doing when setting |
| 67 |
these variables. |
| 68 |
Catalyst Maintainers use VERY minimal envscripts if used at all |
| 69 |
You have been warned |
| 70 |
|
| 71 |
--- Running action sequence: setup_environment |
| 72 |
--- Running action sequence: build_packages |
| 73 |
Copying stage4-chroot.sh to /tmp |
| 74 |
copying stage4-chroot.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20170928//tmp |
| 75 |
copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20170928//tmp |
| 76 |
Ensure the file has the executable bit set |
| 77 |
Running stage4-chroot.sh in chroot /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20170928/ |
| 78 |
>>> Regenerating /etc/ld.so.cache... |
| 79 |
Updating portage with USE="" |
| 80 |
emerge --quiet --usepkg --buildpkg --newuse --oneshot --update --newuse sys-apps/portage |
| 81 |
|
| 82 |
Performing Global Updates |
| 83 |
(Could take a couple of minutes if you have a lot of binary packages.) |
| 84 |
|
| 85 |
|
| 86 |
>>> Verifying ebuild manifests |
| 87 |
>>> Emerging (1 of 1) sys-apps/portage-2.3.8::gentoo |
| 88 |
>>> Installing (1 of 1) sys-apps/portage-2.3.8::gentoo |
| 89 |
Bringing system up to date using profile specific use flags |
| 90 |
emerge --quiet --usepkg --buildpkg --newuse -u @system |
| 91 |
>>> Verifying ebuild manifests |
| 92 |
>>> Running pre-merge checks for sys-devel/gcc-5.4.0-r3 |
| 93 |
>>> Emerging (1 of 3) sys-apps/net-tools-1.60_p20161110235919::gentoo |
| 94 |
>>> Installing (1 of 3) sys-apps/net-tools-1.60_p20161110235919::gentoo |
| 95 |
>>> Emerging (2 of 3) sys-apps/file-5.32::gentoo |
| 96 |
>>> Installing (2 of 3) sys-apps/file-5.32::gentoo |
| 97 |
>>> Emerging (3 of 3) sys-devel/gcc-5.4.0-r3::gentoo |
| 98 |
* The ebuild phase 'compile' has exited unexpectedly. This type of |
| 99 |
* behavior is known to be triggered by things such as failed variable |
| 100 |
* assignments (bug #190128) or bad substitution errors (bug #200313). |
| 101 |
* Normally, before exiting, bash should have displayed an error message |
| 102 |
* above. If bash did not produce an error message above, it's possible |
| 103 |
* that the ebuild has called `exit` when it should have called `die` |
| 104 |
* instead. This behavior may also be triggered by a corrupt bash binary or |
| 105 |
* a hardware problem such as memory or cpu malfunction. If the problem is |
| 106 |
* not reproducible or it appears to occur randomly, then it is likely to |
| 107 |
* be triggered by a hardware problem. If you suspect a hardware problem |
| 108 |
* then you should try some basic hardware diagnostics such as memtest. |
| 109 |
* Please do not report this as a bug unless it is consistently |
| 110 |
* reproducible and you are sure that your bash binary and hardware are |
| 111 |
* functioning properly. |
| 112 |
* The ebuild phase 'die_hooks' has been aborted since PORTAGE_BUILDDIR |
| 113 |
* does not exist: '/var/tmp/portage/sys-devel/gcc-5.4.0-r3' |
| 114 |
* Messages for package sys-devel/gcc-5.4.0-r3: |
| 115 |
* The ebuild phase 'compile' has exited unexpectedly. This type of |
| 116 |
* behavior is known to be triggered by things such as failed variable |
| 117 |
* assignments (bug #190128) or bad substitution errors (bug #200313). |
| 118 |
* Normally, before exiting, bash should have displayed an error message |
| 119 |
* above. If bash did not produce an error message above, it's possible |
| 120 |
* that the ebuild has called `exit` when it should have called `die` |
| 121 |
* instead. This behavior may also be triggered by a corrupt bash binary or |
| 122 |
* a hardware problem such as memory or cpu malfunction. If the problem is |
| 123 |
* not reproducible or it appears to occur randomly, then it is likely to |
| 124 |
* be triggered by a hardware problem. If you suspect a hardware problem |
| 125 |
* then you should try some basic hardware diagnostics such as memtest. |
| 126 |
* Please do not report this as a bug unless it is consistently |
| 127 |
* reproducible and you are sure that your bash binary and hardware are |
| 128 |
* functioning properly. |
| 129 |
|
| 130 |
|
| 131 |
Traceback (most recent call last): |
| 132 |
File "/usr/lib/python-exec/python3.4/emerge", line 50, in <module> |
| 133 |
File "/usr/lib64/python3.4/site-packages/_emerge/main.py", line 1250, in emerge_main |
| 134 |
File "/usr/lib64/python3.4/site-packages/_emerge/actions.py", line 3297, in run_action |
| 135 |
File "/usr/lib64/python3.4/site-packages/_emerge/actions.py", line 540, in action_build |
| 136 |
File "/usr/lib64/python3.4/site-packages/_emerge/Scheduler.py", line 1039, in merge |
| 137 |
File "/usr/lib64/python3.4/site-packages/_emerge/Scheduler.py", line 1444, in _merge |
| 138 |
File "/usr/lib64/python3.4/site-packages/_emerge/Scheduler.py", line 1422, in _main_loop |
| 139 |
File "/usr/lib64/python3.4/site-packages/portage/util/_eventloop/EventLoop.py", line 263, in iteration |
| 140 |
File "/usr/lib64/python3.4/site-packages/portage/util/_eventloop/EventLoop.py", line 534, in _run_timeouts |
| 141 |
File "/usr/lib64/python3.4/site-packages/portage/util/_eventloop/EventLoop.py", line 496, in _run_idle_callbacks |
| 142 |
File "/usr/lib64/python3.4/site-packages/_emerge/AsynchronousTask.py", line 74, in _async_wait_cb |
| 143 |
File "/usr/lib64/python3.4/site-packages/_emerge/AsynchronousTask.py", line 57, in wait |
| 144 |
File "/usr/lib64/python3.4/site-packages/_emerge/AsynchronousTask.py", line 175, in _wait_hook |
| 145 |
File "/usr/lib64/python3.4/site-packages/_emerge/EbuildPhase.py", line 349, in _die_hooks_exit |
| 146 |
File "/usr/lib64/python3.4/site-packages/_emerge/AsynchronousTask.py", line 57, in wait |
| 147 |
File "/usr/lib64/python3.4/site-packages/_emerge/AsynchronousTask.py", line 175, in _wait_hook |
| 148 |
File "/usr/lib64/python3.4/site-packages/_emerge/TaskSequence.py", line 47, in _task_exit_handler |
| 149 |
File "/usr/lib64/python3.4/site-packages/_emerge/AsynchronousTask.py", line 57, in wait |
| 150 |
File "/usr/lib64/python3.4/site-packages/_emerge/AsynchronousTask.py", line 175, in _wait_hook |
| 151 |
File "/usr/lib64/python3.4/site-packages/_emerge/CompositeTask.py", line 134, in _default_final_exit |
| 152 |
File "/usr/lib64/python3.4/site-packages/_emerge/AsynchronousTask.py", line 57, in wait |
| 153 |
File "/usr/lib64/python3.4/site-packages/_emerge/AsynchronousTask.py", line 175, in _wait_hook |
| 154 |
File "/usr/lib64/python3.4/site-packages/_emerge/EbuildBuild.py", line 307, in _build_exit |
| 155 |
File "/usr/lib64/python3.4/site-packages/_emerge/EbuildBuild.py", line 302, in _unlock_builddir |
| 156 |
File "/usr/lib64/python3.4/site-packages/portage/elog/__init__.py", line 176, in elog_process |
| 157 |
File "/usr/lib64/python3.4/site-packages/portage/elog/mod_save_summary.py", line 37, in process |
| 158 |
File "/usr/lib64/python3.4/site-packages/portage/util/__init__.py", line 1425, in ensure_dirs |
| 159 |
File "/usr/lib64/python3.4/site-packages/portage/__init__.py", line 250, in __call__ |
| 160 |
File "/usr/lib64/python3.4/os.py", line 227, in makedirs |
| 161 |
File "/usr/lib64/python3.4/os.py", line 227, in makedirs |
| 162 |
File "/usr/lib64/python3.4/os.py", line 237, in makedirs |
| 163 |
FileNotFoundError: [Errno 2] No such file or directory: b'/var' |
| 164 |
emergelog(): [Errno 2] No such file or directory: b'/var/log/emerge.log' |
| 165 |
|
| 166 |
!!! catalyst: Error in attempt to build packages |
| 167 |
|
| 168 |
|
| 169 |
Traceback (most recent call last): |
| 170 |
File "modules/generic_stage_target.py", line 1432, in build_packages |
| 171 |
"Error in attempt to build packages",env=self.env) |
| 172 |
File "/usr/lib64/catalyst//modules/catalyst_support.py", line 541, in cmd |
| 173 |
raise CatalystError,myexc |
| 174 |
CatalystError |
| 175 |
None |
| 176 |
|
| 177 |
!!! catalyst: stage4build aborting due to error. |
| 178 |
|
| 179 |
Traceback (most recent call last): |
| 180 |
File "/usr/lib64/catalyst/catalyst", line 218, in build_target |
| 181 |
mytarget.run() |
| 182 |
File "modules/generic_stage_target.py", line 1333, in run |
| 183 |
apply(getattr(self,x)) |
| 184 |
File "modules/generic_stage_target.py", line 1437, in build_packages |
| 185 |
"build aborting due to error." |
| 186 |
CatalystError |
| 187 |
!!! catalyst: Error encountered during run of target stage4 |
| 188 |
Catalyst aborting.... |
| 189 |
lockfile does not exist '/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20170928/.catalyst_lock' |
| 190 |
Command exited with non-zero status 1 |
| 191 |
5768.95user 515.27system 1:53:42elapsed 92%CPU (0avgtext+0avgdata 3223168maxresident)k |
| 192 |
6008inputs+8753400outputs (20major+121026937minor)pagefaults 0swaps |
| 193 |
|
| 194 |
|
| 195 |
|
| 196 |
Full build log at /release/tmp/run/catalyst-auto.20170928.r9Ro52/log/hardened_stage4-minimal.log |
Archives