public inbox for gentoo-releng-autobuilds@lists.gentoo.org
 help / color / mirror / Atom feed
From: catalyst@guppy.ia64.dev.gentoo.org
To: releng@gentoo.org,gentoo-releng-autobuilds@lists.gentoo.org
Subject: [gentoo-releng-autobuilds] [ia64-auto] Catalyst fatal build error - stage3.spec
Date: Tue, 26 Jan 2016 12:48:04 +0000	[thread overview]
Message-ID: <20160126124809.29BDCE0857@pigeon.gentoo.org> (raw)




/var/tmp/portage/sys-fs/udev-225/work/systemd-225/src/basic/missing.h:1023:24: error: '__NR_kcmp' undeclared (first use in this function)
         return syscall(__NR_kcmp, pid1, pid2, type, idx1, idx2);
                        ^
/var/tmp/portage/sys-fs/udev-225/work/systemd-225/src/basic/missing.h:1023:24: note: each undeclared identifier is reported only once for each function it appears in
Makefile:13318: recipe for target 'src/libudev/libudev-list.lo' failed
make: *** [src/libudev/libudev-list.lo] Error 1
make: *** Waiting for unfinished jobs....
In file included from /var/tmp/portage/sys-fs/udev-225/work/systemd-225/src/basic/util.h:46:0,
                 from /var/tmp/portage/sys-fs/udev-225/work/systemd-225/src/libsystemd/sd-device/device-util.h:24,
                 from /var/tmp/portage/sys-fs/udev-225/work/systemd-225/src/libudev/libudev-device.c:38:
/var/tmp/portage/sys-fs/udev-225/work/systemd-225/src/basic/missing.h: In function 'kcmp':
/var/tmp/portage/sys-fs/udev-225/work/systemd-225/src/basic/missing.h:1023:24: error: '__NR_kcmp' undeclared (first use in this function)
         return syscall(__NR_kcmp, pid1, pid2, type, idx1, idx2);
                        ^
/var/tmp/portage/sys-fs/udev-225/work/systemd-225/src/basic/missing.h:1023:24: note: each undeclared identifier is reported only once for each function it appears in
Makefile:13318: recipe for target 'src/libudev/libudev-device.lo' failed
make: *** [src/libudev/libudev-device.lo] Error 1
In file included from /var/tmp/portage/sys-fs/udev-225/work/systemd-225/src/basic/util.h:46:0,
                 from /var/tmp/portage/sys-fs/udev-225/work/systemd-225/src/libudev/libudev-private.h:29,
                 from /var/tmp/portage/sys-fs/udev-225/work/systemd-225/src/libudev/libudev-util.c:29:
/var/tmp/portage/sys-fs/udev-225/work/systemd-225/src/basic/missing.h: In function 'kcmp':
/var/tmp/portage/sys-fs/udev-225/work/systemd-225/src/basic/missing.h:1023:24: error: '__NR_kcmp' undeclared (first use in this function)
         return syscall(__NR_kcmp, pid1, pid2, type, idx1, idx2);
                        ^
/var/tmp/portage/sys-fs/udev-225/work/systemd-225/src/basic/missing.h:1023:24: note: each undeclared identifier is reported only once for each function it appears in
In file included from /var/tmp/portage/sys-fs/udev-225/work/systemd-225/src/basic/util.h:46:0,
                 from /var/tmp/portage/sys-fs/udev-225/work/systemd-225/src/libudev/libudev-private.h:29,
                 from /var/tmp/portage/sys-fs/udev-225/work/systemd-225/src/libudev/libudev.c:28:
/var/tmp/portage/sys-fs/udev-225/work/systemd-225/src/basic/missing.h: In function 'kcmp':
/var/tmp/portage/sys-fs/udev-225/work/systemd-225/src/basic/missing.h:1023:24: error: '__NR_kcmp' undeclared (first use in this function)
         return syscall(__NR_kcmp, pid1, pid2, type, idx1, idx2);
                        ^
