1 |
>>> Installing (61 of 118) dev-lang/python-3.4.1::gentoo |
2 |
>>> Emerging (62 of 118) sys-libs/db-4.8.30-r2::gentoo |
3 |
* The ebuild phase 'test' has exited unexpectedly. This type of behavior |
4 |
* is known to be triggered by things such as failed variable assignments |
5 |
* (bug #190128) or bad substitution errors (bug #200313). Normally, before |
6 |
* exiting, bash should have displayed an error message above. If bash did |
7 |
* not produce an error message above, it's possible that the ebuild has |
8 |
* called `exit` when it should have called `die` instead. This behavior |
9 |
* may also be triggered by a corrupt bash binary or a hardware problem |
10 |
* such as memory or cpu malfunction. If the problem is not reproducible or |
11 |
* it appears to occur randomly, then it is likely to be triggered by a |
12 |
* hardware problem. If you suspect a hardware problem then you should try |
13 |
* some basic hardware diagnostics such as memtest. Please do not report |
14 |
* this as a bug unless it is consistently reproducible and you are sure |
15 |
* that your bash binary and hardware are functioning properly. |
16 |
* The ebuild phase 'die_hooks' has been aborted since PORTAGE_BUILDDIR |
17 |
* does not exist: '/var/tmp/portage/sys-libs/db-4.8.30-r2' |
18 |
|
19 |
* Messages for package sys-libs/timezone-data-2015b: |
20 |
|
21 |
* You do not have TIMEZONE set in /etc/timezone. |
22 |
* Skipping auto-update of /etc/localtime. |
23 |
|
24 |
* Messages for package sys-apps/sysvinit-2.88-r7: |
25 |
|
26 |
* The last/lastb/mesg/mountpoint/sulogin/utmpdump/wall tools have been moved to |
27 |
* sys-apps/util-linux. The pidof tool has been moved to sys-process/procps. |
28 |
|
29 |
* Messages for package sys-apps/coreutils-8.23: |
30 |
|
31 |
* Make sure you run 'hash -r' in your active shells. |
32 |
* You should also re-source your shell settings for LS_COLORS |
33 |
* changes, such as: source /etc/profile |
34 |
|
35 |
* Messages for package sys-libs/pam-1.2.1: |
36 |
|
37 |
* Some software with pre-loaded PAM libraries might experience |
38 |
* warnings or failures related to missing symbols and/or versions |
39 |
* after any update. While unfortunate this is a limit of the |
40 |
* implementation of PAM and the software, and it requires you to |
41 |
* restart the software manually after the update. |
42 |
* |
43 |
* You can get a list of such software running a command like |
44 |
* lsof / | egrep -i 'del.*libpam\.so' |
45 |
* |
46 |
* Alternatively, simply reboot your system. |
47 |
|
48 |
* Messages for package sys-apps/busybox-1.23.1-r1: |
49 |
|
50 |
* Could not locate user configfile, so we will save a default one |
51 |
* You cannot have USE='static pam'. Assuming static is more important. |
52 |
* Your configuration for sys-apps/busybox-1.23.1-r1 has been saved in |
53 |
* /etc/portage/savedconfig/sys-apps/busybox-1.23.1-r1 for your editing pleasure. |
54 |
* You can edit these files by hand and remerge this package with |
55 |
* USE=savedconfig to customise the configuration. |
56 |
* You can rename this file/directory to one of the following for |
57 |
* its configuration to apply to multiple versions: |
58 |
* ${PORTAGE_CONFIGROOT}/etc/portage/savedconfig/ |
59 |
* [${CTARGET}|${CHOST}|""]/${CATEGORY}/[${PF}|${P}|${PN}] |
60 |
|
61 |
* Messages for package sys-libs/glibc-2.19-r1: |
62 |
|
63 |
* Defaulting /etc/host.conf:multi to on |
64 |
* Generating all locales; edit /etc/locale.gen to save time/space |
65 |
|
66 |
* Messages for package sys-apps/util-linux-2.25.2-r2: |
67 |
|
68 |
* The mesg/wall/write tools have been disabled due to USE=-tty-helpers. |
69 |
|
70 |
* Messages for package sys-apps/openrc-0.17: |
71 |
|
72 |
* Auto-adding 'binfmt' service to your boot runlevel |
73 |
* Setting the console font does not work on all HPPA consoles. |
74 |
* You can still enable it by running: |
75 |
* # rc-update add consolefont boot |
76 |
* In this version of OpenRC, the loopback interface no longer |
77 |
* satisfies the net virtual. |
78 |
* If you have services now which do not start because of this, |
79 |
* They can be fixed by adding rc_need="!net" |
80 |
* to the /etc/conf.d/<servicename> file. |
81 |
* You should also file a bug against the service asking that |
82 |
* need net be dropped from the dependencies. |
83 |
* The bug you file should block the following tracker: |
84 |
* https://bugs.gentoo.org/show_bug.cgi?id=439092 |
85 |
* |
86 |
* Bug https://bugs.gentoo.org/show_bug.cgi?id=427996 was not |
87 |
* fixed correctly in earlier versions of OpenRC. |
88 |
* The correct fix is implemented in this version, but that |
89 |
* means netmount needs to be added to the default runlevel if |
90 |
* you are using nfs file systems. |
91 |
* |
92 |
* You should now update all files in /etc, using etc-update |
93 |
* or equivalent before restarting any services or this host. |
94 |
|
95 |
* Messages for package sys-devel/gcc-4.8.4: |
96 |
|
97 |
* If you have issues with packages unable to locate libstdc++.la, |
98 |
* then try running 'fix_libtool_files.sh' on the old gcc versions. |
99 |
* You might want to review the GCC upgrade guide when moving between |
100 |
* major versions (like 4.2 to 4.3): |
101 |
* http://www.gentoo.org/doc/en/gcc-upgrading.xml |
102 |
|
103 |
* Messages for package sys-libs/db-4.8.30-r2: |
104 |
|
105 |
* The ebuild phase 'test' has exited unexpectedly. This type of behavior |
106 |
* is known to be triggered by things such as failed variable assignments |
107 |
* (bug #190128) or bad substitution errors (bug #200313). Normally, before |
108 |
* exiting, bash should have displayed an error message above. If bash did |
109 |
* not produce an error message above, it's possible that the ebuild has |
110 |
* called `exit` when it should have called `die` instead. This behavior |
111 |
* may also be triggered by a corrupt bash binary or a hardware problem |
112 |
* such as memory or cpu malfunction. If the problem is not reproducible or |
113 |
* it appears to occur randomly, then it is likely to be triggered by a |
114 |
* hardware problem. If you suspect a hardware problem then you should try |
115 |
* some basic hardware diagnostics such as memtest. Please do not report |
116 |
* this as a bug unless it is consistently reproducible and you are sure |
117 |
* that your bash binary and hardware are functioning properly. |
118 |
Traceback (most recent call last): |
119 |
File "/usr/lib/python-exec/python2.7/emerge", line 50, in <module> |
120 |
retval = emerge_main() |
121 |
File "/usr/lib/python2.7/site-packages/_emerge/main.py", line 1154, in emerge_main |
122 |
return run_action(emerge_config) |
123 |
File "/usr/lib/python2.7/site-packages/_emerge/actions.py", line 3191, in run_action |
124 |
emerge_config.args, spinner) |
125 |
File "/usr/lib/python2.7/site-packages/_emerge/actions.py", line 498, in action_build |
126 |
retval = mergetask.merge() |
127 |
File "/usr/lib/python2.7/site-packages/_emerge/Scheduler.py", line 1028, in merge |
128 |
rval = self._merge() |
129 |
File "/usr/lib/python2.7/site-packages/_emerge/Scheduler.py", line 1430, in _merge |
130 |
self._main_loop() |
131 |
File "/usr/lib/python2.7/site-packages/_emerge/Scheduler.py", line 1401, in _main_loop |
132 |
self._event_loop.iteration() |
133 |
File "/usr/lib/python2.7/site-packages/portage/util/_eventloop/EventLoop.py", line 204, in iteration |
134 |
if self._run_timeouts(): |
135 |
File "/usr/lib/python2.7/site-packages/portage/util/_eventloop/EventLoop.py", line 468, in _run_timeouts |
136 |
if self._run_idle_callbacks(): |
137 |
File "/usr/lib/python2.7/site-packages/portage/util/_eventloop/EventLoop.py", line 430, in _run_idle_callbacks |
138 |
if not x.callback(*x.args): |
139 |
File "/usr/lib/python2.7/site-packages/_emerge/AsynchronousTask.py", line 74, in _async_wait_cb |
140 |
self.wait() |
141 |
File "/usr/lib/python2.7/site-packages/_emerge/AsynchronousTask.py", line 57, in wait |
142 |
self._wait_hook() |
143 |
File "/usr/lib/python2.7/site-packages/_emerge/AsynchronousTask.py", line 175, in _wait_hook |
144 |
self._exit_listener_stack.pop()(self) |
145 |
File "/usr/lib/python2.7/site-packages/_emerge/EbuildPhase.py", line 345, in _die_hooks_exit |
146 |
self.wait() |
147 |
File "/usr/lib/python2.7/site-packages/_emerge/AsynchronousTask.py", line 57, in wait |
148 |
self._wait_hook() |
149 |
File "/usr/lib/python2.7/site-packages/_emerge/AsynchronousTask.py", line 175, in _wait_hook |
150 |
self._exit_listener_stack.pop()(self) |
151 |
File "/usr/lib/python2.7/site-packages/_emerge/TaskSequence.py", line 47, in _task_exit_handler |
152 |
self.wait() |
153 |
File "/usr/lib/python2.7/site-packages/_emerge/AsynchronousTask.py", line 57, in wait |
154 |
self._wait_hook() |
155 |
File "/usr/lib/python2.7/site-packages/_emerge/AsynchronousTask.py", line 175, in _wait_hook |
156 |
self._exit_listener_stack.pop()(self) |
157 |
File "/usr/lib/python2.7/site-packages/_emerge/CompositeTask.py", line 134, in _default_final_exit |
158 |
return self.wait() |
159 |
File "/usr/lib/python2.7/site-packages/_emerge/AsynchronousTask.py", line 57, in wait |
160 |
self._wait_hook() |
161 |
File "/usr/lib/python2.7/site-packages/_emerge/AsynchronousTask.py", line 175, in _wait_hook |
162 |
self._exit_listener_stack.pop()(self) |
163 |
File "/usr/lib/python2.7/site-packages/_emerge/EbuildBuild.py", line 298, in _build_exit |
164 |
self._unlock_builddir() |
165 |
File "/usr/lib/python2.7/site-packages/_emerge/EbuildBuild.py", line 294, in _unlock_builddir |
166 |
self._build_dir.unlock() |
167 |
File "/usr/lib/python2.7/site-packages/_emerge/EbuildBuildDir.py", line 96, in unlock |
168 |
catdir_lock.start() |
169 |
File "/usr/lib/python2.7/site-packages/_emerge/AsynchronousTask.py", line 30, in start |
170 |
self._start() |
171 |
File "/usr/lib/python2.7/site-packages/_emerge/AsynchronousLock.py", line 47, in _start |
172 |
wantnewlockfile=True, flags=os.O_NONBLOCK) |
173 |
File "/usr/lib/python2.7/site-packages/portage/locks.py", line 102, in lockfile |
174 |
raise DirectoryNotFound(os.path.dirname(mypath)) |
175 |
DirectoryNotFound: /var/tmp/portage |
176 |
|
177 |
!!! catalyst: run script failed. |
178 |
|
179 |
|
180 |
Traceback (most recent call last): |
181 |
File "modules/generic_stage_target.py", line 1244, in run_local |
182 |
"run script failed.",env=self.env) |
183 |
File "/usr/lib/catalyst/modules/catalyst_support.py", line 541, in cmd |
184 |
raise CatalystError,myexc |
185 |
CatalystError |
186 |
None |
187 |
|
188 |
!!! catalyst: Stage build aborting due to error. |
189 |
|
190 |
Traceback (most recent call last): |
191 |
File "/usr/lib/catalyst/catalyst", line 218, in build_target |
192 |
mytarget.run() |
193 |
File "modules/generic_stage_target.py", line 1304, in run |
194 |
apply(getattr(self,x)) |
195 |
File "modules/generic_stage_target.py", line 1249, in run_local |
196 |
raise CatalystError,"Stage build aborting due to error." |
197 |
CatalystError |
198 |
!!! catalyst: Error encountered during run of target stage1 |
199 |
Catalyst aborting.... |
200 |
lockfile does not exist '/usr/local/catalyst/tmp/default/stage1-hppa1.1-20150807/.catalyst_lock' |
201 |
|
202 |
|
203 |
|
204 |
Full build log at /tmp/catalyst-auto.ymqAY0/log/hppa1.1_stage1.log |