From: catalyst@lantean.jmbsvicetto.name
To: jmbsvicetto@gmail.com,gentoo-releng-autobuilds@lists.gentoo.org
Subject: [gentoo-releng-autobuilds] [amd64-auto] Catalyst non-fatal build error - installcd-stage1.spec
Date: Mon, 22 Dec 2014 06:39:16 +0000 (UTC) [thread overview]
Message-ID: <20141222063916.85B61E006A@lantean.jmbsvicetto.name> (raw)
checking util/locker.h usability... no
checking util/locker.h presence... no
checking for util/locker.h... no
checking util/application.h usability... no
checking util/application.h presence... no
checking for util/application.h... no
checking for libpng >= 1.0.0... yes
checking LIBPNG_CFLAGS... -I/usr/include/libpng16
checking LIBPNG_LIBS... -lpng16
checking png.h usability... yes
checking png.h presence... yes
checking for png.h... yes
checking libpng/png.h usability... no
checking libpng/png.h presence... no
checking for libpng/png.h... no
checking for png_create_info_struct... yes
checking for png_set_rgb_to_gray... yes
checking for png_get_libpng_ver... yes
checking for png_get_image_width... yes
checking for png_get_image_height... yes
checking for png_get_gAMA... yes
checking for png_get_color_type... yes
checking for png_get_bit_depth... yes
checking for png_set_strip_alpha... yes
checking for png_get_valid... yes
checking for png_get_sRGB... yes
checking if you can include both setjmp.h and png.h... yes
checking jpeglib.h usability... yes
checking jpeglib.h presence... yes
checking for jpeglib.h... yes
checking for jpeg_destroy_decompress in -ljpeg... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating config.h
---------------------------------------------------------
Configuration results:
IPv6: YES
Supported compression: ZLIB BZIP2
SSL support: OPENSSL
UTF-8 terminal: YES
GPM support: YES
Graphics enabled: YES
Graphics drivers: FB
Image formats: GIF PNG XBM JPEG
---------------------------------------------------------
Makefile:465: *** missing separator. Stop.
* ERROR: www-client/links-2.8-r1::gentoo failed (compile phase):
* emake failed
*
* If you need support, post the output of `emerge --info '=www-client/links-2.8-r1::gentoo'`,
* the complete build log and the output of `emerge -pqv '=www-client/links-2.8-r1::gentoo'`.
* The complete build log is located at '/var/log/portage/www-client:links-2.8-r1:20141222-063852.log'.
* For convenience, a symlink to the build log is located at '/var/tmp/portage/www-client/links-2.8-r1/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/www-client/links-2.8-r1/temp/environment'.
* Working directory: '/var/tmp/portage/www-client/links-2.8-r1/work/links-2.8'
* S: '/var/tmp/portage/www-client/links-2.8-r1/work/links-2.8'
* Messages for package net-misc/vconfig-1.9:
* MTU problems exist for many ethernet drivers.
* Reduce the MTU on the interface to 1496 to work around them.
* Messages for package sys-apps/keyutils-1.5.9-r1:
* Unable to find kernel sources at /usr/src/linux
* Unable to calculate Linux Kernel version for build, attempting to use running version
* Messages for package net-fs/cifs-utils-6.1-r1:
* Unable to find kernel sources at /usr/src/linux
* Unable to calculate Linux Kernel version for build, attempting to use running version
* You must enable CIFS support in your kernel config,
* to be able to mount samba shares. You can find it at
*
* File systems
* Network File Systems
* CIFS support
*
* and recompile your kernel ...
* setuid use flag was dropped due to multiple security implications
* such as CVE-2009-2948, CVE-2011-3585 and CVE-2012-1586
* You are free to set setuid flags by yourself
* Messages for package net-dialup/ppp-2.4.7:
* Unable to find kernel sources at /usr/src/linux
* Unable to calculate Linux Kernel version for build, attempting to use running version
* Pon, poff and plog scripts have been supplied for experienced users.
* Users needing particular scripts (ssh,rsh,etc.) should check out the
* /usr/share/doc/ppp-2.4.7/scripts directory.
* Messages for package app-misc/screen-4.0.3-r6:
* Some dangerous key bindings have been removed or changed to more safe values.
* We enable some xterm hacks in our default screenrc, which might break some
* applications. Please check /etc/screenrc for information on these changes.
* Messages for package net-dialup/rp-pppoe-3.8-r2:
* Use pppoe-setup to configure your dialup connection.
* Messages for package sys-apps/busybox-1.21.0:
* Could not locate user configfile, so we will save a default one
* You cannot have USE='static pam'. Assuming static is more important.
* Your configuration for sys-apps/busybox-1.21.0 has been saved in
* /etc/portage/savedconfig/sys-apps/busybox-1.21.0 for your editing pleasure.
* You can edit these files by hand and remerge this package with
* USE=savedconfig to customise the configuration.
* You can rename this file/directory to one of the following for
* its configuration to apply to multiple versions:
* ${PORTAGE_CONFIGROOT}/etc/portage/savedconfig/
* [${CTARGET}|${CHOST}|""]/${CATEGORY}/[${PF}|${P}|${PN}]
* Messages for package sys-fs/fuse-2.9.3:
* Unable to find kernel sources at /usr/src/linux
* Unable to calculate Linux Kernel version for build, attempting to use running version
* Messages for package app-accessibility/brltty-5.0-r3:
*
* please be sure /etc/brltty.conf is correct for your system.
*
* To make brltty start on boot, type this command as root:
*
* rc-update add brltty boot
* Messages for package app-admin/hddtemp-0.3_beta15-r7:
* In order to update your hddtemp database, run:
* emerge --config =app-admin/hddtemp-0.3_beta15-r7
*
* If your hard drive is not recognized by hddtemp, please consider
* submitting your HDD info for inclusion into the Gentoo hddtemp
* database by filing a bug at https://bugs.gentoo.org/
*
* If hddtemp complains but finds your HDD temperature sensor, use the
* --quiet option to suppress the warning.
*
* (Note: Above message is only printed the first time package is
* installed. Please look at /usr/share/doc/hddtemp-0.3_beta15-r7/README.gentoo*
* for future reference)
* Messages for package sys-power/acpid-2.0.20:
*
* You may wish to read the Gentoo Linux Power Management Guide,
* which can be found online at:
* http://www.gentoo.org/doc/en/power-management-guide.xml
*
* Messages for package net-misc/ntp-4.2.6_p5-r10:
* You can find an example /etc/ntp.conf in /usr/share/ntp/
* Review /etc/ntp.conf to setup server info.
* Review /etc/conf.d/ntpd to setup init.d info.
* The way ntp sets and maintains your system time has changed.
* Now you can use /etc/init.d/ntp-client to set your time at
* boot while you can use /etc/init.d/ntpd to maintain your time
* while your machine runs
* Messages for package www-client/links-2.8-r1:
* ERROR: www-client/links-2.8-r1::gentoo failed (compile phase):
* emake failed
*
* If you need support, post the output of `emerge --info '=www-client/links-2.8-r1::gentoo'`,
* the complete build log and the output of `emerge -pqv '=www-client/links-2.8-r1::gentoo'`.
* The complete build log is located at '/var/log/portage/www-client:links-2.8-r1:20141222-063852.log'.
* For convenience, a symlink to the build log is located at '/var/tmp/portage/www-client/links-2.8-r1/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/www-client/links-2.8-r1/temp/environment'.
* Working directory: '/var/tmp/portage/www-client/links-2.8-r1/work/links-2.8'
* S: '/var/tmp/portage/www-client/links-2.8-r1/work/links-2.8'
!!! catalyst: Error in attempt to build packages
Traceback (most recent call last):
File "modules/generic_stage_target.py", line 1403, in build_packages
"Error in attempt to build packages",env=self.env)
File "/usr/lib64/catalyst//modules/catalyst_support.py", line 541, in cmd
raise CatalystError,myexc
CatalystError
None
!!! catalyst: livecdbuild aborting due to error.
Traceback (most recent call last):
File "/usr/lib64/catalyst/catalyst", line 218, in build_target
mytarget.run()
File "modules/generic_stage_target.py", line 1304, in run
apply(getattr(self,x))
File "modules/generic_stage_target.py", line 1408, in build_packages
"build aborting due to error."
CatalystError
!!! catalyst: Error encountered during run of target livecd-stage1
Catalyst aborting....
lockfile does not exist '/home/release/buildroot/amd64-dev/tmp/default/livecd-stage1-amd64-20141222/.catalyst_lock'
Full build log at /home/release/tmp/run/catalyst-auto.nVs7sb/log/installcd-stage1.log
next reply other threads:[~2014-12-22 6:39 UTC|newest]
Thread overview: 126+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-22 6:39 catalyst [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-14 7:26 [gentoo-releng-autobuilds] [amd64-auto] Catalyst non-fatal build error - installcd-stage1.spec catalyst
2023-01-15 18:29 catalyst
2022-03-06 18:16 catalyst
2021-07-10 20:31 catalyst
2020-05-11 22:35 catalyst
2020-04-23 3:28 catalyst
2020-04-16 3:21 catalyst
2020-04-13 4:16 catalyst
2020-01-13 2:51 catalyst
2019-05-30 11:23 catalyst
2019-05-30 2:20 catalyst
2019-05-29 12:28 catalyst
2019-05-27 5:50 catalyst
2019-05-23 2:20 catalyst
2018-12-07 1:26 catalyst
2018-06-15 23:30 catalyst
2018-06-15 1:12 catalyst
2018-06-13 1:09 catalyst
2018-06-11 1:04 catalyst
2018-06-08 1:07 catalyst
2018-06-06 1:09 catalyst
2018-06-04 2:11 catalyst
2018-06-01 1:19 catalyst
2018-05-30 1:12 catalyst
2018-05-28 5:11 catalyst
2018-05-28 1:10 catalyst
2018-05-25 1:12 catalyst
2018-05-23 1:24 catalyst
2018-05-21 5:11 catalyst
2018-05-18 1:14 catalyst
2018-05-16 1:33 catalyst
2018-05-14 5:18 catalyst
2018-05-14 1:18 catalyst
2018-05-11 1:11 catalyst
2018-05-09 1:16 catalyst
2018-05-07 5:10 catalyst
2018-05-07 1:12 catalyst
2018-05-04 1:13 catalyst
2018-05-02 1:12 catalyst
2018-04-30 5:10 catalyst
2018-04-30 1:15 catalyst
2018-04-27 1:10 catalyst
2018-04-24 22:30 catalyst
2018-04-23 5:22 catalyst
2017-12-07 0:22 catalyst
2017-12-06 12:45 catalyst
2017-12-05 0:29 catalyst
2017-12-04 7:05 catalyst
2017-11-30 6:35 catalyst
2017-11-27 7:12 catalyst
2017-11-23 7:25 catalyst
2017-11-20 7:55 catalyst
2017-11-16 6:30 catalyst
2017-11-13 6:48 catalyst
2017-11-09 6:16 catalyst
2017-11-06 6:55 catalyst
2017-11-02 6:21 catalyst
2017-10-30 6:57 catalyst
2017-10-26 6:12 catalyst
2017-10-23 7:21 catalyst
2017-10-19 6:15 catalyst
2017-10-16 7:22 catalyst
2017-10-12 6:12 catalyst
2017-10-09 7:32 catalyst
2017-10-05 6:21 catalyst
2017-04-03 7:30 catalyst
2017-03-06 7:45 catalyst
2017-03-04 19:40 catalyst
2016-12-22 6:06 catalyst
2016-12-15 5:42 catalyst
2016-07-11 6:25 catalyst
2016-07-04 6:21 catalyst
2016-06-27 6:17 catalyst
2016-06-20 6:16 catalyst
2016-06-13 6:24 catalyst
2016-06-06 6:12 catalyst
2016-05-23 13:17 catalyst
2016-05-22 13:15 catalyst
2016-05-21 13:16 catalyst
2016-05-20 13:17 catalyst
2016-05-18 13:17 catalyst
2016-05-16 13:17 catalyst
2016-05-15 13:15 catalyst
2016-05-14 13:15 catalyst
2016-05-13 13:17 catalyst
2016-05-11 13:17 catalyst
2016-05-09 13:17 catalyst
2016-05-08 13:17 catalyst
2016-05-06 13:17 catalyst
2016-05-04 13:17 catalyst
2016-05-02 13:17 catalyst
2016-05-01 13:15 catalyst
2016-04-30 13:17 catalyst
2016-04-29 13:16 catalyst
2016-04-21 5:27 catalyst
2016-01-11 6:55 catalyst
2016-01-07 5:16 catalyst
2015-08-03 7:26 catalyst
2015-07-23 5:22 catalyst
2015-07-16 5:03 catalyst
2015-02-26 4:50 catalyst
2015-02-20 4:28 catalyst
2015-01-19 6:06 catalyst
2014-09-18 5:27 catalyst
2014-09-15 5:44 catalyst
2014-09-11 5:29 catalyst
2014-09-08 5:28 catalyst
2014-07-31 6:59 catalyst
2014-05-01 5:38 catalyst
2014-04-10 6:42 catalyst
2012-05-03 12:45 catalyst
2012-04-26 12:40 catalyst
2012-04-19 12:39 catalyst
2012-04-12 12:38 catalyst
2012-04-05 12:31 catalyst
2012-03-29 12:32 catalyst
2012-03-22 12:19 catalyst
2012-03-15 12:23 catalyst
2012-03-08 12:21 catalyst
2012-03-01 12:22 catalyst
2011-05-26 15:52 catalyst
2011-05-21 10:46 catalyst
2011-04-28 12:57 catalyst
2011-04-07 12:46 catalyst
2011-01-27 11:57 catalyst
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20141222063916.85B61E006A@lantean.jmbsvicetto.name \
--to=catalyst@lantean.jmbsvicetto.name \
--cc=gentoo-releng-autobuilds@lists.gentoo.org \
--cc=jmbsvicetto@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox