Gentoo Archives: gentoo-releng-autobuilds

From: catalyst@×××××××××××××××××××××××××.org
To: releng@g.o, gentoo-releng-autobuilds@l.g.o
Subject: [gentoo-releng-autobuilds] [x86-auto] Catalyst fatal build error - hardened/stage3.spec
Date: Wed, 21 Mar 2012 12:09:15
Message-Id: 20120321120901.D4BE61436AF@poseidon.amd64.dev.gentoo.org
1 *
2 * mount options for directory /dev are no longer
3 * set in /etc/udev/udev.conf, but in /etc/fstab
4 * as for other directories.
5 *
6 * If you use /dev/md/*, /dev/loop/* or /dev/rd/*,
7 * then please migrate over to using the device names
8 * /dev/md*, /dev/loop* and /dev/ram*.
9 * The devfs-compat rules have been removed.
10 * For reference see Bug #269359.
11 *
12 * Rules for /dev/hd* devices have been removed
13 * Please migrate to libata.
14 *
15 * For more information on udev on Gentoo, writing udev rules, and
16 * fixing known issues visit:
17 * http://www.gentoo.org/doc/en/udev-guide.xml
18 * Messages for package sys-apps/coreutils-8.14:
19 * Make sure you run 'hash -r' in your active shells.
20 * You should also re-source your shell settings for LS_COLORS
21 * changes, such as: source /etc/profile
22 * Messages for package net-misc/wget-1.12-r3:
23 * The /etc/wget/wgetrc file has been relocated to /etc/wgetrc
24 * Messages for package sys-fs/e2fsprogs-1.42:
25 * No /etc/mtab file, creating one temporarily
26 * Messages for package sys-devel/gcc-4.5.3-r2:
27 * PT PaX marking -r
28 * /var/tmp/portage/sys-devel/gcc-4.5.3-r2/image//usr/libexec/gcc/i686-pc-linux-gnu/4.5.3/cc1
29 * PT PaX marking -r
30 * /var/tmp/portage/sys-devel/gcc-4.5.3-r2/image//usr/libexec/gcc/i686-pc-linux-gnu/4.5.3/cc1plus
31 * If you have issues with packages unable to locate libstdc++.la,
32 * then try running 'fix_libtool_files.sh' on the old gcc versions.
33 * You might want to review the GCC upgrade guide when moving between
34 * major versions (like 4.2 to 4.3):
35 * http://www.gentoo.org/doc/en/gcc-upgrading.xml
36 * Messages for package sys-apps/man-pages-3.35:
37 * If you don't have a makewhatis cronjob, then you
38 * should update the whatis database yourself:
39 * # makewhatis -u
40 * Messages for package sys-libs/pam-1.1.5:
41 * Some software with pre-loaded PAM libraries might experience
42 * warnings or failures related to missing symbols and/or versions
43 * after any update. While unfortunate this is a limit of the
44 * implementation of PAM and the software, and it requires you to
45 * restart the software manually after the update.
46 *
47 * You can get a list of such software running a command like
48 * lsof / | egrep -i 'del.*libpam\.so'
49 *
50 * Alternatively, simply reboot your system.
51 * Messages for package sys-auth/pambase-20101024-r2:
52 * Starting from version 20080801, pambase optionally enables
53 * SHA512-hashed passwords. For this to work, you need sys-libs/pam-1.0.1
54 * built against sys-libs/glibc-2.7 or later.
55 * If you don't have support for this, it will automatically fallback
56 * to MD5-hashed passwords, just like before.
57 *
58 * Please note that the change only affects the newly-changed passwords
59 * and that SHA512-hashed passwords will not work on earlier versions
60 * of glibc or Linux-PAM.
61 * Messages for package sys-apps/busybox-1.19.3-r1:
62 * Could not locate user configfile, so we will save a default one
63 * Your configuration for sys-apps/busybox-1.19.3-r1 has been saved in
64 * /etc/portage/savedconfig/sys-apps/busybox-1.19.3-r1 for your editing pleasure.
65 * You can edit these files by hand and remerge this package with
66 * USE=savedconfig to customise the configuration.
67 * You can rename this file/directory to one of the following for
68 * its configuration to apply to multiple versions:
69 * ${PORTAGE_CONFIGROOT}/etc/portage/savedconfig/
70 * [${CTARGET}|${CHOST}|""]/${CATEGORY}/[${PF}|${P}|${PN}]
71 * This ebuild has support for user defined configs
72 * Please read this ebuild for more details and re-emerge as needed
73 * if you want to add or remove functionality for busybox
74 * Messages for package net-misc/openssh-5.8_p1-r1:
75 * Starting with openssh-5.8p1, the server will default to a newer key
76 * algorithm (ECDSA). You are encouraged to manually update your stored
77 * keys list as servers update theirs. See ssh-keyscan(1) for more info.
78 * Remember to merge your config files in /etc/ssh/ and then
79 * reload sshd: '/etc/init.d/sshd reload'.
80 * Please be aware users need a valid shell in /etc/passwd
81 * in order to be allowed to login.
82 * Messages for package sys-apps/openrc-0.9.8.4:
83 * You should now update all files in /etc, using etc-update
84 * or equivalent before restarting any services or this host.
85 *
86 * Please read the migration guide available at:
87 * http://www.gentoo.org/doc/en/openrc-migration.xml
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126 removing /release/buildroot/x86-dev/tmp/hardened/stage3-i686-hardened-20120320/tmp/chroot-functions.sh from the chroot
127 --- Running action sequence: preclean
128 copying stage3-preclean-chroot.sh to /release/buildroot/x86-dev/tmp/hardened/stage3-i686-hardened-20120320/tmp/
129 copying chroot-functions.sh to /release/buildroot/x86-dev/tmp/hardened/stage3-i686-hardened-20120320/tmp/
130 Running stage3-preclean-chroot.sh in chroot /release/buildroot/x86-dev/tmp/hardened/stage3-i686-hardened-20120320/
131 >>> Regenerating /etc/ld.so.cache...
132 emerge --depclean --with-bdeps=n
133 !!! CONFIG_PROTECT is empty
134
135 * Depclean may break link level dependencies. Thus, it is
136 * recommended to use a tool such as `revdep-rebuild` (from
137 * app-portage/gentoolkit) in order to detect such breakage.
138 *
139 * Always study the list of packages to be cleaned for any obvious
140 * mistakes. Packages that are part of the world set will always
141 * be kept. They can be manually added to this set with
142 * `emerge --noreplace <atom>`. Packages that are listed in
143 * package.provided (see portage(5)) will be removed by
144 * depclean, even if they are part of the world set.
145 *
146 * As a safety measure, depclean will not remove any packages
147 * unless *all* required dependencies have been resolved. As a
148 * consequence, it is often necessary to run `emerge --update
149 * --newuse --deep @world` prior to depclean.
150 !!! You have no world file.
151 !!! Proceeding is likely to break your installation.
152
153 Calculating dependencies ... done!
154 * Dependencies could not be completely resolved due to
155 * the following required packages not being installed:
156 *
157 * >=sys-libs/ncurses-5.2[unicode] pulled in by:
158 * app-editors/nano-2.2.5
159 *
160 * Have you forgotten to do a complete update prior to depclean? The
161 * most comprehensive command for this purpose is as follows:
162 *
163 * emerge --update --newuse --deep --with-bdeps=y @world
164 *
165 * Note that the --with-bdeps=y option is not required in many
166 * situations. Refer to the emerge manual page (run `man emerge`)
167 * for more information about --with-bdeps.
168 *
169 * Also, note that it may be necessary to manually uninstall
170 * packages that no longer exist in the portage tree, since it may
171 * not be possible to satisfy their dependencies.
172
173 * IMPORTANT: 2 news items need reading for repository 'gentoo'.
174 * Use eselect news to read news items.
175
176
177 !!! catalyst: preclean script failed.
178
179
180 Traceback (most recent call last):
181 File "modules/generic_stage_target.py", line 1167, in preclean
182 " preclean","preclean script failed.",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: Build failed, could not execute preclean
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 1172, in preclean
196 raise CatalystError, "Build failed, could not execute preclean"
197 CatalystError
198 !!! catalyst: Error encountered during run of target stage3
199 Catalyst aborting....
200 lockfile does not exist '/release/buildroot/x86-dev/tmp/hardened/stage3-i686-hardened-20120320/.catalyst_lock'
201
202
203
204 Full build log at /tmp/catalyst-auto.1912/log/hardened_stage3.log