From: catalyst@nightheron.gentoo.org
To: releng@gentoo.org,gentoo-releng-autobuilds@lists.gentoo.org
Subject: [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-minimal.spec
Date: Thu, 19 Oct 2017 23:11:51 +0000 (UTC) [thread overview]
Message-ID: <20171019231151.3119934602@nightheron.gentoo.org> (raw)
copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171019//tmp
Ensure the file has the executable bit set
Running stage4-chroot.sh in chroot /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171019/
>>> Regenerating /etc/ld.so.cache...
Updating portage with USE=""
emerge --quiet --usepkg --buildpkg --newuse --oneshot --update --newuse sys-apps/portage
Bringing system up to date using profile specific use flags
emerge --quiet --usepkg --buildpkg --newuse -u @system
Emerging packages using stage4 use flags
emerge --quiet --usepkg --buildpkg --newuse app-admin/sudo net-misc/dhcp sys-boot/grub sys-apps/dmidecode sys-apps/gptfdisk sys-apps/iproute2 sys-apps/lsb-release sys-devel/bc sys-power/acpid
>>> Verifying ebuild manifests
>>> Running pre-merge checks for sys-power/acpid-2.0.28
* Determining the location of the kernel source code
* Unable to find kernel sources at /usr/src/linux
* Please make sure that /usr/src/linux points at your running kernel,
* (or the kernel you wish to build against).
* Alternatively, set the KERNEL_DIR environment variable to the kernel sources location
* Unable to calculate Linux Kernel version for build, attempting to use running version
* Checking for suitable kernel configuration options...
[ ok ]
>>> Emerging (1 of 22) sys-apps/dmidecode-3.0::gentoo
>>> Installing (1 of 22) sys-apps/dmidecode-3.0::gentoo
>>> Recording sys-apps/dmidecode in "world" favorites file...
>>> Emerging (2 of 22) dev-libs/libunistring-0.9.7::gentoo
>>> Installing (2 of 22) dev-libs/libunistring-0.9.7::gentoo
>>> Emerging (3 of 22) dev-libs/nettle-3.3-r2::gentoo
>>> Installing (3 of 22) dev-libs/nettle-3.3-r2::gentoo
>>> Emerging (4 of 22) virtual/libudev-232::gentoo
>>> Installing (4 of 22) virtual/libudev-232::gentoo
>>> Emerging (5 of 22) sys-apps/lsb-release-1.4::gentoo
>>> Installing (5 of 22) sys-apps/lsb-release-1.4::gentoo
>>> Recording sys-apps/lsb-release in "world" favorites file...
>>> Emerging (6 of 22) sys-devel/bc-1.06.95-r1::gentoo
>>> Installing (6 of 22) sys-devel/bc-1.06.95-r1::gentoo
>>> Recording sys-devel/bc in "world" favorites file...
>>> Emerging (7 of 22) media-libs/freetype-2.8::gentoo
>>> Installing (7 of 22) media-libs/freetype-2.8::gentoo
>>> Emerging (8 of 22) sys-apps/pciutils-3.4.1::gentoo
>>> Installing (8 of 22) sys-apps/pciutils-3.4.1::gentoo
>>> Emerging (9 of 22) sys-libs/efivar-30::gentoo
>>> Installing (9 of 22) sys-libs/efivar-30::gentoo
>>> Emerging (10 of 22) net-dns/libidn2-2.0.4::gentoo
>>> Installing (10 of 22) net-dns/libidn2-2.0.4::gentoo
>>> Emerging (11 of 22) dev-libs/libtasn1-4.12-r1::gentoo
>>> Installing (11 of 22) dev-libs/libtasn1-4.12-r1::gentoo
>>> Emerging (12 of 22) app-admin/metalog-3-r1::gentoo
>>> Installing (12 of 22) app-admin/metalog-3-r1::gentoo
>>> Emerging (13 of 22) net-misc/dhcp-4.3.5::gentoo
>>> Installing (13 of 22) net-misc/dhcp-4.3.5::gentoo
>>> Recording net-misc/dhcp in "world" favorites file...
>>> Emerging (14 of 22) sys-apps/gptfdisk-1.0.1::gentoo
>>> Installing (14 of 22) sys-apps/gptfdisk-1.0.1::gentoo
>>> Recording sys-apps/gptfdisk in "world" favorites file...
>>> Emerging (15 of 22) sys-power/acpid-2.0.28::gentoo
>>> Installing (15 of 22) sys-power/acpid-2.0.28::gentoo
>>> Recording sys-power/acpid in "world" favorites file...
>>> Emerging (16 of 22) sys-boot/efibootmgr-14::gentoo
>>> Installing (16 of 22) sys-boot/efibootmgr-14::gentoo
>>> Emerging (17 of 22) net-libs/gnutls-3.5.15::gentoo
>>> Installing (17 of 22) net-libs/gnutls-3.5.15::gentoo
>>> Emerging (18 of 22) virtual/logger-0::gentoo
>>> Installing (18 of 22) virtual/logger-0::gentoo
>>> Emerging (19 of 22) mail-mta/nullmailer-2.0-r1::gentoo
>>> Installing (19 of 22) mail-mta/nullmailer-2.0-r1::gentoo
>>> Emerging (20 of 22) sys-boot/grub-2.02::gentoo
>>> Installing (20 of 22) sys-boot/grub-2.02::gentoo
>>> Recording sys-boot/grub in "world" favorites file...
>>> Emerging (21 of 22) virtual/mta-1::gentoo
>>> Installing (21 of 22) virtual/mta-1::gentoo
>>> Emerging (22 of 22) app-admin/sudo-1.8.20_p2::gentoo
>>> Installing (22 of 22) app-admin/sudo-1.8.20_p2::gentoo
>>> Recording app-admin/sudo in "world" favorites file...
* Messages for package sys-power/acpid-2.0.28:
* 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-power/acpid-2.0.28:
*
* You may wish to read the Gentoo Linux Power Management Guide,
* which can be found online at:
* https://wiki.gentoo.org/wiki/Power_management/Guide
*
* You should reboot the system now to get /run mounted with tmpfs!
* Messages for package mail-mta/nullmailer-2.0-r1:
* To create an initial setup, please do:
* emerge --config =mail-mta/nullmailer-2.0-r1
* Messages for package sys-boot/grub-2.02:
* For information on how to configure GRUB2 please refer to the guide:
* https://wiki.gentoo.org/wiki/GRUB2_Quick_Start
*
* You may consider installing the following optional packages:
* sys-boot/os-prober for Detect other operating systems (grub-mkconfig)
* dev-libs/libisoburn for Create rescue media (grub-mkrescue)
* sys-fs/mdadm for Enable RAID device detection
* Messages for package app-admin/sudo-1.8.20_p2:
* To use the -A (askpass) option, you need to install a compatible
* password program from the following list. Starred packages will
* automatically register for the use with sudo (but will not force
* the -A option):
*
* [*] net-misc/ssh-askpass-fullscreen
* net-misc/x11-ssh-askpass
*
* You can override the choice by setting the SUDO_ASKPASS environmnent
* variable to the program you want to use.
removing /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171019//tmp/stage4-chroot.sh from the chroot
removing /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171019//tmp/chroot-functions.sh from the chroot
--- Running action sequence: build_kernel
Copying pre-kmerge.sh to /tmp
copying pre-kmerge.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171019//tmp
copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171019//tmp
Ensure the file has the executable bit set
Running pre-kmerge.sh in chroot /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171019/
>>> Regenerating /etc/ld.so.cache...
emerge --quiet --usepkg --buildpkg --newuse --oneshot genkernel
>>> Verifying ebuild manifests
>>> Running pre-merge checks for sys-kernel/genkernel-3.4.52.4-r2
>>> Emerging (1 of 2) app-arch/cpio-2.12-r1::gentoo
>>> Installing (1 of 2) app-arch/cpio-2.12-r1::gentoo
>>> Emerging (2 of 2) sys-kernel/genkernel-3.4.52.4-r2::gentoo
>>> Installing (2 of 2) sys-kernel/genkernel-3.4.52.4-r2::gentoo
* Messages for package sys-kernel/genkernel-3.4.52.4-r2:
* Documentation is available in the genkernel manual page
* as well as the following URL:
* https://wiki.gentoo.org/wiki/Genkernel
* This package is known to not work with reiser4. If you are running
* reiser4 and have a problem, do not file a bug. We know it does not
* work and we don't plan on fixing it since reiser4 is the one that is
* broken in this regard. Try using a sane filesystem like ext4.
* The LUKS support has changed from versions prior to 3.4.4. Now,
* you use crypt_root=/dev/blah instead of real_root=luks:/dev/blah.
removing /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171019//tmp/pre-kmerge.sh from the chroot
removing /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171019//tmp/chroot-functions.sh from the chroot
Copying kmerge.sh to /tmp
copying kmerge.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171019//tmp
copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171019//tmp
Ensure the file has the executable bit set
Running kmerge.sh in chroot /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171019/
>>> Regenerating /etc/ld.so.cache...
Genkernel version 3.4.52.4 found ... continuing
emerge --quiet --usepkg --buildpkg --newuse hardened-sources
[ebuild N ] sys-kernel/hardened-sources-4.8.17-r2
The following mask changes are necessary to proceed:
(see "package.unmask" in the portage(5) man page for more details)
# required by hardened-sources (argument)
# /usr/portage/profiles/package.mask:
# Anthony G. Basile <blueness@gentoo.org> (27 Aug 2017)
# Upstream is no longer providing public patches
=sys-kernel/hardened-sources-4.8.17-r2
Use --autounmask-write to write changes to config files (honoring
CONFIG_PROTECT). Carefully examine the list of proposed changes,
paying special attention to mask or keyword changes that may expose
experimental or unstable packages.
* IMPORTANT: 11 news items need reading for repository 'gentoo'.
* Use eselect news read to view new items.
!!! catalyst: Runscript kernel build failed
Traceback (most recent call last):
File "modules/generic_stage_target.py", line 1457, in build_kernel
self._build_kernel(kname=kname)
File "modules/generic_stage_target.py", line 1501, in _build_kernel
"Runscript kernel build failed",env=self.env)
File "/usr/lib64/catalyst//modules/catalyst_support.py", line 541, in cmd
raise CatalystError,myexc
CatalystError
None
!!! catalyst: build aborting due to kernel build 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 1333, in run
apply(getattr(self,x))
File "modules/generic_stage_target.py", line 1462, in build_kernel
"build aborting due to kernel build error."
CatalystError
!!! catalyst: Error encountered during run of target stage4
Catalyst aborting....
lockfile does not exist '/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171019/.catalyst_lock'
Command exited with non-zero status 1
1129.26user 403.60system 18:14.37elapsed 140%CPU (0avgtext+0avgdata 806112maxresident)k
2096inputs+4328976outputs (0major+114966662minor)pagefaults 0swaps
Full build log at /release/tmp/run/catalyst-auto.20171019.XFbnjd/log/hardened_stage4-minimal.log
next reply other threads:[~2017-10-19 23:11 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-19 23:11 catalyst [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-12-11 22:03 [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-minimal.spec catalyst
2017-12-11 10:22 catalyst
2017-12-07 0:22 catalyst
2017-12-06 7:50 catalyst
2017-12-03 21:11 catalyst
2017-12-03 20:47 catalyst
2017-12-03 20:41 catalyst
2017-11-17 0:18 catalyst
2017-11-09 23:33 catalyst
2017-11-03 0:00 catalyst
2017-10-26 23:17 catalyst
2017-10-12 22:59 catalyst
2017-10-05 23:36 catalyst
2017-09-28 22:00 catalyst
2017-09-21 11:03 catalyst
2017-09-14 11:00 catalyst
2017-09-08 5:45 catalyst
2017-09-01 5:57 catalyst
2017-03-01 3:47 catalyst
2017-03-01 3:47 catalyst
2017-03-01 3:47 catalyst
2017-03-01 3:47 catalyst
2016-08-18 17:06 catalyst
2016-07-30 13:08 catalyst
2016-07-25 3:11 catalyst
2016-05-30 3:00 catalyst
2016-04-30 13:17 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=20171019231151.3119934602@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