1 |
/usr/lib/portage/python2.7/ebuild-helpers/xattr/install -c -m 644 /var/tmp/portage/sys-devel/gettext-0.19.4/work/gettext-0.19.4/gettext-tools/examples/hello-php/po/sv.po /var/tmp/portage/sys-devel/gettext-0.19.4/image//usr/share/doc/gettext-0.19.4/examples/hello-php/po/sv.po |
2 |
/bin/sh: line 11: /usr/lib/portage/python2.7/ebuild-helpers/xattr/install: No such file or directory |
3 |
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored. |
4 |
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored. |
5 |
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored. |
6 |
/usr/lib/portage/python2.7/ebuild-helpers/xattr/install -c -m 644 /var/tmp/portage/sys-devel/gettext-0.19.4/work/gettext-0.19.4/gettext-tools/examples/hello-php/po/tr.po /var/tmp/portage/sys-devel/gettext-0.19.4/image//usr/share/doc/gettext-0.19.4/examples/hello-php/po/tr.po |
7 |
/bin/sh: line 11: /usr/lib/portage/python2.7/ebuild-helpers/xattr/install: No such file or directory |
8 |
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored. |
9 |
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored. |
10 |
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored. |
11 |
/usr/lib/portage/python2.7/ebuild-helpers/xattr/install -c -m 644 /var/tmp/portage/sys-devel/gettext-0.19.4/work/gettext-0.19.4/gettext-tools/examples/hello-php/po/uk.po /var/tmp/portage/sys-devel/gettext-0.19.4/image//usr/share/doc/gettext-0.19.4/examples/hello-php/po/uk.po |
12 |
/bin/sh: line 11: /usr/lib/portage/python2.7/ebuild-helpers/xattr/install: No such file or directory |
13 |
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored. |
14 |
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored. |
15 |
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored. |
16 |
/usr/lib/portage/python2.7/ebuild-helpers/xattr/install -c -m 644 /var/tmp/portage/sys-devel/gettext-0.19.4/work/gettext-0.19.4/gettext-tools/examples/hello-php/po/vi.po /var/tmp/portage/sys-devel/gettext-0.19.4/image//usr/share/doc/gettext-0.19.4/examples/hello-php/po/vi.po |
17 |
/bin/sh: line 11: /usr/lib/portage/python2.7/ebuild-helpers/xattr/install: No such file or directory |
18 |
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored. |
19 |
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored. |
20 |
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored. |
21 |
/usr/lib/portage/python2.7/ebuild-helpers/xattr/install -c -m 644 /var/tmp/portage/sys-devel/gettext-0.19.4/work/gettext-0.19.4/gettext-tools/examples/hello-php/po/zh_CN.po /var/tmp/portage/sys-devel/gettext-0.19.4/image//usr/share/doc/gettext-0.19.4/examples/hello-php/po/zh_CN.po |
22 |
/bin/sh: line 11: /usr/lib/portage/python2.7/ebuild-helpers/xattr/install: No such file or directory |
23 |
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored. |
24 |
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored. |
25 |
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored. |
26 |
/usr/lib/portage/python2.7/ebuild-helpers/xattr/install -c -m 644 /var/tmp/portage/sys-devel/gettext-0.19.4/work/gettext-0.19.4/gettext-tools/examples/hello-php/po/zh_HK.po /var/tmp/portage/sys-devel/gettext-0.19.4/image//usr/share/doc/gettext-0.19.4/examples/hello-php/po/zh_HK.po |
27 |
/bin/sh: line 11: /usr/lib/portage/python2.7/ebuild-helpers/xattr/install: No such file or directory |
28 |
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored. |
29 |
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored. |
30 |
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored. |
31 |
/usr/lib/portage/python2.7/ebuild-helpers/xattr/install -c -m 644 /var/tmp/portage/sys-devel/gettext-0.19.4/work/gettext-0.19.4/gettext-tools/examples/hello-php/po/zh_TW.po /var/tmp/portage/sys-devel/gettext-0.19.4/image//usr/share/doc/gettext-0.19.4/examples/hello-php/po/zh_TW.po |
32 |
/bin/sh: line 11: /usr/lib/portage/python2.7/ebuild-helpers/xattr/install: No such file or directory |
33 |
Makefile:1232: recipe for target 'install-data-local' failed |
34 |
make[5]: *** [install-data-local] Error 127 |
35 |
make[5]: Leaving directory '/var/tmp/portage/sys-devel/gettext-0.19.4/work/gettext-0.19.4-abi_x86_64.amd64/gettext-tools/examples' |
36 |
Makefile:1118: recipe for target 'install-am' failed |
37 |
make[4]: *** [install-am] Error 2 |
38 |
make[4]: Leaving directory '/var/tmp/portage/sys-devel/gettext-0.19.4/work/gettext-0.19.4-abi_x86_64.amd64/gettext-tools/examples' |
39 |
Makefile:816: recipe for target 'install-recursive' failed |
40 |
make[3]: *** [install-recursive] Error 1 |
41 |
make[3]: Leaving directory '/var/tmp/portage/sys-devel/gettext-0.19.4/work/gettext-0.19.4-abi_x86_64.amd64/gettext-tools/examples' |
42 |
Makefile:1721: recipe for target 'install-recursive' failed |
43 |
make[2]: *** [install-recursive] Error 1 |
44 |
make[2]: Leaving directory '/var/tmp/portage/sys-devel/gettext-0.19.4/work/gettext-0.19.4-abi_x86_64.amd64/gettext-tools' |
45 |
Makefile:369: recipe for target 'install-recursive' failed |
46 |
make[1]: *** [install-recursive] Error 1 |
47 |
make[1]: Leaving directory '/var/tmp/portage/sys-devel/gettext-0.19.4/work/gettext-0.19.4-abi_x86_64.amd64' |
48 |
Makefile:666: recipe for target 'install' failed |
49 |
make: *** [install] Error 2 |
50 |
* ERROR: sys-devel/gettext-0.19.4::gentoo failed (install phase): |
51 |
* emake failed |
52 |
* |
53 |
* If you need support, post the output of `emerge --info '=sys-devel/gettext-0.19.4::gentoo'`, |
54 |
* the complete build log and the output of `emerge -pqv '=sys-devel/gettext-0.19.4::gentoo'`. |
55 |
* The complete build log is located at '/home/release/tmp/logs/sys-devel:gettext-0.19.4:20151123-160059.log'. |
56 |
* For convenience, a symlink to the build log is located at '/var/tmp/portage/sys-devel/gettext-0.19.4/temp/build.log'. |
57 |
* The ebuild environment file is located at '/var/tmp/portage/sys-devel/gettext-0.19.4/temp/environment'. |
58 |
* Working directory: '/var/tmp/portage/sys-devel/gettext-0.19.4/work/gettext-0.19.4-abi_x86_64.amd64' |
59 |
* S: '/var/tmp/portage/sys-devel/gettext-0.19.4/work/gettext-0.19.4' |
60 |
/usr/lib/portage/python2.7/isolated-functions.sh: line 232: /usr/lib/portage/python2.7/ebuild-ipc: No such file or directory |
61 |
* The ebuild phase 'install' has exited unexpectedly. This type of |
62 |
* behavior is known to be triggered by things such as failed variable |
63 |
* assignments (bug #190128) or bad substitution errors (bug #200313). |
64 |
* Normally, before exiting, bash should have displayed an error message |
65 |
* above. If bash did not produce an error message above, it's possible |
66 |
* that the ebuild has called `exit` when it should have called `die` |
67 |
* instead. This behavior may also be triggered by a corrupt bash binary or |
68 |
* a hardware problem such as memory or cpu malfunction. If the problem is |
69 |
* not reproducible or it appears to occur randomly, then it is likely to |
70 |
* be triggered by a hardware problem. If you suspect a hardware problem |
71 |
* then you should try some basic hardware diagnostics such as memtest. |
72 |
* Please do not report this as a bug unless it is consistently |
73 |
* reproducible and you are sure that your bash binary and hardware are |
74 |
* functioning properly. |
75 |
[Errno 2] No such file or directory: |
76 |
/usr/bin/sandbox /usr/lib/portage/python2.7/misc-functions.sh die_hooks |
77 |
Traceback (most recent call last): |
78 |
File "/usr/lib64/python2.7/site-packages/portage/process.py", line 317, in spawn |
79 |
File "/usr/lib64/python2.7/site-packages/portage/process.py", line 515, in _exec |
80 |
File "/usr/lib64/python2.7/site-packages/portage/__init__.py", line 259, in __call__ |
81 |
OSError: [Errno 2] No such file or directory |
82 |
* The ebuild phase 'die_hooks' has exited unexpectedly. This type of |
83 |
* behavior is known to be triggered by things such as failed variable |
84 |
* assignments (bug #190128) or bad substitution errors (bug #200313). |
85 |
* Normally, before exiting, bash should have displayed an error message |
86 |
* above. If bash did not produce an error message above, it's possible |
87 |
* that the ebuild has called `exit` when it should have called `die` |
88 |
* instead. This behavior may also be triggered by a corrupt bash binary or |
89 |
* a hardware problem such as memory or cpu malfunction. If the problem is |
90 |
* not reproducible or it appears to occur randomly, then it is likely to |
91 |
* be triggered by a hardware problem. If you suspect a hardware problem |
92 |
* then you should try some basic hardware diagnostics such as memtest. |
93 |
* Please do not report this as a bug unless it is consistently |
94 |
* reproducible and you are sure that your bash binary and hardware are |
95 |
* functioning properly. |
96 |
|
97 |
* Messages for package sys-libs/timezone-data-2015f merged to /tmp/stage1root/: |
98 |
|
99 |
* You do not have TIMEZONE set in /tmp/stage1root/etc/timezone. |
100 |
* Setting /tmp/stage1root/etc/localtime to Factory. |
101 |
|
102 |
* Messages for package sys-apps/shadow-4.1.5.1-r1 merged to /tmp/stage1root/: |
103 |
|
104 |
* Running 'grpck' returned errors. Please run it by hand, and then |
105 |
* run 'grpconv' afterwards! |
106 |
|
107 |
* Messages for package sys-apps/less-481 merged to /tmp/stage1root/: |
108 |
|
109 |
* lesspipe offers colorization options. Run 'lesspipe -h' for info. |
110 |
|
111 |
* Messages for package sys-apps/coreutils-8.23 merged to /tmp/stage1root/: |
112 |
|
113 |
* Make sure you run 'hash -r' in your active shells. |
114 |
* You should also re-source your shell settings for LS_COLORS |
115 |
* changes, such as: source /etc/profile |
116 |
|
117 |
* Messages for package app-portage/portage-utils-0.56 merged to /tmp/stage1root/: |
118 |
|
119 |
* /etc/portage/postsync.d/q-reinitialize has been installed for convenience |
120 |
* If you wish for it to be automatically run at the end of every --sync: |
121 |
* # chmod +x /etc/portage/postsync.d/q-reinitialize |
122 |
* Normally this should only take a few seconds to run but file systems |
123 |
* such as ext3 can take a lot longer. To disable, simply do: |
124 |
* # chmod -x /etc/portage/postsync.d/q-reinitialize |
125 |
|
126 |
* Messages for package dev-lang/perl-5.20.2 merged to /tmp/stage1root/: |
127 |
|
128 |
* Unable to establish /tmp/stage1root//usr/share/man/man1/ptar.1.bz2 symlink |
129 |
* Unable to establish /tmp/stage1root//usr/share/man/man1/ptardiff.1.bz2 symlink |
130 |
* Unable to establish /tmp/stage1root//usr/share/man/man1/ptargrep.1.bz2 symlink |
131 |
* Unable to establish /tmp/stage1root//usr/share/man/man1/shasum.1.bz2 symlink |
132 |
* Unable to establish /tmp/stage1root//usr/share/man/man1/cpan.1.bz2 symlink |
133 |
* Unable to establish /tmp/stage1root//usr/share/man/man1/enc2xs.1.bz2 symlink |
134 |
* Unable to establish /tmp/stage1root//usr/share/man/man1/piconv.1.bz2 symlink |
135 |
* Unable to establish /tmp/stage1root//usr/share/man/man1/instmodsh.1.bz2 symlink |
136 |
* Unable to establish /tmp/stage1root//usr/share/man/man1/xsubpp.1.bz2 symlink |
137 |
* Unable to establish /tmp/stage1root//usr/share/man/man1/zipdetails.1.bz2 symlink |
138 |
* Unable to establish /tmp/stage1root//usr/share/man/man1/json_pp.1.bz2 symlink |
139 |
* Unable to establish /tmp/stage1root//usr/share/man/man1/corelist.1.bz2 symlink |
140 |
* Unable to establish /tmp/stage1root//usr/share/man/man1/pod2usage.1.bz2 symlink |
141 |
* Unable to establish /tmp/stage1root//usr/share/man/man1/podchecker.1.bz2 symlink |
142 |
* Unable to establish /tmp/stage1root//usr/share/man/man1/podselect.1.bz2 symlink |
143 |
* Unable to establish /tmp/stage1root//usr/share/man/man1/perldoc.1.bz2 symlink |
144 |
* Unable to establish /tmp/stage1root//usr/share/man/man1/prove.1.bz2 symlink |
145 |
* Unable to establish /tmp/stage1root//usr/share/man/man1/pod2man.1.bz2 symlink |
146 |
* Unable to establish /tmp/stage1root//usr/share/man/man1/pod2text.1.bz2 symlink |
147 |
* Unable to establish /tmp/stage1root//usr/share/man/man1/perlpodstyle.1.bz2 symlink |
148 |
|
149 |
* Messages for package sys-libs/glibc-2.21-r1 merged to /tmp/stage1root/: |
150 |
|
151 |
* Defaulting /etc/host.conf:multi to on |
152 |
|
153 |
* Messages for package dev-libs/libxml2-2.9.2-r4 merged to /tmp/stage1root/: |
154 |
|
155 |
* Skipping XML catalog creation for stage building (bug #208887). |
156 |
|
157 |
* Messages for package sys-devel/gcc-4.9.3 merged to /tmp/stage1root/: |
158 |
|
159 |
* If you have issues with packages unable to locate libstdc++.la, |
160 |
* then try running 'fix_libtool_files.sh' on the old gcc versions. |
161 |
* You might want to review the GCC upgrade guide when moving between |
162 |
* major versions (like 4.2 to 4.3): |
163 |
* https://wiki.gentoo.org/wiki/Upgrading_GCC |
164 |
|
165 |
* Messages for package sys-devel/gettext-0.19.4 merged to /tmp/stage1root/: |
166 |
|
167 |
* The ebuild phase 'install' has exited unexpectedly. This type of |
168 |
* behavior is known to be triggered by things such as failed variable |
169 |
* assignments (bug #190128) or bad substitution errors (bug #200313). |
170 |
* Normally, before exiting, bash should have displayed an error message |
171 |
* above. If bash did not produce an error message above, it's possible |
172 |
* that the ebuild has called `exit` when it should have called `die` |
173 |
* instead. This behavior may also be triggered by a corrupt bash binary or |
174 |
* a hardware problem such as memory or cpu malfunction. If the problem is |
175 |
* not reproducible or it appears to occur randomly, then it is likely to |
176 |
* be triggered by a hardware problem. If you suspect a hardware problem |
177 |
* then you should try some basic hardware diagnostics such as memtest. |
178 |
* Please do not report this as a bug unless it is consistently |
179 |
* reproducible and you are sure that your bash binary and hardware are |
180 |
* functioning properly. |
181 |
* ERROR: sys-devel/gettext-0.19.4::gentoo failed (install phase): |
182 |
* emake failed |
183 |
* |
184 |
* If you need support, post the output of `emerge --info '=sys-devel/gettext-0.19.4::gentoo'`, |
185 |
* the complete build log and the output of `emerge -pqv '=sys-devel/gettext-0.19.4::gentoo'`. |
186 |
* The complete build log is located at '/home/release/tmp/logs/sys-devel:gettext-0.19.4:20151123-160059.log'. |
187 |
* For convenience, a symlink to the build log is located at '/var/tmp/portage/sys-devel/gettext-0.19.4/temp/build.log'. |
188 |
* The ebuild environment file is located at '/var/tmp/portage/sys-devel/gettext-0.19.4/temp/environment'. |
189 |
* Working directory: '/var/tmp/portage/sys-devel/gettext-0.19.4/work/gettext-0.19.4-abi_x86_64.amd64' |
190 |
* S: '/var/tmp/portage/sys-devel/gettext-0.19.4/work/gettext-0.19.4' |
191 |
23 Nov 2015 16:04:46 UTC: ERROR : CatalystError: cmd() NON-zero return value from: run script failed. |
192 |
23 Nov 2015 16:04:46 UTC: ERROR : CatalystError: Stage build aborting due to error. |
193 |
23 Nov 2015 16:04:46 UTC: ERROR : Exception running action sequence run_local |
194 |
Traceback (most recent call last): |
195 |
File "/usr/lib64/python2.7/site-packages/catalyst/base/stagebase.py", line 1397, in run |
196 |
getattr(self, x)() |
197 |
File "/usr/lib64/python2.7/site-packages/catalyst/base/stagebase.py", line 1309, in run_local |
198 |
print_traceback=False) |
199 |
CatalystError |
200 |
23 Nov 2015 16:04:46 UTC: NOTICE : Cleaning up... Running unbind() |
201 |
|
202 |
|
203 |
|
204 |
Full build log at /home/release/tmp/run/catalyst-auto.oyKqIK/log/hardened_stage1.log |