1 |
copying src/cryptography/hazmat/backends/commoncrypto/backend.py -> /var/tmp/portage/dev-python/cryptography-1.0.2/work/cryptography-1.0.2-python2_7/lib/cryptography/hazmat/backends/commoncrypto |
2 |
copying src/cryptography/hazmat/backends/commoncrypto/ciphers.py -> /var/tmp/portage/dev-python/cryptography-1.0.2/work/cryptography-1.0.2-python2_7/lib/cryptography/hazmat/backends/commoncrypto |
3 |
copying src/cryptography/hazmat/backends/commoncrypto/hashes.py -> /var/tmp/portage/dev-python/cryptography-1.0.2/work/cryptography-1.0.2-python2_7/lib/cryptography/hazmat/backends/commoncrypto |
4 |
running egg_info |
5 |
writing requirements to /var/tmp/portage/dev-python/cryptography-1.0.2/work/cryptography-1.0.2-python2_7/cryptography.egg-info/requires.txt |
6 |
writing /var/tmp/portage/dev-python/cryptography-1.0.2/work/cryptography-1.0.2-python2_7/cryptography.egg-info/PKG-INFO |
7 |
writing top-level names to /var/tmp/portage/dev-python/cryptography-1.0.2/work/cryptography-1.0.2-python2_7/cryptography.egg-info/top_level.txt |
8 |
writing dependency_links to /var/tmp/portage/dev-python/cryptography-1.0.2/work/cryptography-1.0.2-python2_7/cryptography.egg-info/dependency_links.txt |
9 |
writing entry points to /var/tmp/portage/dev-python/cryptography-1.0.2/work/cryptography-1.0.2-python2_7/cryptography.egg-info/entry_points.txt |
10 |
reading manifest file '/var/tmp/portage/dev-python/cryptography-1.0.2/work/cryptography-1.0.2-python2_7/cryptography.egg-info/SOURCES.txt' |
11 |
reading manifest template 'MANIFEST.in' |
12 |
no previously-included directories found matching 'docs/_build' |
13 |
warning: no previously-included files matching '*' found under directory 'vectors' |
14 |
writing manifest file '/var/tmp/portage/dev-python/cryptography-1.0.2/work/cryptography-1.0.2-python2_7/cryptography.egg-info/SOURCES.txt' |
15 |
warning: build_py: byte-compiling is disabled, skipping. |
16 |
|
17 |
running build_ext |
18 |
generating cffi module '/var/tmp/portage/dev-python/cryptography-1.0.2/work/cryptography-1.0.2-python2_7/temp.linux-ia64-2.7/_padding.c' |
19 |
creating /var/tmp/portage/dev-python/cryptography-1.0.2/work/cryptography-1.0.2-python2_7/temp.linux-ia64-2.7 |
20 |
generating cffi module '/var/tmp/portage/dev-python/cryptography-1.0.2/work/cryptography-1.0.2-python2_7/temp.linux-ia64-2.7/_constant_time.c' |
21 |
generating cffi module '/var/tmp/portage/dev-python/cryptography-1.0.2/work/cryptography-1.0.2-python2_7/temp.linux-ia64-2.7/_openssl.c' |
22 |
building '_openssl' extension |
23 |
creating /var/tmp/portage/dev-python/cryptography-1.0.2/work/cryptography-1.0.2-python2_7/temp.linux-ia64-2.7/var |
24 |
creating /var/tmp/portage/dev-python/cryptography-1.0.2/work/cryptography-1.0.2-python2_7/temp.linux-ia64-2.7/var/tmp |
25 |
creating /var/tmp/portage/dev-python/cryptography-1.0.2/work/cryptography-1.0.2-python2_7/temp.linux-ia64-2.7/var/tmp/portage |
26 |
creating /var/tmp/portage/dev-python/cryptography-1.0.2/work/cryptography-1.0.2-python2_7/temp.linux-ia64-2.7/var/tmp/portage/dev-python |
27 |
creating /var/tmp/portage/dev-python/cryptography-1.0.2/work/cryptography-1.0.2-python2_7/temp.linux-ia64-2.7/var/tmp/portage/dev-python/cryptography-1.0.2 |
28 |
creating /var/tmp/portage/dev-python/cryptography-1.0.2/work/cryptography-1.0.2-python2_7/temp.linux-ia64-2.7/var/tmp/portage/dev-python/cryptography-1.0.2/work |
29 |
creating /var/tmp/portage/dev-python/cryptography-1.0.2/work/cryptography-1.0.2-python2_7/temp.linux-ia64-2.7/var/tmp/portage/dev-python/cryptography-1.0.2/work/cryptography-1.0.2-python2_7 |
30 |
creating /var/tmp/portage/dev-python/cryptography-1.0.2/work/cryptography-1.0.2-python2_7/temp.linux-ia64-2.7/var/tmp/portage/dev-python/cryptography-1.0.2/work/cryptography-1.0.2-python2_7/temp.linux-ia64-2.7 |
31 |
ia64-unknown-linux-gnu-gcc -O2 -pipe -fPIC -I/usr/include/python2.7 -c /var/tmp/portage/dev-python/cryptography-1.0.2/work/cryptography-1.0.2-python2_7/temp.linux-ia64-2.7/_openssl.c -o /var/tmp/portage/dev-python/cryptography-1.0.2/work/cryptography-1.0.2-python2_7/temp.linux-ia64-2.7/var/tmp/portage/dev-python/cryptography-1.0.2/work/cryptography-1.0.2-python2_7/temp.linux-ia64-2.7/_openssl.o |
32 |
/var/tmp/portage/dev-python/cryptography-1.0.2/work/cryptography-1.0.2-python2_7/temp.linux-ia64-2.7/_openssl.c:687:6: error: conflicting types for ‘BIO_new_mem_buf’ |
33 |
BIO *BIO_new_mem_buf(void *, int); |
34 |
^ |
35 |
In file included from /usr/include/openssl/asn1.h:65:0, |
36 |
from /var/tmp/portage/dev-python/cryptography-1.0.2/work/cryptography-1.0.2-python2_7/temp.linux-ia64-2.7/_openssl.c:403: |
37 |
/usr/include/openssl/bio.h:692:6: note: previous declaration of ‘BIO_new_mem_buf’ was here |
38 |
BIO *BIO_new_mem_buf(const void *buf, int len); |
39 |
^ |
40 |
error: command 'ia64-unknown-linux-gnu-gcc' failed with exit status 1 |
41 |
* ERROR: dev-python/cryptography-1.0.2::gentoo failed (compile phase): |
42 |
* (no error message) |
43 |
* |
44 |
* Call stack: |
45 |
* ebuild.sh, line 133: Called src_compile |
46 |
* environment, line 3600: Called distutils-r1_src_compile |
47 |
* environment, line 916: Called _distutils-r1_run_foreach_impl 'distutils-r1_python_compile' |
48 |
* environment, line 337: Called python_foreach_impl 'distutils-r1_run_phase' 'distutils-r1_python_compile' |
49 |
* environment, line 3140: Called multibuild_foreach_variant '_python_multibuild_wrapper' 'distutils-r1_run_phase' 'distutils-r1_python_compile' |
50 |
* environment, line 2249: Called _multibuild_run '_python_multibuild_wrapper' 'distutils-r1_run_phase' 'distutils-r1_python_compile' |
51 |
* environment, line 2247: Called _python_multibuild_wrapper 'distutils-r1_run_phase' 'distutils-r1_python_compile' |
52 |
* environment, line 599: Called distutils-r1_run_phase 'distutils-r1_python_compile' |
53 |
* environment, line 907: Called distutils-r1_python_compile |
54 |
* environment, line 779: Called esetup.py 'build' |
55 |
* environment, line 1407: Called die |
56 |
* The specific snippet of code: |
57 |
* "${@}" || die "${die_args[@]}" || return ${?} |
58 |
* |
59 |
* If you need support, post the output of `emerge --info '=dev-python/cryptography-1.0.2::gentoo'`, |
60 |
* the complete build log and the output of `emerge -pqv '=dev-python/cryptography-1.0.2::gentoo'`. |
61 |
* The complete build log is located at '/var/tmp/portage/dev-python/cryptography-1.0.2/temp/build.log'. |
62 |
* The ebuild environment file is located at '/var/tmp/portage/dev-python/cryptography-1.0.2/temp/environment'. |
63 |
* Working directory: '/var/tmp/portage/dev-python/cryptography-1.0.2/work/cryptography-1.0.2' |
64 |
* S: '/var/tmp/portage/dev-python/cryptography-1.0.2/work/cryptography-1.0.2' |
65 |
|
66 |
* Messages for package sys-power/acpid-2.0.23: |
67 |
|
68 |
* Unable to find kernel sources at /usr/src/linux |
69 |
* Unable to calculate Linux Kernel version for build, attempting to use running version |
70 |
|
71 |
* Messages for package sys-fs/eudev-3.1.5: |
72 |
|
73 |
* |
74 |
* As of 2013-01-29, eudev-3.1.5 provides the new interface renaming functionality, |
75 |
* as described in the URL below: |
76 |
* http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames |
77 |
* |
78 |
* This functionality is enabled BY DEFAULT because eudev has no means of synchronizing |
79 |
* between the default or user-modified choice of sys-fs/udev. If you wish to disable |
80 |
* this new iface naming, please be sure that /etc/udev/rules.d/80-net-name-slot.rules |
81 |
* exists: touch /etc/udev/rules.d/80-net-name-slot.rules |
82 |
* |
83 |
|
84 |
* Messages for package sys-apps/keyutils-1.5.9-r1: |
85 |
|
86 |
* Unable to find kernel sources at /usr/src/linux |
87 |
* Unable to calculate Linux Kernel version for build, attempting to use running version |
88 |
* You must have CONFIG_KEYS to use this package! |
89 |
* Please check to make sure these options are set correctly. |
90 |
* Failure to do so may cause unexpected problems. |
91 |
|
92 |
* Messages for package sys-apps/busybox-1.24.1: |
93 |
|
94 |
* Could not locate user configfile, so we will save a default one |
95 |
* You cannot have USE='static pam'. Assuming static is more important. |
96 |
* Your configuration for sys-apps/busybox-1.24.1 has been saved in |
97 |
* /etc/portage/savedconfig/sys-apps/busybox-1.24.1 for your editing pleasure. |
98 |
* You can edit these files by hand and remerge this package with |
99 |
* USE=savedconfig to customise the configuration. |
100 |
* You can rename this file/directory to one of the following for |
101 |
* its configuration to apply to multiple versions: |
102 |
* ${PORTAGE_CONFIGROOT}/etc/portage/savedconfig/ |
103 |
* [${CTARGET}|${CHOST}|""]/${CATEGORY}/[${PF}|${P}|${PN}] |
104 |
|
105 |
* Messages for package app-misc/screen-4.3.1-r1: |
106 |
|
107 |
* Some dangerous key bindings have been removed or changed to more safe values. |
108 |
* We enable some xterm hacks in our default screenrc, which might break some |
109 |
* applications. Please check /etc/screenrc for information on these changes. |
110 |
* This revision changes the screen socket location to /tmp/screen |
111 |
|
112 |
* Messages for package sys-apps/openrc-0.19.1: |
113 |
|
114 |
* In this version of OpenRC, the loopback interface no longer |
115 |
* satisfies the net virtual. |
116 |
* If you have services now which do not start because of this, |
117 |
* They can be fixed by adding rc_need="!net" |
118 |
* to the /etc/conf.d/<servicename> file. |
119 |
* You should also file a bug against the service asking that |
120 |
* need net be dropped from the dependencies. |
121 |
* The bug you file should block the following tracker: |
122 |
* https://bugs.gentoo.org/show_bug.cgi?id=439092 |
123 |
* |
124 |
* Bug https://bugs.gentoo.org/show_bug.cgi?id=427996 was not |
125 |
* fixed correctly in earlier versions of OpenRC. |
126 |
* The correct fix is implemented in this version, but that |
127 |
* means netmount needs to be added to the default runlevel if |
128 |
* you are using nfs file systems. |
129 |
* |
130 |
* You should now update all files in /etc, using etc-update |
131 |
* or equivalent before restarting any services or this host. |
132 |
|
133 |
* Messages for package app-accessibility/brltty-5.2: |
134 |
|
135 |
* |
136 |
* please be sure /etc/brltty.conf is correct for your system. |
137 |
* |
138 |
* To make brltty start on boot, type this command as root: |
139 |
* |
140 |
* rc-update add brltty boot |
141 |
|
142 |
* Messages for package sys-power/acpid-2.0.23: |
143 |
|
144 |
* |
145 |
* You may wish to read the Gentoo Linux Power Management Guide, |
146 |
* which can be found online at: |
147 |
* https://www.gentoo.org/doc/en/power-management-guide.xml |
148 |
* |
149 |
|
150 |
* Messages for package dev-python/cryptography-1.0.2: |
151 |
|
152 |
* ERROR: dev-python/cryptography-1.0.2::gentoo failed (compile phase): |
153 |
* (no error message) |
154 |
* |
155 |
* Call stack: |
156 |
* ebuild.sh, line 133: Called src_compile |
157 |
* environment, line 3600: Called distutils-r1_src_compile |
158 |
* environment, line 916: Called _distutils-r1_run_foreach_impl 'distutils-r1_python_compile' |
159 |
* environment, line 337: Called python_foreach_impl 'distutils-r1_run_phase' 'distutils-r1_python_compile' |
160 |
* environment, line 3140: Called multibuild_foreach_variant '_python_multibuild_wrapper' 'distutils-r1_run_phase' 'distutils-r1_python_compile' |
161 |
* environment, line 2249: Called _multibuild_run '_python_multibuild_wrapper' 'distutils-r1_run_phase' 'distutils-r1_python_compile' |
162 |
* environment, line 2247: Called _python_multibuild_wrapper 'distutils-r1_run_phase' 'distutils-r1_python_compile' |
163 |
* environment, line 599: Called distutils-r1_run_phase 'distutils-r1_python_compile' |
164 |
* environment, line 907: Called distutils-r1_python_compile |
165 |
* environment, line 779: Called esetup.py 'build' |
166 |
* environment, line 1407: Called die |
167 |
* The specific snippet of code: |
168 |
* "${@}" || die "${die_args[@]}" || return ${?} |
169 |
* |
170 |
* If you need support, post the output of `emerge --info '=dev-python/cryptography-1.0.2::gentoo'`, |
171 |
* the complete build log and the output of `emerge -pqv '=dev-python/cryptography-1.0.2::gentoo'`. |
172 |
* The complete build log is located at '/var/tmp/portage/dev-python/cryptography-1.0.2/temp/build.log'. |
173 |
* The ebuild environment file is located at '/var/tmp/portage/dev-python/cryptography-1.0.2/temp/environment'. |
174 |
* Working directory: '/var/tmp/portage/dev-python/cryptography-1.0.2/work/cryptography-1.0.2' |
175 |
* S: '/var/tmp/portage/dev-python/cryptography-1.0.2/work/cryptography-1.0.2' |
176 |
|
177 |
!!! catalyst: Error in attempt to build packages |
178 |
|
179 |
|
180 |
Traceback (most recent call last): |
181 |
File "modules/generic_stage_target.py", line 1403, in build_packages |
182 |
"Error in attempt to build packages",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: livecdbuild 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 1408, in build_packages |
196 |
"build aborting due to error." |
197 |
CatalystError |
198 |
!!! catalyst: Error encountered during run of target livecd-stage1 |
199 |
Catalyst aborting.... |
200 |
lockfile does not exist '/home/catalyst/tmp/default/livecd-stage1-ia64-20160322/.catalyst_lock' |
201 |
|
202 |
|
203 |
|
204 |
Full build log at /tmp/catalyst-auto.kxHM6F/log/installcd-stage1.log |