/var/tmp/portage/sys-fs/udev-225/work/systemd-225/src/basic/missing.h:1023:24: note: each undeclared identifier is reported only once for each function it appears in
Makefile:13318: recipe for target 'src/libudev/libudev-util.lo' failed
make: *** [src/libudev/libudev-util.lo] Error 1
Makefile:13318: recipe for target 'src/libudev/libudev.lo' failed
make: *** [src/libudev/libudev.lo] Error 1
 * ERROR: sys-fs/udev-225::gentoo failed (compile phase):
 *   emake failed
 * 
 * If you need support, post the output of `emerge --info '=sys-fs/udev-225::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=sys-fs/udev-225::gentoo'`.
 * The complete build log is located at '/var/tmp/portage/sys-fs/udev-225/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-fs/udev-225/temp/environment'.
 * Working directory: '/var/tmp/portage/sys-fs/udev-225/work/systemd-225-.ia64'
 * S: '/var/tmp/portage/sys-fs/udev-225/work/systemd-225'
 * Messages for package sys-libs/timezone-data-2015f:
 * You do not have TIMEZONE set in /etc/timezone.
 * Skipping auto-update of /etc/localtime.
 * Messages for package sys-apps/baselayout-2.2:
 * The following users have non-existent shells!
 * halt - /sbin/halt
 * shutdown - /sbin/shutdown
 * Messages for package sys-apps/sysvinit-2.88-r7:
 * The last/lastb/mesg/mountpoint/sulogin/utmpdump/wall tools have been moved to
 * sys-apps/util-linux. The pidof tool has been moved to sys-process/procps.
 * Messages for package sys-apps/busybox-1.24.1:
 * Could not locate user configfile, so we will save a default one
 * Your configuration for sys-apps/busybox-1.24.1 has been saved in 
 * /etc/portage/savedconfig/sys-apps/busybox-1.24.1 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-apps/coreutils-8.23:
 * Make sure you run 'hash -r' in your active shells.
 * You should also re-source your shell settings for LS_COLORS
 *   changes, such as: source /etc/profile
 * Messages for package sys-libs/glibc-2.21-r1:
 * Defaulting /etc/host.conf:multi to on
 * Generating all locales; edit /etc/locale.gen to save time/space
 * Messages for package sys-apps/less-481:
 * lesspipe offers colorization options.  Run 'lesspipe -h' for info.
 * Messages for package sys-devel/gcc-4.9.3:
 * If you have issues with packages unable to locate libstdc++.la,
 * then try running 'fix_libtool_files.sh' on the old gcc versions.
 * You might want to review the GCC upgrade guide when moving between
 * major versions (like 4.2 to 4.3):
 * https://wiki.gentoo.org/wiki/Upgrading_GCC
 * Messages for package sys-libs/pam-1.2.1:
 * Some software with pre-loaded PAM libraries might experience
 * warnings or failures related to missing symbols and/or versions
 * after any update. While unfortunate this is a limit of the
 * implementation of PAM and the software, and it requires you to
 * restart the software manually after the update.
 * 
 * You can get a list of such software running a command like
 *   lsof / | egrep -i 'del.*libpam\.so'
 * 
 * Alternatively, simply reboot your system.
 * Messages for package sys-apps/util-linux-2.26.2:
 * The mesg/wall/write tools have been disabled due to USE=-tty-helpers.
 * The agetty util now clears the terminal by default. You
 * might want to add --noclear to your /etc/inittab lines.
 * Messages for package sys-apps/man-db-2.7.2:
 * Defaulting to USE=gdbm due to ambiguous berkdb/gdbm USE flag settings
 * Messages for package sys-apps/openrc-0.18.4:
 * Auto-adding 'termencoding' service to your boot runlevel
 * Auto-adding 'swapfiles' service to your boot runlevel
 * Auto-adding 'sysfs' service to your sysinit runlevel
 * Auto-adding 'tmpfiles.setup' service to your boot runlevel
 * Auto-adding 'loopback' service to your boot runlevel
 * Auto-adding 'tmpfiles.dev' service to your sysinit runlevel
 * Auto-adding 'binfmt' service to your boot runlevel
 * Auto-adding 'mtab' service to your boot runlevel
 * 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
 * 
 * Bug https://bugs.gentoo.org/show_bug.cgi?id=427996 was not
 * fixed correctly in earlier versions of OpenRC.
 * The correct fix is implemented in this version, but that
 * means netmount needs to be added to the default runlevel if
 * you are using nfs file systems.
 * 
 * You should now update all files in /etc, using etc-update
 * or equivalent before restarting any services or this host.
 * Messages for package net-misc/netifrc-0.2.2:
 * The network configuration scripts will use dhcp by
 * default to set up your interfaces.
 * If you need to set up something more complete, see
 * //usr/share/doc/netifrc-0.2.2/README
 * Messages for package sys-fs/udev-225:
 * Unable to find kernel sources at /usr/src/linux
 * Unable to calculate Linux Kernel version for build, attempting to use running version
 *   CONFIG_IDE:	 should not be set. But it is.
 *   CONFIG_FHANDLE:	 is not set when it should be.
 *   CONFIG_FW_LOADER_USER_HELPER:	 should not be set. But it is.
 * Please check to make sure these options are set correctly.
 * Failure to do so may cause unexpected problems.
 * ERROR: sys-fs/udev-225::gentoo failed (compile phase):
 *   emake failed
 * 
 * If you need support, post the output of `emerge --info '=sys-fs/udev-225::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=sys-fs/udev-225::gentoo'`.
 * The complete build log is located at '/var/tmp/portage/sys-fs/udev-225/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-fs/udev-225/temp/environment'.
 * Working directory: '/var/tmp/portage/sys-fs/udev-225/work/systemd-225-.ia64'
 * S: '/var/tmp/portage/sys-fs/udev-225/work/systemd-225'





























