1 |
* Linux kernels >=2.6.9 support memory locking for unprivileged processes. |
2 |
* The soft resource limit for memory locking specifies the limit an |
3 |
* unprivileged process may lock into memory. You can also use POSIX |
4 |
* capabilities to allow pinentry to lock memory. To do so activate the caps |
5 |
* USE flag and add the CAP_IPC_LOCK capability to the permitted set of |
6 |
* your users. |
7 |
* Messages for package app-accessibility/brltty-4.2: |
8 |
* |
9 |
* please be sure /etc/brltty.conf is correct for your system. |
10 |
* |
11 |
* To make brltty start on boot, type this command as root: |
12 |
* |
13 |
* rc-update add brltty boot |
14 |
* Messages for package app-misc/screen-4.0.3-r4: |
15 |
* Some dangerous key bindings have been removed or changed to more safe values. |
16 |
* We enable some xterm hacks in our default screenrc, which might break some |
17 |
* applications. Please check /etc/screenrc for information on these changes. |
18 |
* Messages for package net-dialup/rp-pppoe-3.8-r2: |
19 |
* Use pppoe-setup to configure your dialup connection. |
20 |
* Messages for package net-misc/ntp-4.2.6_p3: |
21 |
* You can find an example /etc/ntp.conf in /usr/share/ntp/ |
22 |
* Review /etc/ntp.conf to setup server info. |
23 |
* Review /etc/conf.d/ntpd to setup init.d info. |
24 |
* The way ntp sets and maintains your system time has changed. |
25 |
* Now you can use /etc/init.d/ntp-client to set your time at |
26 |
* boot while you can use /etc/init.d/ntpd to maintain your time |
27 |
* while your machine runs |
28 |
* Messages for package net-wireless/iwl3945-ucode-15.32.2.9: |
29 |
* |
30 |
* Due to ucode API change this version of ucode works only with kernels |
31 |
* >=2.6.29-rc1. If you have to use older kernels please install ucode |
32 |
* with older API: |
33 |
* emerge net-wireless/iwl3945-ucode:0 |
34 |
* For more information take a look at bugs.gentoo.org/246045 |
35 |
* |
36 |
* Messages for package net-wireless/iwl4965-ucode-228.61.2.24: |
37 |
* Due to ucode API change this version of ucode works only with kernels |
38 |
* >=2.6.27. If you need ucode for older versions please install it with |
39 |
* emerge net-wireless/iwl4965-ucode:0 |
40 |
* For more information take a look at bugs.gentoo.org/235007 |
41 |
* Messages for package sys-fs/mdadm-3.1.4: |
42 |
* If using baselayout-2 and not relying on kernel auto-detect |
43 |
* of your RAID devices, you need to add 'mdraid' to your 'boot' |
44 |
* runlevel. Run the following command: |
45 |
* rc-update add mdraid boot |
46 |
* Messages for package app-misc/livecd-tools-1.0.42: |
47 |
* This package is designed for use on the LiveCD only and will do |
48 |
* unspeakably horrible and unexpected things on a normal system. |
49 |
* YOU HAVE BEEN WARNED!!! |
50 |
* Messages for package sys-fs/lvm2-2.02.73-r1: |
51 |
* Unable to find kernel sources at /usr/src/linux |
52 |
* Unable to calculate Linux Kernel version for build, attempting to use running version |
53 |
* Building shared LVM, it will not work inside genkernel! |
54 |
* USE flag nocman is deprecated and replaced |
55 |
* with the cman USE flag. |
56 |
* |
57 |
* USE flags clvm and cman are masked |
58 |
* by default and need to be unmasked to use them |
59 |
* |
60 |
* If you are using genkernel and root-on-LVM, rebuild the initramfs. |
61 |
* lvm volumes are no longer automatically created for |
62 |
* baselayout-2 users. If you are using baselayout-2, be sure to |
63 |
* run: # rc-update add lvm boot |
64 |
* Do NOT add it if you are using baselayout-1 still. |
65 |
* Messages for package sys-apps/hwsetup-1.2-r1: |
66 |
* This package is designed for use on the LiveCD only and will do |
67 |
* unspeakably horrible and unexpected things on a normal system. |
68 |
* YOU HAVE BEEN WARNED!!! |
69 |
* This package is intended for usage on the Gentoo release media. If |
70 |
* you are not building a CD, remove this package. It will not work |
71 |
* properly on a running system, as Gentoo does not use any of the |
72 |
* Knoppix-style detection except for CD builds. |
73 |
* Messages for package app-crypt/gnupg-2.0.17: |
74 |
* If you wish to view images emerge: |
75 |
* media-gfx/xloadimage, media-gfx/xli or any other viewer |
76 |
* Remember to use photo-viewer option in configuration file to activate |
77 |
* the right viewer. |
78 |
* Please remember to restart gpg-agent if a different version |
79 |
* of the agent is currently used. If you are unsure of the gpg |
80 |
* agent you are using please run 'killall gpg-agent', |
81 |
* and to start a fresh daemon just run 'gpg-agent --daemon'. |
82 |
* Messages for package sys-fs/cryptsetup-1.1.3-r3: |
83 |
* Unable to find kernel sources at /usr/src/linux |
84 |
* Unable to calculate Linux Kernel version for build, attempting to use running version |
85 |
* This ebuild introduces a new set of scripts and configuration |
86 |
* than the last version. If you are currently using /etc/conf.d/cryptfs |
87 |
* then you *MUST* copy your old file to: |
88 |
* /etc/conf.d/dmcrypt |
89 |
* Or your encrypted partitions will *NOT* work. |
90 |
* Please see the example for configuring a LUKS mountpoint |
91 |
* in /etc/conf.d/dmcrypt |
92 |
* |
93 |
* If you are using baselayout-2 then please do: |
94 |
* rc-update add dmcrypt boot |
95 |
* This version introduces a command line arguement 'key_timeout'. |
96 |
* If you want the search for the removable key device to timeout |
97 |
* after 10 seconds add the following to your bootloader config: |
98 |
* key_timeout=10 |
99 |
* A timeout of 0 will mean it will wait indefinitely. |
100 |
* |
101 |
* Users using cryptsetup-1.0.x (dm-crypt plain) volumes must use |
102 |
* a compatibility mode when using cryptsetup-1.1.x. This can be |
103 |
* done by specifying the cipher (-c), key size (-s) and hash (-h). |
104 |
* For more info, see http://code.google.com/p/cryptsetup/wiki/FrequentlyAskedQuestions#6._Issues_with_Specific_Versions_of_cryptsetup |
105 |
* Messages for package sys-fs/dmraid-1.0.0_rc14: |
106 |
* Unable to find kernel sources at /usr/src/linux |
107 |
* Unable to calculate Linux Kernel version for build, attempting to use running version |
108 |
* DMRAID should be safe to use, but no warranties can be given |
109 |
* Messages for package app-admin/syslog-ng-3.1.4: |
110 |
* It is highly recommended that app-admin/logrotate be emerged to |
111 |
* manage the log files. syslog-ng installs a file in /etc/logrotate.d |
112 |
* for logrotate to use. |
113 |
* Messages for package sys-fs/evms-2.5.5-r11: |
114 |
* ERROR: sys-fs/evms-2.5.5-r11 failed (compile phase): |
115 |
* Failed emake |
116 |
* |
117 |
* Call stack: |
118 |
* ebuild.sh, line 56: Called src_compile |
119 |
* environment, line 3920: Called die |
120 |
* The specific snippet of code: |
121 |
* emake || die "Failed emake" |
122 |
* |
123 |
* If you need support, post the output of 'emerge --info =sys-fs/evms-2.5.5-r11', |
124 |
* the complete build log and the output of 'emerge -pqv =sys-fs/evms-2.5.5-r11'. |
125 |
* The complete build log is located at '/var/tmp/portage/sys-fs/evms-2.5.5-r11/temp/build.log'. |
126 |
* The ebuild environment file is located at '/var/tmp/portage/sys-fs/evms-2.5.5-r11/temp/environment'. |
127 |
* S: '/var/tmp/portage/sys-fs/evms-2.5.5-r11/work/evms-2.5.5' |
128 |
|
129 |
|
130 |
|
131 |
|
132 |
|
133 |
|
134 |
|
135 |
|
136 |
|
137 |
|
138 |
|
139 |
|
140 |
|
141 |
|
142 |
|
143 |
|
144 |
|
145 |
|
146 |
|
147 |
|
148 |
|
149 |
|
150 |
|
151 |
|
152 |
|
153 |
|
154 |
|
155 |
|
156 |
|
157 |
|
158 |
|
159 |
|
160 |
|
161 |
|
162 |
|
163 |
|
164 |
|
165 |
|
166 |
|
167 |
|
168 |
|
169 |
|
170 |
* Regenerating GNU info directory index... |
171 |
* Processed 90 info files. |
172 |
|
173 |
* IMPORTANT: 3 news items need reading for repository 'gentoo'. |
174 |
* Use eselect news to read news items. |
175 |
|
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 1362, in build_packages |
182 |
"Error in attempt to build packages",env=self.env) |
183 |
File "/usr/lib64/catalyst/modules/catalyst_support.py", line 542, 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/lib64/catalyst/catalyst", line 209, in build_target |
192 |
mytarget.run() |
193 |
File "modules/generic_stage_target.py", line 1263, in run |
194 |
apply(getattr(self,x)) |
195 |
File "modules/generic_stage_target.py", line 1367, 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 '/release/buildroot/x86-dev/tmp/default/livecd-stage1-x86-20110524/.catalyst_lock' |
201 |
|
202 |
|
203 |
|
204 |
Full build log at /tmp/catalyst-auto.14794/log/installcd-stage1.log |