From: catalyst@nightheron.gentoo.org
To: releng@gentoo.org,gentoo-releng-autobuilds@lists.gentoo.org
Subject: [gentoo-releng-autobuilds] [x86-auto] Catalyst non-fatal build error - installcd-stage1.spec
Date: Tue, 9 Sep 2014 04:44:02 +0000 (UTC) [thread overview]
Message-ID: <20140909044402.549F52421C@nightheron.gentoo.org> (raw)
make[2]: Nothing to be done for `install-data-am'.
/bin/mkdir -p '/var/tmp/portage/net-proxy/dante-1.4.0-r2/image//usr/sbin'
/bin/sh ../libtool --mode=install /usr/bin/install -c sockd '/var/tmp/portage/net-proxy/dante-1.4.0-r2/image//usr/sbin'
libtool: install: /usr/bin/install -c sockd /var/tmp/portage/net-proxy/dante-1.4.0-r2/image//usr/sbin/sockd
make[2]: Leaving directory `/var/tmp/portage/net-proxy/dante-1.4.0-r2/work/dante-1.4.0/sockd'
make[1]: Leaving directory `/var/tmp/portage/net-proxy/dante-1.4.0-r2/work/dante-1.4.0/sockd'
Making install in unlicensed
make[1]: Entering directory `/var/tmp/portage/net-proxy/dante-1.4.0-r2/work/dante-1.4.0/unlicensed'
make[2]: Entering directory `/var/tmp/portage/net-proxy/dante-1.4.0-r2/work/dante-1.4.0/unlicensed'
make[2]: Nothing to be done for `install-exec-am'.
make[2]: Nothing to be done for `install-data-am'.
make[2]: Leaving directory `/var/tmp/portage/net-proxy/dante-1.4.0-r2/work/dante-1.4.0/unlicensed'
make[1]: Leaving directory `/var/tmp/portage/net-proxy/dante-1.4.0-r2/work/dante-1.4.0/unlicensed'
Making install in example
make[1]: Entering directory `/var/tmp/portage/net-proxy/dante-1.4.0-r2/work/dante-1.4.0/example'
make[2]: Entering directory `/var/tmp/portage/net-proxy/dante-1.4.0-r2/work/dante-1.4.0/example'
make[2]: Nothing to be done for `install-exec-am'.
make[2]: Nothing to be done for `install-data-am'.
make[2]: Leaving directory `/var/tmp/portage/net-proxy/dante-1.4.0-r2/work/dante-1.4.0/example'
make[1]: Leaving directory `/var/tmp/portage/net-proxy/dante-1.4.0-r2/work/dante-1.4.0/example'
Making install in doc
make[1]: Entering directory `/var/tmp/portage/net-proxy/dante-1.4.0-r2/work/dante-1.4.0/doc'
make[2]: Entering directory `/var/tmp/portage/net-proxy/dante-1.4.0-r2/work/dante-1.4.0/doc'
make[2]: Nothing to be done for `install-exec-am'.
/bin/mkdir -p '/var/tmp/portage/net-proxy/dante-1.4.0-r2/image//usr/share/man/man1'
/bin/mkdir -p '/var/tmp/portage/net-proxy/dante-1.4.0-r2/image//usr/share/man/man5'
/bin/mkdir -p '/var/tmp/portage/net-proxy/dante-1.4.0-r2/image//usr/share/man/man8'
/usr/bin/install -c -m 644 socksify.1 '/var/tmp/portage/net-proxy/dante-1.4.0-r2/image//usr/share/man/man1'
/usr/bin/install -c -m 644 sockd.8 '/var/tmp/portage/net-proxy/dante-1.4.0-r2/image//usr/share/man/man8'
/usr/bin/install -c -m 644 sockd.conf.5 socks.conf.5 '/var/tmp/portage/net-proxy/dante-1.4.0-r2/image//usr/share/man/man5'
make[2]: Leaving directory `/var/tmp/portage/net-proxy/dante-1.4.0-r2/work/dante-1.4.0/doc'
make[1]: Leaving directory `/var/tmp/portage/net-proxy/dante-1.4.0-r2/work/dante-1.4.0/doc'
Making install in bin
make[1]: Entering directory `/var/tmp/portage/net-proxy/dante-1.4.0-r2/work/dante-1.4.0/bin'
make[2]: Entering directory `/var/tmp/portage/net-proxy/dante-1.4.0-r2/work/dante-1.4.0/bin'
make[2]: Nothing to be done for `install-data-am'.
/bin/mkdir -p '/var/tmp/portage/net-proxy/dante-1.4.0-r2/image//usr/bin'
/usr/bin/install -c socksify '/var/tmp/portage/net-proxy/dante-1.4.0-r2/image//usr/bin'
make[2]: Leaving directory `/var/tmp/portage/net-proxy/dante-1.4.0-r2/work/dante-1.4.0/bin'
make[1]: Leaving directory `/var/tmp/portage/net-proxy/dante-1.4.0-r2/work/dante-1.4.0/bin'
Making install in SPECS
make[1]: Entering directory `/var/tmp/portage/net-proxy/dante-1.4.0-r2/work/dante-1.4.0/SPECS'
make[2]: Entering directory `/var/tmp/portage/net-proxy/dante-1.4.0-r2/work/dante-1.4.0/SPECS'
make[2]: Nothing to be done for `install-exec-am'.
make[2]: Nothing to be done for `install-data-am'.
make[2]: Leaving directory `/var/tmp/portage/net-proxy/dante-1.4.0-r2/work/dante-1.4.0/SPECS'
make[1]: Leaving directory `/var/tmp/portage/net-proxy/dante-1.4.0-r2/work/dante-1.4.0/SPECS'
Making install in capi
make[1]: Entering directory `/var/tmp/portage/net-proxy/dante-1.4.0-r2/work/dante-1.4.0/capi'
make[2]: Entering directory `/var/tmp/portage/net-proxy/dante-1.4.0-r2/work/dante-1.4.0/capi'
make[2]: Nothing to be done for `install-exec-am'.
/bin/mkdir -p '/var/tmp/portage/net-proxy/dante-1.4.0-r2/image//usr/include'
/usr/bin/install -c -m 644 socks.h '/var/tmp/portage/net-proxy/dante-1.4.0-r2/image//usr/include'
make[2]: Leaving directory `/var/tmp/portage/net-proxy/dante-1.4.0-r2/work/dante-1.4.0/capi'
make[1]: Leaving directory `/var/tmp/portage/net-proxy/dante-1.4.0-r2/work/dante-1.4.0/capi'
Making install in contrib
make[1]: Entering directory `/var/tmp/portage/net-proxy/dante-1.4.0-r2/work/dante-1.4.0/contrib'
make[2]: Entering directory `/var/tmp/portage/net-proxy/dante-1.4.0-r2/work/dante-1.4.0/contrib'
make[2]: Nothing to be done for `install-exec-am'.
make[2]: Nothing to be done for `install-data-am'.
make[2]: Leaving directory `/var/tmp/portage/net-proxy/dante-1.4.0-r2/work/dante-1.4.0/contrib'
make[1]: Leaving directory `/var/tmp/portage/net-proxy/dante-1.4.0-r2/work/dante-1.4.0/contrib'
make[1]: Entering directory `/var/tmp/portage/net-proxy/dante-1.4.0-r2/work/dante-1.4.0'
make[2]: Entering directory `/var/tmp/portage/net-proxy/dante-1.4.0-r2/work/dante-1.4.0'
make[2]: Nothing to be done for `install-exec-am'.
make[2]: Nothing to be done for `install-data-am'.
make[2]: Leaving directory `/var/tmp/portage/net-proxy/dante-1.4.0-r2/work/dante-1.4.0'
make[1]: Leaving directory `/var/tmp/portage/net-proxy/dante-1.4.0-r2/work/dante-1.4.0'
install: cannot stat '/usr/portage/net-proxy/dante/files/sock?.conf': No such file or directory
!!! doins: /usr/portage/net-proxy/dante/files/sock?.conf does not exist
* ERROR: net-proxy/dante-1.4.0-r2::gentoo failed (install phase):
* doins failed
*
* If you need support, post the output of `emerge --info '=net-proxy/dante-1.4.0-r2::gentoo'`,
* the complete build log and the output of `emerge -pqv '=net-proxy/dante-1.4.0-r2::gentoo'`.
* The complete build log is located at '/var/tmp/portage/net-proxy/dante-1.4.0-r2/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/net-proxy/dante-1.4.0-r2/temp/environment'.
* Working directory: '/var/tmp/portage/net-proxy/dante-1.4.0-r2/work/dante-1.4.0'
* S: '/var/tmp/portage/net-proxy/dante-1.4.0-r2/work/dante-1.4.0'
* QA Notice: file does not exist:
*
* doins: /usr/portage/net-proxy/dante/files/sock?.conf does not exist
* Messages for package sys-libs/timezone-data-2014f:
* You do not have TIMEZONE set in /etc/timezone.
* Skipping auto-update of /etc/localtime.
* 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 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 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 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 sys-apps/openrc-0.12.4:
* In this version of OpenRC, the loopback interface no longer
* satisfies the net virtual.
* If you have services now which do not start because of this,
* They can be fixed by adding rc_need="!net"
* to the /etc/conf.d/<servicename> file.
* You should also file a bug against the service asking that
* need net be dropped from the dependencies.
* The bug you file should block the following tracker:
* https://bugs.gentoo.org/show_bug.cgi?id=439092
* This version of OpenRC doesn't enable nfs mounts automatically any
* longer. In order to mount nfs file systems, you must use the
* nfsmount service from the nfs-utils package.
* See bug https://bugs.gentoo.org/show_bug.cgi?id=427996 for
* more information on this.
* You should now update all files in /etc, using etc-update
* or equivalent before restarting any services or this host.
* Messages for package net-proxy/dante-1.4.0-r2:
* ERROR: net-proxy/dante-1.4.0-r2::gentoo failed (install phase):
* doins failed
*
* If you need support, post the output of `emerge --info '=net-proxy/dante-1.4.0-r2::gentoo'`,
* the complete build log and the output of `emerge -pqv '=net-proxy/dante-1.4.0-r2::gentoo'`.
* The complete build log is located at '/var/tmp/portage/net-proxy/dante-1.4.0-r2/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/net-proxy/dante-1.4.0-r2/temp/environment'.
* Working directory: '/var/tmp/portage/net-proxy/dante-1.4.0-r2/work/dante-1.4.0'
* S: '/var/tmp/portage/net-proxy/dante-1.4.0-r2/work/dante-1.4.0'
!!! 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 '/release/buildroot/x86-dev/tmp/default/livecd-stage1-x86-20140909/.catalyst_lock'
Full build log at /release/tmp/run/catalyst-auto.24694/log/installcd-stage1.log
next reply other threads:[~2014-09-09 5:19 UTC|newest]
Thread overview: 87+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-09 4:44 catalyst [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-05-13 21:49 [gentoo-releng-autobuilds] [x86-auto] Catalyst non-fatal build error - installcd-stage1.spec catalyst
2019-05-29 5:13 catalyst
2018-12-08 0:48 catalyst
2018-12-05 4:41 catalyst
2018-07-11 4:38 catalyst
2018-06-14 0:05 catalyst
2018-06-12 0:03 catalyst
2018-06-09 0:27 catalyst
2018-06-07 0:07 catalyst
2018-06-05 0:09 catalyst
2018-06-02 0:04 catalyst
2018-05-31 0:11 catalyst
2018-05-30 4:25 catalyst
2018-05-29 0:07 catalyst
2018-05-26 0:03 catalyst
2018-05-24 0:05 catalyst
2018-05-23 4:24 catalyst
2018-05-17 0:04 catalyst
2018-05-16 4:32 catalyst
2018-05-15 0:22 catalyst
2018-05-12 0:02 catalyst
2018-05-10 0:05 catalyst
2018-05-09 4:24 catalyst
2018-05-08 0:05 catalyst
2018-05-05 0:03 catalyst
2018-05-03 0:03 catalyst
2018-05-02 4:22 catalyst
2018-05-01 0:01 catalyst
2018-04-28 0:05 catalyst
2018-04-26 0:05 catalyst
2018-04-25 4:38 catalyst
2018-04-24 0:56 catalyst
2017-12-06 7:09 catalyst
2017-11-29 7:06 catalyst
2017-11-28 6:03 catalyst
2017-11-22 7:42 catalyst
2017-11-21 6:46 catalyst
2017-11-15 6:55 catalyst
2017-11-14 5:52 catalyst
2017-11-08 6:56 catalyst
2017-11-07 5:53 catalyst
2017-11-01 6:59 catalyst
2017-10-31 5:43 catalyst
2017-10-26 3:25 catalyst
2017-10-24 5:49 catalyst
2017-10-17 5:44 catalyst
2017-10-11 7:10 catalyst
2017-10-10 5:47 catalyst
2017-10-04 7:25 catalyst
2017-10-03 5:44 catalyst
2016-12-20 5:11 catalyst
2016-07-19 5:47 catalyst
2016-07-13 8:19 catalyst
2016-07-12 6:00 catalyst
2016-07-06 6:20 catalyst
2016-07-05 5:55 catalyst
2016-06-29 6:22 catalyst
2016-06-28 5:53 catalyst
2016-06-22 6:11 catalyst
2016-06-15 6:19 catalyst
2016-06-08 6:11 catalyst
2016-01-13 7:29 catalyst
2016-01-12 4:41 catalyst
2015-12-29 6:00 catalyst
2015-07-21 4:56 catalyst
2015-03-11 6:51 catalyst
2015-02-24 4:25 catalyst
2014-08-27 5:36 catalyst
2014-06-03 5:40 catalyst
2012-09-11 19:11 catalyst
2012-08-21 13:10 catalyst
2012-05-08 13:33 catalyst
2012-05-01 13:28 catalyst
2012-04-24 13:29 catalyst
2012-04-17 13:21 catalyst
2012-04-10 13:22 catalyst
2012-04-03 13:23 catalyst
2012-03-27 13:16 catalyst
2012-03-20 13:07 catalyst
2012-03-13 13:03 catalyst
2011-08-30 12:23 catalyst
2011-05-31 15:38 catalyst
2011-05-24 13:27 catalyst
2011-05-03 12:25 catalyst
2011-04-05 11:09 catalyst
2011-01-25 10:49 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=20140909044402.549F52421C@nightheron.gentoo.org \
--to=catalyst@nightheron.gentoo.org \
--cc=gentoo-releng-autobuilds@lists.gentoo.org \
--cc=releng@gentoo.org \
/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