| 1 |
Checking for processes running in chroot and killing them. |
| 2 |
Removing AutoResume Points: ... |
| 3 |
Emptying directory /var/tmp/catalyst/tmp/default/.autoresume-stage1-s390-20180110T081028Z/ |
| 4 |
--- Running action sequence: unpack |
| 5 |
Referenced SEEDCACHE does not appear to be a directory, trying to untar... |
| 6 |
No Valid Resume point detected, cleaning up... |
| 7 |
Removing AutoResume Points: ... |
| 8 |
Emptying directory /var/tmp/catalyst/tmp/default/.autoresume-stage1-s390-20180110T081028Z/ |
| 9 |
Emptying directory /var/tmp/catalyst/tmp/default/stage1-s390-20180110T081028Z/ |
| 10 |
|
| 11 |
Starting tar extract from /var/tmp/catalyst/builds/default/stage3-s390-latest.tar.bz2 |
| 12 |
to /var/tmp/catalyst/tmp/default/stage1-s390-20180110T081028Z/ (This may take some time) ... |
| 13 |
|
| 14 |
tar: SELinux support is not available |
| 15 |
--- Running action sequence: unpack_snapshot |
| 16 |
Cleaning up invalid snapshot cache at |
| 17 |
/var/tmp/catalyst/snapshot_cache/20180110T081028Z/ (This can take a long time)... |
| 18 |
Unpacking portage tree (This can take a long time) ... |
| 19 |
tar: SELinux support is not available |
| 20 |
lockfile does not exist '/var/tmp/catalyst/snapshot_cache/20180110T081028Z/.catalyst_lock' |
| 21 |
--- Running action sequence: setup_confdir |
| 22 |
Configuring /etc/portage... |
| 23 |
--- Running action sequence: portage_overlay |
| 24 |
--- Running action sequence: base_dirs |
| 25 |
--- Running action sequence: bind |
| 26 |
--- Running action sequence: chroot_setup |
| 27 |
Setting up chroot... |
| 28 |
|
| 29 |
Warning!!!! |
| 30 |
Overriding certain env variables may cause catastrophic failure. |
| 31 |
If your build fails look here first as the possible problem. |
| 32 |
Catalyst assumes you know what you are doing when setting |
| 33 |
these variables. |
| 34 |
Catalyst Maintainers use VERY minimal envscripts if used at all |
| 35 |
You have been warned |
| 36 |
|
| 37 |
--- Running action sequence: setup_environment |
| 38 |
--- Running action sequence: run_local |
| 39 |
copying make.conf to /var/tmp/catalyst/tmp/default/stage1-s390-20180110T081028Z///tmp/stage1root/etc/portage |
| 40 |
Copying stage1-chroot.sh to /tmp |
| 41 |
copying stage1-chroot.sh to /var/tmp/catalyst/tmp/default/stage1-s390-20180110T081028Z//tmp |
| 42 |
copying chroot-functions.sh to /var/tmp/catalyst/tmp/default/stage1-s390-20180110T081028Z//tmp |
| 43 |
Ensure the file has the executable bit set |
| 44 |
Running stage1-chroot.sh in chroot /var/tmp/catalyst/tmp/default/stage1-s390-20180110T081028Z/ |
| 45 |
>>> Regenerating /etc/ld.so.cache... |
| 46 |
Adding USE=' build' to make.conf for portage build |
| 47 |
emerge --quiet --oneshot --update --newuse sys-apps/portage |
| 48 |
|
| 49 |
Performing Global Updates |
| 50 |
(Could take a couple of minutes if you have a lot of binary packages.) |
| 51 |
|
| 52 |
|
| 53 |
|
| 54 |
The following packages are causing rebuilds: |
| 55 |
|
| 56 |
(app-arch/bzip2-1.0.6-r8:0/1::gentoo, ebuild scheduled for merge) causes rebuilds for: |
| 57 |
(dev-lang/python-2.7.14-r1:2.7/2.7::gentoo, ebuild scheduled for merge) |
| 58 |
(dev-lang/python-3.4.5-r1:3.4/3.4m::gentoo, ebuild scheduled for merge) |
| 59 |
(sys-libs/zlib-1.2.11-r1:0/1::gentoo, ebuild scheduled for merge) causes rebuilds for: |
| 60 |
(dev-libs/libxml2-2.9.4-r1:2/2::gentoo, ebuild scheduled for merge) |
| 61 |
(dev-lang/python-2.7.14-r1:2.7/2.7::gentoo, ebuild scheduled for merge) |
| 62 |
(dev-lang/python-3.4.5-r1:3.4/3.4m::gentoo, ebuild scheduled for merge) |
| 63 |
|
| 64 |
!!! The following installed packages are masked: |
| 65 |
- sys-devel/gcc-4.9.4::gentoo (masked by: package.mask) |
| 66 |
/usr/portage/profiles/package.mask: |
| 67 |
# Michał Górny <mgorny@g.o>, Andreas K. Hüttel <dilfridge@g.o>, |
| 68 |
# Matthias Maier <tamiko@g.o> (21 May 2017) |
| 69 |
# These old versions of toolchain packages (binutils, gcc, glibc) are no |
| 70 |
# longer officially supported and are not suitable for general use. Using |
| 71 |
# these packages can result in build failures (and possible breakage) for |
| 72 |
# many packages, and may leave your system vulnerable to known security |
| 73 |
# exploits. |
| 74 |
# If you still use one of these old toolchain packages, please upgrade (and |
| 75 |
# switch the compiler / the binutils) ASAP. If you need them for a specific |
| 76 |
# (isolated) use case, feel free to unmask them on your system. |
| 77 |
# (updated 27 Dec 2017 with gcc < 5.4) |
| 78 |
|
| 79 |
- sys-libs/glibc-2.23-r3::gentoo (masked by: package.mask) |
| 80 |
- sys-devel/binutils-2.26.1::gentoo (masked by: package.mask) |
| 81 |
For more information, see the MASKED PACKAGES section in the emerge |
| 82 |
man page or refer to the Gentoo Handbook. |
| 83 |
|
| 84 |
>>> Verifying ebuild manifests |
| 85 |
>>> Emerging (1 of 8) app-arch/bzip2-1.0.6-r8::gentoo |
| 86 |
>>> Installing (1 of 8) app-arch/bzip2-1.0.6-r8::gentoo |
| 87 |
>>> Emerging (2 of 8) app-portage/elt-patches-20170815::gentoo |
| 88 |
>>> Installing (2 of 8) app-portage/elt-patches-20170815::gentoo |
| 89 |
>>> Emerging (3 of 8) sys-libs/zlib-1.2.11-r1::gentoo |
| 90 |
>>> Installing (3 of 8) sys-libs/zlib-1.2.11-r1::gentoo |
| 91 |
>>> Emerging (4 of 8) dev-lang/python-2.7.14-r1::gentoo |
| 92 |
>>> Installing (4 of 8) dev-lang/python-2.7.14-r1::gentoo |
| 93 |
>>> Emerging (5 of 8) dev-lang/python-3.4.5-r1::gentoo |
| 94 |
>>> Installing (5 of 8) dev-lang/python-3.4.5-r1::gentoo |
| 95 |
>>> Emerging (6 of 8) dev-libs/libxml2-2.9.4-r1::gentoo |
| 96 |
>>> Installing (6 of 8) dev-libs/libxml2-2.9.4-r1::gentoo |
| 97 |
>>> Emerging (7 of 8) dev-lang/python-3.5.4-r1::gentoo |
| 98 |
>>> Installing (7 of 8) dev-lang/python-3.5.4-r1::gentoo |
| 99 |
>>> Emerging (8 of 8) sys-apps/portage-2.3.8::gentoo |
| 100 |
>>> Installing (8 of 8) sys-apps/portage-2.3.8::gentoo |
| 101 |
* Messages for package dev-lang/python-3.5.4-r1: |
| 102 |
* You have just upgraded from an older version of Python. |
| 103 |
* |
| 104 |
* Please adjust PYTHON_TARGETS (if so desired), and run emerge with the --newuse or --changed-use option to rebuild packages installing python modules. |
| 105 |
|
| 106 |
|
| 107 |
Updating seed stage... |
| 108 |
emerge --quiet --update --deep --newuse --complete-graph --rebuild-if-new-ver gcc |
| 109 |
[ebuild U ] sys-apps/gentoo-functions-0.12 [0.10] |
| 110 |
[ebuild U ] app-text/sgml-common-0.6.3-r6 [0.6.3-r5] |
| 111 |
[ebuild U ] sys-devel/binutils-config-5-r4 [5-r3] |
| 112 |
[ebuild U ] dev-libs/libffi-3.2.1 [3.0.13-r1] |
| 113 |
[ebuild R ] sys-libs/cracklib-2.9.6-r1 |
| 114 |
[ebuild U ] sys-apps/file-5.32 [5.29] |
| 115 |
[ebuild U ] dev-libs/mpc-1.0.2-r1 [1.0.1] |
| 116 |
[ebuild U ] sys-apps/coreutils-8.26 [8.25] |
| 117 |
[ebuild U ] app-admin/eselect-1.4.8 [1.4.5] |
| 118 |
[ebuild R ] sys-kernel/linux-headers-4.4 |
| 119 |
[ebuild U ] dev-libs/openssl-1.0.2n [1.0.2k] |
| 120 |
[ebuild U ] dev-libs/expat-2.2.1 [2.2.0-r1] |
| 121 |
[ebuild U ] sys-devel/gettext-0.19.8.1 [0.19.7] |
| 122 |
[ebuild NS ] sys-devel/gcc-5.4.0-r4 [4.9.4] |
| 123 |
[ebuild U ] sys-libs/pam-1.2.1-r2 [1.2.1] |
| 124 |
[ebuild U ] app-text/docbook-xsl-stylesheets-1.79.1-r2 [1.79.1-r1] |
| 125 |
[ebuild U ] net-misc/rsync-3.1.2-r1 [3.1.2] |
| 126 |
[ebuild U ] dev-python/setuptools-36.0.1 [30.4.0] |
| 127 |
[ebuild R ] dev-python/certifi-2016.9.26 |
| 128 |
[ebuild R ] dev-python/pyxattr-0.5.5 |
| 129 |
[ebuild U ] app-admin/perl-cleaner-2.25 [2.20] |
| 130 |
|
| 131 |
The following keyword changes are necessary to proceed: |
| 132 |
(see "package.accept_keywords" in the portage(5) man page for more details) |
| 133 |
# required by dev-python/pyxattr-0.5.5::gentoo |
| 134 |
# required by sys-apps/portage-2.3.8::gentoo[python_targets_python2_7,xattr] |
| 135 |
# required by app-admin/perl-cleaner-2.25::gentoo |
| 136 |
# required by dev-lang/perl-5.22.3_rc4::gentoo |
| 137 |
# required by sys-kernel/linux-headers-4.4::gentoo |
| 138 |
# required by sys-apps/busybox-1.25.1::gentoo |
| 139 |
# required by @system |
| 140 |
# required by @world (argument) |
| 141 |
=dev-python/setuptools-36.0.1 ~s390 |
| 142 |
|
| 143 |
Use --autounmask-write to write changes to config files (honoring |
| 144 |
CONFIG_PROTECT). Carefully examine the list of proposed changes, |
| 145 |
paying special attention to mask or keyword changes that may expose |
| 146 |
experimental or unstable packages. |
| 147 |
|
| 148 |
* In order to avoid wasting time, backtracking has terminated early |
| 149 |
* due to the above autounmask change(s). The --autounmask-backtrack=y |
| 150 |
* option can be used to force further backtracking, but there is no |
| 151 |
* guarantee that it will produce a solution. |
| 152 |
|
| 153 |
!!! The following installed packages are masked: |
| 154 |
- sys-devel/gcc-4.9.4::gentoo (masked by: package.mask) |
| 155 |
/usr/portage/profiles/package.mask: |
| 156 |
# Michał Górny <mgorny@g.o>, Andreas K. Hüttel <dilfridge@g.o>, |
| 157 |
# Matthias Maier <tamiko@g.o> (21 May 2017) |
| 158 |
# These old versions of toolchain packages (binutils, gcc, glibc) are no |
| 159 |
# longer officially supported and are not suitable for general use. Using |
| 160 |
# these packages can result in build failures (and possible breakage) for |
| 161 |
# many packages, and may leave your system vulnerable to known security |
| 162 |
# exploits. |
| 163 |
# If you still use one of these old toolchain packages, please upgrade (and |
| 164 |
# switch the compiler / the binutils) ASAP. If you need them for a specific |
| 165 |
# (isolated) use case, feel free to unmask them on your system. |
| 166 |
# (updated 27 Dec 2017 with gcc < 5.4) |
| 167 |
|
| 168 |
- sys-libs/glibc-2.23-r3::gentoo (masked by: package.mask) |
| 169 |
- sys-devel/binutils-2.26.1::gentoo (masked by: package.mask) |
| 170 |
For more information, see the MASKED PACKAGES section in the emerge |
| 171 |
man page or refer to the Gentoo Handbook. |
| 172 |
|
| 173 |
|
| 174 |
!!! catalyst: run script failed. |
| 175 |
|
| 176 |
|
| 177 |
Traceback (most recent call last): |
| 178 |
File "modules/generic_stage_target.py", line 1244, in run_local |
| 179 |
"run script failed.",env=self.env) |
| 180 |
File "/usr/lib/catalyst/modules/catalyst_support.py", line 541, in cmd |
| 181 |
raise CatalystError,myexc |
| 182 |
CatalystError |
| 183 |
None |
| 184 |
|
| 185 |
!!! catalyst: Stage build aborting due to error. |
| 186 |
|
| 187 |
Traceback (most recent call last): |
| 188 |
File "/usr/lib/catalyst/catalyst", line 218, in build_target |
| 189 |
mytarget.run() |
| 190 |
File "modules/generic_stage_target.py", line 1304, in run |
| 191 |
apply(getattr(self,x)) |
| 192 |
File "modules/generic_stage_target.py", line 1249, in run_local |
| 193 |
raise CatalystError,"Stage build aborting due to error." |
| 194 |
CatalystError |
| 195 |
!!! catalyst: Error encountered during run of target stage1 |
| 196 |
Catalyst aborting.... |
| 197 |
lockfile does not exist '/var/tmp/catalyst/tmp/default/stage1-s390-20180110T081028Z/.catalyst_lock' |
| 198 |
Command exited with non-zero status 1 |
| 199 |
420.15user 76.83system 6:43.64elapsed 123%CPU (0avgtext+0avgdata 465088maxresident)k |
| 200 |
0inputs+0outputs (549major+37537421minor)pagefaults 0swaps |
| 201 |
|
| 202 |
|
| 203 |
|
| 204 |
Full build log at /tmp/catalyst-auto.20180110T081028Z.Jju9gB/log/stage1.log |
Archives