| 1 |
*** Running command: time catalyst -a -c /etc/catalyst/release/amd64-auto.conf -f hardened/stage2-selinux.spec |
| 2 |
02 Jan 2019 18:41:17 UTC: NOTICE : Loading configuration file: /etc/catalyst/release/amd64-auto.conf |
| 3 |
02 Jan 2019 18:41:17 UTC: NOTICE : conf_values[options] = {'clear-autoresume', 'autoresume', 'preserve_libs', 'pkgcache', 'snapcache', 'bindist', 'seedcache'} |
| 4 |
02 Jan 2019 18:41:17 UTC: NOTICE : Processing spec file: hardened/stage2-selinux.spec |
| 5 |
02 Jan 2019 18:41:18 UTC: NOTICE : Using target: stage2 |
| 6 |
02 Jan 2019 18:41:18 UTC: NOTICE : Source file specification matching setting is: loose |
| 7 |
02 Jan 2019 18:41:18 UTC: NOTICE : Accepted source file extensions search order: ['tar', 'tar.xz', 'tpxz', 'xz', 'tar.bz2', 'bz2', 'tbz2', 'tar.gz', 'gz'] |
| 8 |
02 Jan 2019 18:41:18 UTC: NOTICE : Source path set to /release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux-20190101T214502Z/ |
| 9 |
02 Jan 2019 18:41:18 UTC: NOTICE : Removing AutoResume Points ... |
| 10 |
02 Jan 2019 18:41:18 UTC: NOTICE : Emptying directory: /release/buildroot/amd64-dev/tmp/hardened/.autoresume-stage2-amd64-hardened-selinux-20190101T214502Z |
| 11 |
02 Jan 2019 18:41:18 UTC: NOTICE : --- Running action sequence: unpack |
| 12 |
02 Jan 2019 18:41:18 UTC: NOTICE : Resume: "seed source" unpack resume point is disabled |
| 13 |
02 Jan 2019 18:41:18 UTC: NOTICE : Resume: Target chroot is invalid, cleaning up... |
| 14 |
02 Jan 2019 18:41:18 UTC: NOTICE : Removing AutoResume Points ... |
| 15 |
02 Jan 2019 18:41:18 UTC: NOTICE : Emptying directory: /release/buildroot/amd64-dev/tmp/hardened/.autoresume-stage2-amd64-hardened-selinux-20190101T214502Z |
| 16 |
02 Jan 2019 18:41:18 UTC: NOTICE : Clearing the chroot path ... |
| 17 |
02 Jan 2019 18:41:18 UTC: NOTICE : Emptying directory: /release/buildroot/amd64-dev/tmp/hardened/stage2-amd64-hardened-selinux-20190101T214502Z |
| 18 |
02 Jan 2019 18:41:18 UTC: NOTICE : Starting rsync from /release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux-20190101T214502Z/ |
| 19 |
02 Jan 2019 18:41:18 UTC: NOTICE : to /release/buildroot/amd64-dev/tmp/hardened/stage2-amd64-hardened-selinux-20190101T214502Z (this may take some time) .. |
| 20 |
02 Jan 2019 18:41:22 UTC: NOTICE : --- Running action sequence: unpack_snapshot |
| 21 |
02 Jan 2019 18:41:22 UTC: NOTICE : --- Running action sequence: setup_confdir |
| 22 |
02 Jan 2019 18:41:22 UTC: NOTICE : --- Running action sequence: portage_overlay |
| 23 |
02 Jan 2019 18:41:22 UTC: NOTICE : --- Running action sequence: base_dirs |
| 24 |
02 Jan 2019 18:41:22 UTC: NOTICE : --- Running action sequence: bind |
| 25 |
02 Jan 2019 18:41:22 UTC: NOTICE : --- Running action sequence: chroot_setup |
| 26 |
02 Jan 2019 18:41:22 UTC: NOTICE : Setting up chroot... |
| 27 |
02 Jan 2019 18:41:22 UTC: WARNING : Overriding certain env variables may cause catastrophic failure. |
| 28 |
02 Jan 2019 18:41:22 UTC: WARNING : If your build fails look here first as the possible problem. |
| 29 |
02 Jan 2019 18:41:22 UTC: WARNING : Catalyst assumes you know what you are doing when setting these variables. |
| 30 |
02 Jan 2019 18:41:22 UTC: WARNING : Catalyst Maintainers use VERY minimal envscripts, if used at all. |
| 31 |
02 Jan 2019 18:41:22 UTC: WARNING : You have been warned. |
| 32 |
02 Jan 2019 18:41:22 UTC: NOTICE : Writing the stage make.conf to: /release/buildroot/amd64-dev/tmp/hardened/stage2-amd64-hardened-selinux-20190101T214502Z/etc/portage/make.conf |
| 33 |
02 Jan 2019 18:41:22 UTC: NOTICE : STICKY-CONFIG is enabled |
| 34 |
02 Jan 2019 18:41:22 UTC: NOTICE : --- Running action sequence: setup_environment |
| 35 |
02 Jan 2019 18:41:22 UTC: NOTICE : --- Running action sequence: run_local |
| 36 |
Copying stage2-chroot.sh to /tmp |
| 37 |
copying stage2-chroot.sh to /release/buildroot/amd64-dev/tmp/hardened/stage2-amd64-hardened-selinux-20190101T214502Z/tmp |
| 38 |
copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/hardened/stage2-amd64-hardened-selinux-20190101T214502Z/tmp |
| 39 |
Ensure the file has the executable bit set |
| 40 |
Running stage2-chroot.sh in chroot: |
| 41 |
chroot /release/buildroot/amd64-dev/tmp/hardened/stage2-amd64-hardened-selinux-20190101T214502Z /tmp/stage2-chroot.sh |
| 42 |
>>> Regenerating /etc/ld.so.cache... |
| 43 |
|
| 44 |
Gentoo Linux; http://www.gentoo.org/ |
| 45 |
Copyright 1999-$ Gentoo Foundation; Distributed under the GPLv2 |
| 46 |
------------------------------------------------------------------------------- |
| 47 |
[[ (0/3) Locating packages ]] |
| 48 |
* Using baselayout : >=sys-apps/baselayout-2 |
| 49 |
* Using portage : portage |
| 50 |
* Using os-headers : >=sys-kernel/linux-headers-4.14-r1 |
| 51 |
* Using binutils : sys-devel/binutils |
| 52 |
* Using gcc : sys-devel/gcc |
| 53 |
* Using gettext : gettext |
| 54 |
* Using libc : virtual/libc |
| 55 |
* Using texinfo : sys-apps/texinfo |
| 56 |
* Using zlib : zlib |
| 57 |
* Using ncurses : ncurses |
| 58 |
------------------------------------------------------------------------------- |
| 59 |
[[ (1/3) Configuring environment ]] |
| 60 |
------------------------------------------------------------------------------- |
| 61 |
[[ (2/3) Updating portage ]] |
| 62 |
|
| 63 |
Performing Global Updates |
| 64 |
(Could take a couple of minutes if you have a lot of binary packages.) |
| 65 |
|
| 66 |
|
| 67 |
>>> Verifying ebuild manifests |
| 68 |
>>> Emerging (1 of 1) sys-apps/portage-2.3.51-r1::gentoo |
| 69 |
>>> Installing (1 of 1) sys-apps/portage-2.3.51-r1::gentoo |
| 70 |
|
| 71 |
* Messages for package sys-apps/portage-2.3.51-r1: |
| 72 |
|
| 73 |
* Could not find a UTF-8 locale. This may trigger build failures in |
| 74 |
* some python packages. Please ensure that a UTF-8 locale is listed in |
| 75 |
* /etc/locale.gen and run locale-gen. |
| 76 |
------------------------------------------------------------------------------- |
| 77 |
[[ (3/3) Emerging packages ]] |
| 78 |
>>> Verifying ebuild manifests |
| 79 |
>>> Running pre-merge checks for sys-devel/gcc-7.3.0-r3 |
| 80 |
>>> Emerging binary (1 of 13) sys-libs/zlib-1.2.11-r2::gentoo |
| 81 |
>>> Installing (1 of 13) sys-libs/zlib-1.2.11-r2::gentoo |
| 82 |
>>> Emerging binary (2 of 13) sys-apps/baselayout-2.6-r1::gentoo |
| 83 |
>>> Installing (2 of 13) sys-apps/baselayout-2.6-r1::gentoo |
| 84 |
>>> Emerging binary (3 of 13) sys-kernel/linux-headers-4.14-r1::gentoo |
| 85 |
>>> Installing (3 of 13) sys-kernel/linux-headers-4.14-r1::gentoo |
| 86 |
>>> Emerging binary (4 of 13) app-portage/elt-patches-20170815::gentoo |
| 87 |
>>> Installing (4 of 13) app-portage/elt-patches-20170815::gentoo |
| 88 |
>>> Emerging binary (5 of 13) sys-devel/binutils-2.30-r4::gentoo |
| 89 |
>>> Installing (5 of 13) sys-devel/binutils-2.30-r4::gentoo |
| 90 |
>>> Emerging binary (6 of 13) sys-devel/gettext-0.19.8.1::gentoo |
| 91 |
>>> Installing (6 of 13) sys-devel/gettext-0.19.8.1::gentoo |
| 92 |
>>> Emerging binary (7 of 13) virtual/libc-1::gentoo |
| 93 |
>>> Installing (7 of 13) virtual/libc-1::gentoo |
| 94 |
>>> Emerging (8 of 13) sys-devel/gcc-7.3.0-r3::gentoo |
| 95 |
>>> Emerging binary (9 of 13) dev-perl/Text-Unidecode-1.300.0::gentoo |
| 96 |
>>> Installing (9 of 13) dev-perl/Text-Unidecode-1.300.0::gentoo |
| 97 |
>>> Emerging binary (10 of 13) dev-perl/libintl-perl-1.280.0::gentoo |
| 98 |
>>> Failed to emerge sys-devel/gcc-7.3.0-r3 |
| 99 |
>>> Installing (10 of 13) dev-perl/libintl-perl-1.280.0::gentoo |
| 100 |
|
| 101 |
* Messages for package sys-apps/baselayout-2.6-r1: |
| 102 |
|
| 103 |
* The following users have non-existent shells! |
| 104 |
* halt - /sbin/halt |
| 105 |
* shutdown - /sbin/shutdown |
| 106 |
* You should reboot now to get /run mounted with tmpfs! |
| 107 |
|
| 108 |
* Messages for package sys-devel/gcc-7.3.0-r3: |
| 109 |
|
| 110 |
* The ebuild phase 'unpack' has exited unexpectedly. This type of behavior |
| 111 |
* is known to be triggered by things such as failed variable assignments |
| 112 |
* (bug #190128) or bad substitution errors (bug #200313). Normally, before |
| 113 |
* exiting, bash should have displayed an error message above. If bash did |
| 114 |
* not produce an error message above, it's possible that the ebuild has |
| 115 |
* called `exit` when it should have called `die` instead. This behavior |
| 116 |
* may also be triggered by a corrupt bash binary or a hardware problem |
| 117 |
* such as memory or cpu malfunction. If the problem is not reproducible or |
| 118 |
* it appears to occur randomly, then it is likely to be triggered by a |
| 119 |
* hardware problem. If you suspect a hardware problem then you should try |
| 120 |
* some basic hardware diagnostics such as memtest. Please do not report |
| 121 |
* this as a bug unless it is consistently reproducible and you are sure |
| 122 |
* that your bash binary and hardware are functioning properly. |
| 123 |
02 Jan 2019 18:43:38 UTC: ERROR : CatalystError: cmd(['/usr/share/catalyst/targets/stage2/stage2-controller.sh', 'run']) exited 1 |
| 124 |
02 Jan 2019 18:43:38 UTC: ERROR : CatalystError: Stage build aborting due to error. |
| 125 |
02 Jan 2019 18:43:38 UTC: ERROR : Exception running action sequence run_local |
| 126 |
Traceback (most recent call last): |
| 127 |
File "/usr/lib64/python3.6/site-packages/catalyst/base/stagebase.py", line 1355, in run_local |
| 128 |
env=self.env) |
| 129 |
File "/usr/lib64/python3.6/site-packages/catalyst/support.py", line 54, in cmd |
| 130 |
print_traceback=False) |
| 131 |
catalyst.support.CatalystError: cmd(['/usr/share/catalyst/targets/stage2/stage2-controller.sh', 'run']) exited 1 |
| 132 |
|
| 133 |
During handling of the above exception, another exception occurred: |
| 134 |
|
| 135 |
Traceback (most recent call last): |
| 136 |
File "/usr/lib64/python3.6/site-packages/catalyst/base/stagebase.py", line 1460, in run |
| 137 |
getattr(self, x)() |
| 138 |
File "/usr/lib64/python3.6/site-packages/catalyst/base/stagebase.py", line 1364, in run_local |
| 139 |
print_traceback=False) |
| 140 |
catalyst.support.CatalystError: Stage build aborting due to error. |
| 141 |
02 Jan 2019 18:43:38 UTC: NOTICE : Cleaning up... Running unbind() |
| 142 |
Command exited with non-zero status 2 |
| 143 |
77.58user 36.22system 2:21.59elapsed 80%CPU (0avgtext+0avgdata 70620maxresident)k |
| 144 |
80inputs+2787664outputs (0major+3665026minor)pagefaults 0swaps |
| 145 |
|
| 146 |
|
| 147 |
|
| 148 |
Full build log at /release/tmp/run/catalyst-auto.20190101T214502Z.9qoH9V/log/hardened_stage2-selinux.log |
Archives