1 |
[0xfaef8004] |
2 |
[0xfb4f4e0c] |
3 |
/proc/29431/cmdline: ../../miniperl -I../../lib Makefile.PL INSTALLDIRS=perl INSTALLMAN1DIR=none INSTALLMAN3DIR=none PERL_CORE=1 LIBPERL_A=libperl.so.5.20.2 LINKTYPE=dynamic |
4 |
|
5 |
6 from cpan/Time-HiRes's Makefile.PL at make_ext.pl line 508. |
6 |
(null)*(null) ../../sandbox-2.6/libsandbox/libsandbox.c:check_syscall():879: failure (No such file or directory): |
7 |
(null)*(null) ISE: |
8 |
abs_path: (null) |
9 |
res_path: (null) |
10 |
[0xfaef8004] |
11 |
[0xfb10be0c] |
12 |
/proc/29430/cmdline: ./miniperl -Ilib make_ext.pl lib/auto/Time/HiRes/HiRes.so MAKE=make LIBPERL_A=libperl.so.5.20.2 LINKTYPE=dynamic |
13 |
|
14 |
makefile:592: recipe for target 'lib/auto/Time/HiRes/HiRes.so' failed |
15 |
make: *** [lib/auto/Time/HiRes/HiRes.so] Aborted |
16 |
* ERROR: dev-lang/perl-5.20.2::gentoo failed (compile phase): |
17 |
* emake failed |
18 |
* |
19 |
* If you need support, post the output of `emerge --info '=dev-lang/perl-5.20.2::gentoo'`, |
20 |
* the complete build log and the output of `emerge -pqv '=dev-lang/perl-5.20.2::gentoo'`. |
21 |
* The complete build log is located at '/var/tmp/portage/dev-lang/perl-5.20.2/temp/build.log'. |
22 |
* The ebuild environment file is located at '/var/tmp/portage/dev-lang/perl-5.20.2/temp/environment'. |
23 |
* Working directory: '/var/tmp/portage/dev-lang/perl-5.20.2/work/perl-5.20.2' |
24 |
* S: '/var/tmp/portage/dev-lang/perl-5.20.2/work/perl-5.20.2' |
25 |
ebuild-ipc: daemon process not detected |
26 |
* The ebuild phase 'compile' has exited unexpectedly. This type of |
27 |
* behavior is known to be triggered by things such as failed variable |
28 |
* assignments (bug #190128) or bad substitution errors (bug #200313). |
29 |
* Normally, before exiting, bash should have displayed an error message |
30 |
* above. If bash did not produce an error message above, it's possible |
31 |
* that the ebuild has called `exit` when it should have called `die` |
32 |
* instead. This behavior may also be triggered by a corrupt bash binary or |
33 |
* a hardware problem such as memory or cpu malfunction. If the problem is |
34 |
* not reproducible or it appears to occur randomly, then it is likely to |
35 |
* be triggered by a hardware problem. If you suspect a hardware problem |
36 |
* then you should try some basic hardware diagnostics such as memtest. |
37 |
* Please do not report this as a bug unless it is consistently |
38 |
* reproducible and you are sure that your bash binary and hardware are |
39 |
* functioning properly. |
40 |
ebuild-ipc: daemon process not detected |
41 |
* The ebuild phase 'die_hooks' has exited unexpectedly. This type of |
42 |
* behavior is known to be triggered by things such as failed variable |
43 |
* assignments (bug #190128) or bad substitution errors (bug #200313). |
44 |
* Normally, before exiting, bash should have displayed an error message |
45 |
* above. If bash did not produce an error message above, it's possible |
46 |
* that the ebuild has called `exit` when it should have called `die` |
47 |
* instead. This behavior may also be triggered by a corrupt bash binary or |
48 |
* a hardware problem such as memory or cpu malfunction. If the problem is |
49 |
* not reproducible or it appears to occur randomly, then it is likely to |
50 |
* be triggered by a hardware problem. If you suspect a hardware problem |
51 |
* then you should try some basic hardware diagnostics such as memtest. |
52 |
* Please do not report this as a bug unless it is consistently |
53 |
* reproducible and you are sure that your bash binary and hardware are |
54 |
* functioning properly. |
55 |
|
56 |
* Messages for package sys-libs/timezone-data-2015b: |
57 |
|
58 |
* You do not have TIMEZONE set in /etc/timezone. |
59 |
* Skipping auto-update of /etc/localtime. |
60 |
|
61 |
* Messages for package sys-apps/sysvinit-2.88-r7: |
62 |
|
63 |
* The last/lastb/mesg/mountpoint/sulogin/utmpdump/wall tools have been moved to |
64 |
* sys-apps/util-linux. The pidof tool has been moved to sys-process/procps. |
65 |
|
66 |
* Messages for package sys-apps/coreutils-8.23: |
67 |
|
68 |
* Make sure you run 'hash -r' in your active shells. |
69 |
* You should also re-source your shell settings for LS_COLORS |
70 |
* changes, such as: source /etc/profile |
71 |
|
72 |
* Messages for package sys-libs/pam-1.2.1: |
73 |
|
74 |
* Some software with pre-loaded PAM libraries might experience |
75 |
* warnings or failures related to missing symbols and/or versions |
76 |
* after any update. While unfortunate this is a limit of the |
77 |
* implementation of PAM and the software, and it requires you to |
78 |
* restart the software manually after the update. |
79 |
* |
80 |
* You can get a list of such software running a command like |
81 |
* lsof / | egrep -i 'del.*libpam\.so' |
82 |
* |
83 |
* Alternatively, simply reboot your system. |
84 |
|
85 |
* Messages for package sys-apps/busybox-1.23.1-r1: |
86 |
|
87 |
* Could not locate user configfile, so we will save a default one |
88 |
* You cannot have USE='static pam'. Assuming static is more important. |
89 |
* Your configuration for sys-apps/busybox-1.23.1-r1 has been saved in |
90 |
* /etc/portage/savedconfig/sys-apps/busybox-1.23.1-r1 for your editing pleasure. |
91 |
* You can edit these files by hand and remerge this package with |
92 |
* USE=savedconfig to customise the configuration. |
93 |
* You can rename this file/directory to one of the following for |
94 |
* its configuration to apply to multiple versions: |
95 |
* ${PORTAGE_CONFIGROOT}/etc/portage/savedconfig/ |
96 |
* [${CTARGET}|${CHOST}|""]/${CATEGORY}/[${PF}|${P}|${PN}] |
97 |
|
98 |
* Messages for package sys-libs/glibc-2.19-r1: |
99 |
|
100 |
* Defaulting /etc/host.conf:multi to on |
101 |
* Generating all locales; edit /etc/locale.gen to save time/space |
102 |
|
103 |
* Messages for package sys-apps/util-linux-2.25.2-r2: |
104 |
|
105 |
* The mesg/wall/write tools have been disabled due to USE=-tty-helpers. |
106 |
|
107 |
* Messages for package sys-apps/openrc-0.17: |
108 |
|
109 |
* Auto-adding 'binfmt' service to your boot runlevel |
110 |
* Setting the console font does not work on all HPPA consoles. |
111 |
* You can still enable it by running: |
112 |
* # rc-update add consolefont boot |
113 |
* In this version of OpenRC, the loopback interface no longer |
114 |
* satisfies the net virtual. |
115 |
* If you have services now which do not start because of this, |
116 |
* They can be fixed by adding rc_need="!net" |
117 |
* to the /etc/conf.d/<servicename> file. |
118 |
* You should also file a bug against the service asking that |
119 |
* need net be dropped from the dependencies. |
120 |
* The bug you file should block the following tracker: |
121 |
* https://bugs.gentoo.org/show_bug.cgi?id=439092 |
122 |
* |
123 |
* Bug https://bugs.gentoo.org/show_bug.cgi?id=427996 was not |
124 |
* fixed correctly in earlier versions of OpenRC. |
125 |
* The correct fix is implemented in this version, but that |
126 |
* means netmount needs to be added to the default runlevel if |
127 |
* you are using nfs file systems. |
128 |
* |
129 |
* You should now update all files in /etc, using etc-update |
130 |
* or equivalent before restarting any services or this host. |
131 |
|
132 |
* Messages for package sys-devel/gcc-4.8.4: |
133 |
|
134 |
* If you have issues with packages unable to locate libstdc++.la, |
135 |
* then try running 'fix_libtool_files.sh' on the old gcc versions. |
136 |
* You might want to review the GCC upgrade guide when moving between |
137 |
* major versions (like 4.2 to 4.3): |
138 |
* http://www.gentoo.org/doc/en/gcc-upgrading.xml |
139 |
|
140 |
* Messages for package net-misc/openssh-6.9_p1-r2: |
141 |
|
142 |
* Remember to merge your config files in /etc/ssh/ and then |
143 |
* reload sshd: '/etc/init.d/sshd reload'. |
144 |
* Note: openssh-6.7 versions no longer support USE=tcpd as upstream has |
145 |
* dropped it. Make sure to update any configs that you might have. |
146 |
|
147 |
* Messages for package dev-lang/perl-5.20.2: |
148 |
|
149 |
* UPDATE THE PERL MODULES: |
150 |
* After updating dev-lang/perl you must reinstall |
151 |
* the installed perl modules. |
152 |
* Use: perl-cleaner --all |
153 |
* The ebuild phase 'compile' has exited unexpectedly. This type of |
154 |
* behavior is known to be triggered by things such as failed variable |
155 |
* assignments (bug #190128) or bad substitution errors (bug #200313). |
156 |
* Normally, before exiting, bash should have displayed an error message |
157 |
* above. If bash did not produce an error message above, it's possible |
158 |
* that the ebuild has called `exit` when it should have called `die` |
159 |
* instead. This behavior may also be triggered by a corrupt bash binary or |
160 |
* a hardware problem such as memory or cpu malfunction. If the problem is |
161 |
* not reproducible or it appears to occur randomly, then it is likely to |
162 |
* be triggered by a hardware problem. If you suspect a hardware problem |
163 |
* then you should try some basic hardware diagnostics such as memtest. |
164 |
* Please do not report this as a bug unless it is consistently |
165 |
* reproducible and you are sure that your bash binary and hardware are |
166 |
* functioning properly. |
167 |
* ERROR: dev-lang/perl-5.20.2::gentoo failed (compile phase): |
168 |
* emake failed |
169 |
* |
170 |
* If you need support, post the output of `emerge --info '=dev-lang/perl-5.20.2::gentoo'`, |
171 |
* the complete build log and the output of `emerge -pqv '=dev-lang/perl-5.20.2::gentoo'`. |
172 |
* The complete build log is located at '/var/tmp/portage/dev-lang/perl-5.20.2/temp/build.log'. |
173 |
* The ebuild environment file is located at '/var/tmp/portage/dev-lang/perl-5.20.2/temp/environment'. |
174 |
* Working directory: '/var/tmp/portage/dev-lang/perl-5.20.2/work/perl-5.20.2' |
175 |
* S: '/var/tmp/portage/dev-lang/perl-5.20.2/work/perl-5.20.2' |
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-20150731/.catalyst_lock' |
201 |
|
202 |
|
203 |
|
204 |
Full build log at /tmp/catalyst-auto.PsEE2a/log/hppa1.1_stage1.log |