| 1 |
02 Mar 2017 03:39:50 UTC: NOTICE : Loading configuration file: /etc/catalyst/release/amd64-auto.conf |
| 2 |
02 Mar 2017 03:39:50 UTC: NOTICE : Processing spec file: hardened/stage1-nomultilib.spec |
| 3 |
02 Mar 2017 03:39:51 UTC: NOTICE : Using target: stage1 |
| 4 |
02 Mar 2017 03:39:51 UTC: NOTICE : Source file specification matching setting is: loose |
| 5 |
02 Mar 2017 03:39:51 UTC: NOTICE : Accepted source file extensions search order: ['tar', 'tar.xz', 'tpxz', 'xz', 'tar.bz2', 'bz2', 'tbz2', 'tar.gz', 'gz'] |
| 6 |
02 Mar 2017 03:40:09 UTC: NOTICE : Source path set to /home/release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened+nomultilib-latest.tar.xz |
| 7 |
02 Mar 2017 03:40:09 UTC: NOTICE : stage1 stage path is /home/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened+nomultilib-20170301/tmp/stage1root |
| 8 |
>>> Waiting 10 seconds before starting... |
| 9 |
>>> (Control-C to abort)... |
| 10 |
Purging Caches ... in: 10 9 8 7 6 5 4 3 2 1 |
| 11 |
02 Mar 2017 03:40:23 UTC: NOTICE : purge(); clearing autoresume ... |
| 12 |
02 Mar 2017 03:40:23 UTC: NOTICE : purge(); clearing chroot ... |
| 13 |
02 Mar 2017 03:40:23 UTC: NOTICE : Clearing the chroot path ... |
| 14 |
02 Mar 2017 03:40:23 UTC: NOTICE : purge(); clearing package cache ... |
| 15 |
02 Mar 2017 03:40:23 UTC: NOTICE : purging the pkgcache ... |
| 16 |
02 Mar 2017 03:40:23 UTC: NOTICE : purge(); clearing kerncache ... |
| 17 |
02 Mar 2017 03:40:23 UTC: NOTICE : --- Running action sequence: unpack |
| 18 |
02 Mar 2017 03:40:23 UTC: NOTICE : Clearing the chroot path ... |
| 19 |
02 Mar 2017 03:40:23 UTC: NOTICE : Starting auto from /home/release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened+nomultilib-latest.tar.xz |
| 20 |
02 Mar 2017 03:40:23 UTC: NOTICE : to /home/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened+nomultilib-20170301 (this may take some time) .. |
| 21 |
02 Mar 2017 03:40:34 UTC: NOTICE : --- Running action sequence: unpack_snapshot |
| 22 |
02 Mar 2017 03:40:34 UTC: NOTICE : Unpacking portage tree (this can take a long time) ... |
| 23 |
02 Mar 2017 03:41:08 UTC: NOTICE : --- Running action sequence: setup_confdir |
| 24 |
02 Mar 2017 03:41:08 UTC: NOTICE : --- Running action sequence: portage_overlay |
| 25 |
02 Mar 2017 03:41:08 UTC: NOTICE : --- Running action sequence: base_dirs |
| 26 |
02 Mar 2017 03:41:08 UTC: NOTICE : --- Running action sequence: bind |
| 27 |
02 Mar 2017 03:41:08 UTC: NOTICE : --- Running action sequence: chroot_setup |
| 28 |
02 Mar 2017 03:41:08 UTC: NOTICE : Setting up chroot... |
| 29 |
02 Mar 2017 03:41:08 UTC: WARNING : Overriding certain env variables may cause catastrophic failure. |
| 30 |
02 Mar 2017 03:41:08 UTC: WARNING : If your build fails look here first as the possible problem. |
| 31 |
02 Mar 2017 03:41:08 UTC: WARNING : Catalyst assumes you know what you are doing when setting these variables. |
| 32 |
02 Mar 2017 03:41:08 UTC: WARNING : Catalyst Maintainers use VERY minimal envscripts, if used at all. |
| 33 |
02 Mar 2017 03:41:08 UTC: WARNING : You have been warned. |
| 34 |
02 Mar 2017 03:41:08 UTC: NOTICE : --- Running action sequence: setup_environment |
| 35 |
02 Mar 2017 03:41:08 UTC: NOTICE : --- Running action sequence: run_local |
| 36 |
copying make.conf to /home/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened+nomultilib-20170301/tmp/stage1root/etc/portage |
| 37 |
sed: -e expression #1, char 25: unterminated `s' command |
| 38 |
Copying stage1-chroot.sh to /tmp |
| 39 |
copying stage1-chroot.sh to /home/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened+nomultilib-20170301/tmp |
| 40 |
copying chroot-functions.sh to /home/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened+nomultilib-20170301/tmp |
| 41 |
Ensure the file has the executable bit set |
| 42 |
Running stage1-chroot.sh in chroot: |
| 43 |
chroot /home/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened+nomultilib-20170301 /tmp/stage1-chroot.sh |
| 44 |
>>> Regenerating /etc/ld.so.cache... |
| 45 |
Adding USE="${USE} build" to make.conf for portage build |
| 46 |
emerge --quiet --oneshot --update --newuse sys-apps/portage |
| 47 |
|
| 48 |
Performing Global Updates |
| 49 |
(Could take a couple of minutes if you have a lot of binary packages.) |
| 50 |
|
| 51 |
|
| 52 |
|
| 53 |
The following packages are causing rebuilds: |
| 54 |
|
| 55 |
(sys-libs/ncurses-6.0-r1:0/6::gentoo, ebuild scheduled for merge) causes rebuilds for: |
| 56 |
(sys-devel/gettext-0.19.7:0/0::gentoo, ebuild scheduled for merge) |
| 57 |
(sys-apps/openrc-0.23.2:0/0::gentoo, ebuild scheduled for merge) |
| 58 |
(app-editors/nano-2.6.3:0/0::gentoo, ebuild scheduled for merge) |
| 59 |
(sys-apps/less-487:0/0::gentoo, ebuild scheduled for merge) |
| 60 |
(app-shells/bash-4.3_p48-r1:0/0::gentoo, ebuild scheduled for merge) |
| 61 |
(sys-apps/util-linux-2.28.2:0/0::gentoo, ebuild scheduled for merge) |
| 62 |
>>> Verifying ebuild manifests |
| 63 |
>>> Emerging (1 of 13) sys-libs/ncurses-6.0-r1::gentoo |
| 64 |
* The ebuild phase 'configure' has exited unexpectedly. This type of |
| 65 |
* behavior is known to be triggered by things such as failed variable |
| 66 |
* assignments (bug #190128) or bad substitution errors (bug #200313). |
| 67 |
* Normally, before exiting, bash should have displayed an error message |
| 68 |
* above. If bash did not produce an error message above, it's possible |
| 69 |
* that the ebuild has called `exit` when it should have called `die` |
| 70 |
* instead. This behavior may also be triggered by a corrupt bash binary or |
| 71 |
* a hardware problem such as memory or cpu malfunction. If the problem is |
| 72 |
* not reproducible or it appears to occur randomly, then it is likely to |
| 73 |
* be triggered by a hardware problem. If you suspect a hardware problem |
| 74 |
* then you should try some basic hardware diagnostics such as memtest. |
| 75 |
* Please do not report this as a bug unless it is consistently |
| 76 |
* reproducible and you are sure that your bash binary and hardware are |
| 77 |
* functioning properly. |
| 78 |
* The ebuild phase 'die_hooks' has been aborted since PORTAGE_BUILDDIR |
| 79 |
* does not exist: '/var/tmp/portage/sys-libs/ncurses-6.0-r1' |
| 80 |
* Messages for package sys-libs/ncurses-6.0-r1: |
| 81 |
* The ebuild phase 'configure' has exited unexpectedly. This type of |
| 82 |
* behavior is known to be triggered by things such as failed variable |
| 83 |
* assignments (bug #190128) or bad substitution errors (bug #200313). |
| 84 |
* Normally, before exiting, bash should have displayed an error message |
| 85 |
* above. If bash did not produce an error message above, it's possible |
| 86 |
* that the ebuild has called `exit` when it should have called `die` |
| 87 |
* instead. This behavior may also be triggered by a corrupt bash binary or |
| 88 |
* a hardware problem such as memory or cpu malfunction. If the problem is |
| 89 |
* not reproducible or it appears to occur randomly, then it is likely to |
| 90 |
* be triggered by a hardware problem. If you suspect a hardware problem |
| 91 |
* then you should try some basic hardware diagnostics such as memtest. |
| 92 |
* Please do not report this as a bug unless it is consistently |
| 93 |
* reproducible and you are sure that your bash binary and hardware are |
| 94 |
* functioning properly. |
| 95 |
|
| 96 |
|
| 97 |
Traceback (most recent call last): |
| 98 |
File "/usr/lib/python-exec/python3.4/emerge", line 50, in <module> |
| 99 |
File "/usr/lib64/python3.4/site-packages/_emerge/main.py", line 1185, in emerge_main |
| 100 |
File "/usr/lib64/python3.4/site-packages/_emerge/actions.py", line 3236, in run_action |
| 101 |
File "/usr/lib64/python3.4/site-packages/_emerge/actions.py", line 505, in action_build |
| 102 |
File "/usr/lib64/python3.4/site-packages/_emerge/Scheduler.py", line 1032, in merge |
| 103 |
File "/usr/lib64/python3.4/site-packages/_emerge/Scheduler.py", line 1434, in _merge |
| 104 |
File "/usr/lib64/python3.4/site-packages/_emerge/Scheduler.py", line 1405, in _main_loop |
| 105 |
File "/usr/lib64/python3.4/site-packages/portage/util/_eventloop/EventLoop.py", line 204, in iteration |
| 106 |
File "/usr/lib64/python3.4/site-packages/portage/util/_eventloop/EventLoop.py", line 468, in _run_timeouts |
| 107 |
File "/usr/lib64/python3.4/site-packages/portage/util/_eventloop/EventLoop.py", line 430, in _run_idle_callbacks |
| 108 |
File "/usr/lib64/python3.4/site-packages/_emerge/AsynchronousTask.py", line 74, in _async_wait_cb |
| 109 |
File "/usr/lib64/python3.4/site-packages/_emerge/AsynchronousTask.py", line 57, in wait |
| 110 |
File "/usr/lib64/python3.4/site-packages/_emerge/AsynchronousTask.py", line 175, in _wait_hook |
| 111 |
File "/usr/lib64/python3.4/site-packages/_emerge/EbuildPhase.py", line 345, in _die_hooks_exit |
| 112 |
File "/usr/lib64/python3.4/site-packages/_emerge/AsynchronousTask.py", line 57, in wait |
| 113 |
File "/usr/lib64/python3.4/site-packages/_emerge/AsynchronousTask.py", line 175, in _wait_hook |
| 114 |
File "/usr/lib64/python3.4/site-packages/_emerge/TaskSequence.py", line 47, in _task_exit_handler |
| 115 |
File "/usr/lib64/python3.4/site-packages/_emerge/AsynchronousTask.py", line 57, in wait |
| 116 |
File "/usr/lib64/python3.4/site-packages/_emerge/AsynchronousTask.py", line 175, in _wait_hook |
| 117 |
File "/usr/lib64/python3.4/site-packages/_emerge/CompositeTask.py", line 134, in _default_final_exit |
| 118 |
File "/usr/lib64/python3.4/site-packages/_emerge/AsynchronousTask.py", line 57, in wait |
| 119 |
File "/usr/lib64/python3.4/site-packages/_emerge/AsynchronousTask.py", line 175, in _wait_hook |
| 120 |
File "/usr/lib64/python3.4/site-packages/_emerge/EbuildBuild.py", line 297, in _build_exit |
| 121 |
File "/usr/lib64/python3.4/site-packages/_emerge/EbuildBuild.py", line 293, in _unlock_builddir |
| 122 |
File "/usr/lib64/python3.4/site-packages/_emerge/EbuildBuildDir.py", line 96, in unlock |
| 123 |
File "/usr/lib64/python3.4/site-packages/_emerge/AsynchronousTask.py", line 30, in start |
| 124 |
File "/usr/lib64/python3.4/site-packages/_emerge/AsynchronousLock.py", line 47, in _start |
| 125 |
File "/usr/lib64/python3.4/site-packages/portage/locks.py", line 102, in lockfile |
| 126 |
portage.exception.DirectoryNotFound: /var/tmp/portage |
| 127 |
emergelog(): [Errno 2] No such file or directory: b'/var/log/emerge.log' |
| 128 |
Error in atexit._run_exitfuncs: |
| 129 |
Traceback (most recent call last): |
| 130 |
File "/usr/lib64/python3.4/site-packages/portage/process.py", line 164, in run_exitfuncs |
| 131 |
File "/usr/lib64/python3.4/site-packages/portage/__init__.py", line 259, in __call__ |
| 132 |
File "/usr/lib64/python3.4/shutil.py", line 455, in rmtree |
| 133 |
File "/usr/lib64/python3.4/shutil.py", line 453, in rmtree |
| 134 |
FileNotFoundError: [Errno 2] No such file or directory: '/var/tmp/portage/._portage_reinstall_.sml1f8oi' |
| 135 |
02 Mar 2017 03:42:06 UTC: ERROR : CatalystError: cmd(['/usr/share/catalyst/targets/stage1/stage1-controller.sh', 'run']) exited 1 |
| 136 |
02 Mar 2017 03:42:06 UTC: ERROR : CatalystError: Stage build aborting due to error. |
| 137 |
02 Mar 2017 03:42:06 UTC: ERROR : Exception running action sequence run_local |
| 138 |
Traceback (most recent call last): |
| 139 |
File "/usr/lib64/python3.4/site-packages/catalyst/base/stagebase.py", line 1316, in run_local |
| 140 |
env=self.env) |
| 141 |
File "/usr/lib64/python3.4/site-packages/catalyst/support.py", line 54, in cmd |
| 142 |
print_traceback=False) |
| 143 |
catalyst.support.CatalystError: cmd(['/usr/share/catalyst/targets/stage1/stage1-controller.sh', 'run']) exited 1 |
| 144 |
|
| 145 |
During handling of the above exception, another exception occurred: |
| 146 |
|
| 147 |
Traceback (most recent call last): |
| 148 |
File "/usr/lib64/python3.4/site-packages/catalyst/base/stagebase.py", line 1416, in run |
| 149 |
getattr(self, x)() |
| 150 |
File "/usr/lib64/python3.4/site-packages/catalyst/base/stagebase.py", line 1325, in run_local |
| 151 |
print_traceback=False) |
| 152 |
catalyst.support.CatalystError: Stage build aborting due to error. |
| 153 |
02 Mar 2017 03:42:06 UTC: NOTICE : Cleaning up... Running unbind() |
| 154 |
Command exited with non-zero status 2 |
| 155 |
34.95user 7.76system 2:16.24elapsed 31%CPU (0avgtext+0avgdata 361832maxresident)k |
| 156 |
345408inputs+3206560outputs (0major+491143minor)pagefaults 0swaps |
| 157 |
|
| 158 |
|
| 159 |
|
| 160 |
Full build log at /home/release/tmp/run/catalyst-auto.20170301.cXOIkx/log/hardened_stage1-nomultilib.log |
Archives