!!! catalyst: run script failed.


Traceback (most recent call last):
  File "modules/generic_stage_target.py", line 1244, in run_local
    "run script failed.",env=self.env)
  File "/usr/lib/catalyst/modules/catalyst_support.py", line 541, in cmd
    raise CatalystError,myexc
CatalystError
None

!!! catalyst: Stage build aborting due to error.

Traceback (most recent call last):
File "/usr/lib/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 1249, in run_local
    raise CatalystError,"Stage build aborting due to error."
CatalystError
!!! catalyst: Error encountered during run of target stage3
Catalyst aborting....
lockfile does not exist '/home/catalyst/tmp/default/stage3-ia64-20160126/.catalyst_lock'



Full build log at /tmp/catalyst-auto.vVp9RT/log/stage3.log


             reply	other threads:[~2016-01-26 12:48 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-26 12:48 catalyst [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-09-30  7:20 [gentoo-releng-autobuilds] [ia64-auto] Catalyst fatal build error - stage3.spec catalyst
2019-09-29  7:35 catalyst
2019-09-21  6:48 catalyst
2019-09-20  6:53 catalyst
2019-09-19  6:43 catalyst
2019-09-18  6:47 catalyst
2019-09-17  6:52 catalyst
2019-09-16  7:39 catalyst
2019-09-15  6:52 catalyst
2019-09-14  6:48 catalyst
2019-09-13  6:46 catalyst
2019-09-13  1:27 catalyst
2019-09-12  6:51 catalyst
2019-09-11  6:52 catalyst
2019-09-10  6:48 catalyst
2019-09-09  7:15 catalyst
2019-09-08  6:52 catalyst
2019-09-07  6:49 catalyst
2019-09-06  6:47 catalyst
2018-05-22 13:11 catalyst
2018-02-19  9:47 catalyst
2018-02-18 10:50 catalyst
2018-02-17  9:38 catalyst
2018-02-16  9:23 catalyst
2018-02-15  9:22 catalyst
2018-02-14  9:21 catalyst
2018-02-13  9:36 catalyst
2018-02-12  9:22 catalyst
2018-01-30  7:21 catalyst
2018-01-29 12:57 catalyst
2018-01-28 13:11 catalyst
2016-02-23 13:33 catalyst
2016-02-16 12:59 catalyst
2016-02-09 13:05 catalyst
2016-02-02 13:01 catalyst
2016-01-12 12:19 catalyst
2015-02-24  7:28 catalyst
2013-08-28  1:09 catalyst
2012-07-17 15:11 catalyst
2011-05-17 18:58 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=20160126124809.29BDCE0857@pigeon.gentoo.org \
    --to=catalyst@guppy.ia64.dev.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