1 |
Catalyst, version 2.0.17 |
2 |
Copyright 2003-2008 Gentoo Foundation |
3 |
Copyright 2008-2012 various authors |
4 |
Distributed under the GNU General Public License version 2.1 |
5 |
|
6 |
Using command line specified Catalyst configuration file, /etc/catalyst/catalyst.conf |
7 |
Setting sharedir to config file value "/usr/lib/catalyst" |
8 |
Setting snapshot_cache to config file value "/usr/local/catalyst/snapshot_cache" |
9 |
Setting hash_function to config file value "crc32" |
10 |
Setting storedir to config file value "/usr/local/catalyst" |
11 |
Setting portdir to config file value "/usr/portage" |
12 |
Setting distdir to config file value "/usr/portage/distfiles" |
13 |
Setting options to config file value "autoresume bindist pkgcache seedcache snapcache" |
14 |
Autoresuming support enabled. |
15 |
Binary redistribution enabled |
16 |
Package cache support enabled. |
17 |
Seed cache support enabled. |
18 |
Snapshot cache support enabled. |
19 |
Envscript support enabled. |
20 |
Using target: stage1 |
21 |
Building natively for hppa |
22 |
stage1 root path is /tmp/stage1root |
23 |
Source path set to /usr/local/catalyst/builds/default/stage3-hppa2.0-latest.tar.bz2 |
24 |
Caching snapshot to /usr/local/catalyst/snapshot_cache/20141017/ |
25 |
The autoresume path is /usr/local/catalyst/tmp/default/.autoresume-stage1-hppa2.0-20141017/ |
26 |
stage1 stage path is /usr/local/catalyst/tmp/default/stage1-hppa2.0-20141017/tmp/stage1root |
27 |
Location of the package cache is /usr/local/catalyst/packages/default/stage1-hppa2.0-20141017/ |
28 |
Checking for processes running in chroot and killing them. |
29 |
Removing AutoResume Points: ... |
30 |
Emptying directory /usr/local/catalyst/tmp/default/.autoresume-stage1-hppa2.0-20141017/ |
31 |
>>> Waiting 10 seconds before starting... |
32 |
>>> (Control-C to abort)... |
33 |
Purging Caches ... in: 10 9 8 7 6 5 4 3 2 1 |
34 |
clearing autoresume ... |
35 |
Removing AutoResume Points: ... |
36 |
Emptying directory /usr/local/catalyst/tmp/default/.autoresume-stage1-hppa2.0-20141017/ |
37 |
clearing chroot ... |
38 |
Emptying directory /usr/local/catalyst/tmp/default/stage1-hppa2.0-20141017/ |
39 |
clearing package cache ... |
40 |
purging the pkgcache ... |
41 |
clearing kerncache ... |
42 |
--- Running action sequence: unpack |
43 |
Referenced SEEDCACHE does not appear to be a directory, trying to untar... |
44 |
No Valid Resume point detected, cleaning up... |
45 |
Removing AutoResume Points: ... |
46 |
Emptying directory /usr/local/catalyst/tmp/default/.autoresume-stage1-hppa2.0-20141017/ |
47 |
Emptying directory /usr/local/catalyst/tmp/default/stage1-hppa2.0-20141017/ |
48 |
|
49 |
Starting tar extract from /usr/local/catalyst/builds/default/stage3-hppa2.0-latest.tar.bz2 |
50 |
to /usr/local/catalyst/tmp/default/stage1-hppa2.0-20141017/ (This may take some time) ... |
51 |
|
52 |
--- Running action sequence: unpack_snapshot |
53 |
Valid snapshot cache, skipping unpack of portage tree... |
54 |
--- Running action sequence: setup_confdir |
55 |
--- Running action sequence: portage_overlay |
56 |
--- Running action sequence: base_dirs |
57 |
--- Running action sequence: bind |
58 |
--- Running action sequence: chroot_setup |
59 |
Setting up chroot... |
60 |
|
61 |
Warning!!!! |
62 |
Overriding certain env variables may cause catastrophic failure. |
63 |
If your build fails look here first as the possible problem. |
64 |
Catalyst assumes you know what you are doing when setting |
65 |
these variables. |
66 |
Catalyst Maintainers use VERY minimal envscripts if used at all |
67 |
You have been warned |
68 |
|
69 |
--- Running action sequence: setup_environment |
70 |
--- Running action sequence: run_local |
71 |
copying make.conf to /usr/local/catalyst/tmp/default/stage1-hppa2.0-20141017///tmp/stage1root/etc/portage |
72 |
Copying stage1-chroot.sh to /tmp |
73 |
copying stage1-chroot.sh to /usr/local/catalyst/tmp/default/stage1-hppa2.0-20141017//tmp |
74 |
copying chroot-functions.sh to /usr/local/catalyst/tmp/default/stage1-hppa2.0-20141017//tmp |
75 |
Ensure the file has the executable bit set |
76 |
Running stage1-chroot.sh in chroot /usr/local/catalyst/tmp/default/stage1-hppa2.0-20141017/ |
77 |
>>> Regenerating /etc/ld.so.cache... |
78 |
emerge --quiet --oneshot --nodeps --update sys-apps/portage |
79 |
|
80 |
Performing Global Updates |
81 |
(Could take a couple of minutes if you have a lot of binary packages.) |
82 |
|
83 |
|
84 |
>>> Verifying ebuild manifests |
85 |
>>> Emerging (1 of 1) sys-apps/portage-2.2.8-r2 |
86 |
>>> Installing (1 of 1) sys-apps/portage-2.2.8-r2 |
87 |
Updating seed stage... |
88 |
emerge --quiet --update --deep --newuse --complete-graph --rebuild-if-new-ver gcc |
89 |
|
90 |
!!! The following installed packages are masked: |
91 |
- virtual/perl-ExtUtils-Install-1.580.0-r1::gentoo (masked by: package.mask) |
92 |
/usr/portage/profiles/package.mask: |
93 |
# Andreas K. Huettel <dilfridge@g.o> (9 Oct 2014) |
94 |
# Masked for removal in 30 days; see e.g. bug 446376 |
95 |
# Please upgrade to stable Perl 5.18 |
96 |
|
97 |
- virtual/perl-File-Temp-0.220.0-r3::gentoo (masked by: package.mask) |
98 |
- dev-lang/perl-5.16.3::gentoo (masked by: package.mask) |
99 |
For more information, see the MASKED PACKAGES section in the emerge |
100 |
man page or refer to the Gentoo Handbook. |
101 |
|
102 |
>>> Recording sys-devel/gcc:4.7 in "world" favorites file... |
103 |
>>> Verifying ebuild manifests |
104 |
>>> Running pre-merge checks for sys-devel/gcc-4.8.3 |
105 |
>>> Emerging (1 of 3) sys-libs/timezone-data-2014g |
106 |
>>> Installing (1 of 3) sys-libs/timezone-data-2014g |
107 |
>>> Emerging (2 of 3) sys-libs/glibc-2.19-r1 |
108 |
>>> Installing (2 of 3) sys-libs/glibc-2.19-r1 |
109 |
>>> Emerging (3 of 3) sys-devel/gcc-4.8.3 |
110 |
>>> Failed to emerge sys-devel/gcc-4.8.3 |
111 |
|
112 |
* Messages for package sys-libs/timezone-data-2014g: |
113 |
|
114 |
* You do not have TIMEZONE set in /etc/timezone. |
115 |
* Skipping auto-update of /etc/localtime. |
116 |
|
117 |
* Messages for package sys-libs/glibc-2.19-r1: |
118 |
|
119 |
* Defaulting /etc/host.conf:multi to on |
120 |
* Generating all locales; edit /etc/locale.gen to save time/space |
121 |
* The ebuild phase 'other' has exited unexpectedly. This type of behavior |
122 |
* is known to be triggered by things such as failed variable assignments |
123 |
* (bug #190128) or bad substitution errors (bug #200313). Normally, before |
124 |
* exiting, bash should have displayed an error message above. If bash did |
125 |
* not produce an error message above, it's possible that the ebuild has |
126 |
* called `exit` when it should have called `die` instead. This behavior |
127 |
* may also be triggered by a corrupt bash binary or a hardware problem |
128 |
* such as memory or cpu malfunction. If the problem is not reproducible or |
129 |
* it appears to occur randomly, then it is likely to be triggered by a |
130 |
* hardware problem. If you suspect a hardware problem then you should try |
131 |
* some basic hardware diagnostics such as memtest. Please do not report |
132 |
* this as a bug unless it is consistently reproducible and you are sure |
133 |
* that your bash binary and hardware are functioning properly. |
134 |
|
135 |
* Messages for package sys-devel/gcc-4.8.3: |
136 |
|
137 |
|
138 |
!!! catalyst: run script failed. |
139 |
|
140 |
|
141 |
Traceback (most recent call last): |
142 |
File "modules/generic_stage_target.py", line 1244, in run_local |
143 |
"run script failed.",env=self.env) |
144 |
File "/usr/lib/catalyst/modules/catalyst_support.py", line 541, in cmd |
145 |
raise CatalystError,myexc |
146 |
CatalystError |
147 |
None |
148 |
|
149 |
!!! catalyst: Stage build aborting due to error. |
150 |
|
151 |
Traceback (most recent call last): |
152 |
File "/usr/lib/catalyst/catalyst", line 218, in build_target |
153 |
mytarget.run() |
154 |
File "modules/generic_stage_target.py", line 1304, in run |
155 |
apply(getattr(self,x)) |
156 |
File "modules/generic_stage_target.py", line 1249, in run_local |
157 |
raise CatalystError,"Stage build aborting due to error." |
158 |
CatalystError |
159 |
!!! catalyst: Error encountered during run of target stage1 |
160 |
Catalyst aborting.... |
161 |
lockfile does not exist '/usr/local/catalyst/tmp/default/stage1-hppa2.0-20141017/.catalyst_lock' |
162 |
|
163 |
|
164 |
|
165 |
Full build log at /tmp/catalyst-auto.23296/log/hppa2.0_stage1.log |