From: catalyst@thor.jmbsvicetto.name
To: jmbsvicetto@gmail.com,gentoo-releng-autobuilds@lists.gentoo.org
Subject: [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - cloud/stage4-minimal.spec
Date: Mon, 20 Mar 2017 08:31:55 +0000 (UTC) [thread overview]
Message-ID: <20170320083155.2263A13460F@thor.jmbsvicetto.name> (raw)
20 Mar 2017 08:18:32 UTC: NOTICE : Loading configuration file: /etc/catalyst/release/amd64-auto.conf
20 Mar 2017 08:18:32 UTC: NOTICE : Processing spec file: cloud/stage4-minimal.spec
20 Mar 2017 08:18:32 UTC: NOTICE : Using target: stage4
20 Mar 2017 08:18:32 UTC: NOTICE : Source file specification matching setting is: loose
20 Mar 2017 08:18:32 UTC: NOTICE : Accepted source file extensions search order: ['tar.xz', 'tpxz', 'xz', 'tar.bz2', 'bz2', 'tbz2', 'squashfs', 'sfs', 'tar.gz', 'gz', 'tar']
20 Mar 2017 08:18:33 UTC: NOTICE : Source path set to /home/release/buildroot/amd64-dev/builds/default/stage3-amd64-latest.tar.xz
20 Mar 2017 08:18:33 UTC: NOTICE : purge(); clearing autoresume ...
20 Mar 2017 08:18:33 UTC: NOTICE : purge(); clearing chroot ...
20 Mar 2017 08:18:33 UTC: NOTICE : Clearing the chroot path ...
20 Mar 2017 08:18:33 UTC: NOTICE : purge(); clearing package cache ...
20 Mar 2017 08:18:33 UTC: NOTICE : purging the pkgcache ...
20 Mar 2017 08:18:33 UTC: NOTICE : purge(); clearing kerncache ...
20 Mar 2017 08:18:33 UTC: NOTICE : --- Running action sequence: unpack
20 Mar 2017 08:18:33 UTC: NOTICE : Clearing the chroot path ...
20 Mar 2017 08:18:33 UTC: NOTICE : Starting auto from /home/release/buildroot/amd64-dev/builds/default/stage3-amd64-latest.tar.xz
20 Mar 2017 08:18:33 UTC: NOTICE : to /home/release/buildroot/amd64-dev/tmp/default/stage4-amd64-minimal-20170320 (this may take some time) ..
20 Mar 2017 08:18:36 UTC: NOTICE : --- Running action sequence: unpack_snapshot
20 Mar 2017 08:18:36 UTC: NOTICE : Unpacking portage tree (this can take a long time) ...
20 Mar 2017 08:18:46 UTC: NOTICE : --- Running action sequence: config_profile_link
20 Mar 2017 08:18:46 UTC: NOTICE : --- Running action sequence: setup_confdir
20 Mar 2017 08:18:46 UTC: NOTICE : --- Running action sequence: portage_overlay
20 Mar 2017 08:18:46 UTC: NOTICE : --- Running action sequence: bind
20 Mar 2017 08:18:46 UTC: NOTICE : --- Running action sequence: chroot_setup
20 Mar 2017 08:18:46 UTC: NOTICE : Setting up chroot...
20 Mar 2017 08:18:46 UTC: WARNING : Overriding certain env variables may cause catastrophic failure.
20 Mar 2017 08:18:46 UTC: WARNING : If your build fails look here first as the possible problem.
20 Mar 2017 08:18:46 UTC: WARNING : Catalyst assumes you know what you are doing when setting these variables.
20 Mar 2017 08:18:46 UTC: WARNING : Catalyst Maintainers use VERY minimal envscripts, if used at all.
20 Mar 2017 08:18:46 UTC: WARNING : You have been warned.
20 Mar 2017 08:18:46 UTC: NOTICE : --- Running action sequence: setup_environment
20 Mar 2017 08:18:46 UTC: NOTICE : --- Running action sequence: build_packages
Copying stage4-chroot.sh to /tmp
copying stage4-chroot.sh to /home/release/buildroot/amd64-dev/tmp/default/stage4-amd64-minimal-20170320/tmp
copying chroot-functions.sh to /home/release/buildroot/amd64-dev/tmp/default/stage4-amd64-minimal-20170320/tmp
Ensure the file has the executable bit set
Running stage4-chroot.sh in chroot:
chroot /home/release/buildroot/amd64-dev/tmp/default/stage4-amd64-minimal-20170320 /tmp/stage4-chroot.sh
>>> Regenerating /etc/ld.so.cache...
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 net-misc/iputils sys-boot/grub 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-libs/efivar-30::gentoo
>>> Installing (1 of 22) sys-libs/efivar-30::gentoo
>>> Emerging (2 of 22) net-dns/libidn-1.33::gentoo
>>> Installing (2 of 22) net-dns/libidn-1.33::gentoo
>>> Emerging (3 of 22) dev-libs/nettle-3.2-r1::gentoo
>>> Installing (3 of 22) dev-libs/nettle-3.2-r1::gentoo
>>> Emerging (4 of 22) dev-scheme/guile-1.8.8-r3::gentoo
>>> Installing (4 of 22) dev-scheme/guile-1.8.8-r3::gentoo
>>> Emerging (5 of 22) virtual/libudev-215-r1::gentoo
>>> Installing (5 of 22) virtual/libudev-215-r1::gentoo
>>> Emerging (6 of 22) sys-apps/lsb-release-1.4::gentoo
>>> Installing (6 of 22) sys-apps/lsb-release-1.4::gentoo
>>> Recording sys-apps/lsb-release in "world" favorites file...
>>> Emerging (7 of 22) sys-devel/bc-1.06.95-r1::gentoo
>>> Installing (7 of 22) sys-devel/bc-1.06.95-r1::gentoo
>>> Recording sys-devel/bc in "world" favorites file...
>>> Emerging (8 of 22) media-libs/freetype-2.7.1-r2::gentoo
>>> Installing (8 of 22) media-libs/freetype-2.7.1-r2::gentoo
>>> Emerging (9 of 22) sys-apps/pciutils-3.4.1::gentoo
>>> Installing (9 of 22) sys-apps/pciutils-3.4.1::gentoo
>>> Emerging (10 of 22) sys-devel/autogen-5.18.4::gentoo
>>> Installing (10 of 22) sys-devel/autogen-5.18.4::gentoo
>>> Emerging (11 of 22) dev-libs/libtasn1-4.10::gentoo
>>> Installing (11 of 22) dev-libs/libtasn1-4.10::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.4::gentoo
>>> Installing (13 of 22) net-misc/dhcp-4.3.4::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.3.26::gentoo
>>> Installing (17 of 22) net-libs/gnutls-3.3.26::gentoo
>>> Emerging (18 of 22) virtual/logger-0::gentoo
>>> Installing (18 of 22) virtual/logger-0::gentoo
>>> Emerging (19 of 22) mail-mta/nullmailer-1.13-r5::gentoo
>>> Installing (19 of 22) mail-mta/nullmailer-1.13-r5::gentoo
>>> Emerging (20 of 22) sys-boot/grub-2.02_beta3-r1::gentoo
>>> Installing (20 of 22) sys-boot/grub-2.02_beta3-r1::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.18_p1::gentoo
>>> Installing (22 of 22) app-admin/sudo-1.8.18_p1::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-1.13-r5:
* To create an initial setup, please do:
* emerge --config =mail-mta/nullmailer-1.13-r5
* Messages for package sys-boot/grub-2.02_beta3-r1:
* For information on how to configure GRUB2 please refer to the guide:
* https://wiki.gentoo.org/wiki/GRUB2_Quick_Start
*
* For manual configuration, see /usr/share/doc/grub-2.02_beta3-r1/grub.cfg.example
*
* 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.18_p1:
* 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 /home/release/buildroot/amd64-dev/tmp/default/stage4-amd64-minimal-20170320/tmp/stage4-chroot.sh from the chroot
removing /home/release/buildroot/amd64-dev/tmp/default/stage4-amd64-minimal-20170320/tmp/chroot-functions.sh from the chroot
20 Mar 2017 08:31:53 UTC: NOTICE : --- Running action sequence: build_kernel
Copying pre-kmerge.sh to /tmp
copying pre-kmerge.sh to /home/release/buildroot/amd64-dev/tmp/default/stage4-amd64-minimal-20170320/tmp
copying chroot-functions.sh to /home/release/buildroot/amd64-dev/tmp/default/stage4-amd64-minimal-20170320/tmp
Ensure the file has the executable bit set
Running pre-kmerge.sh in chroot:
chroot /home/release/buildroot/amd64-dev/tmp/default/stage4-amd64-minimal-20170320 /tmp/pre-kmerge.sh
"/etc/portage/make.conf", line 8: Invalid token 'bindist' (not '=')
"/etc/portage/make.conf", line 8: Invalid token 'bindist' (not '=')
"/etc/portage/make.conf", line 8: Invalid token 'bindist' (not '=')
"/etc/portage/make.conf", line 8: Invalid token 'bindist' (not '=')
>>> Regenerating /etc/ld.so.cache...
emerge --quiet --usepkg --buildpkg --newuse --oneshot genkernel
"/etc/portage/make.conf", line 8: Invalid token 'bindist' (not '=')
20 Mar 2017 08:31:54 UTC: ERROR : CatalystError: cmd(['/usr/share/catalyst/targets/stage4/stage4-controller.sh', 'pre-kmerge']) exited 1
20 Mar 2017 08:31:55 UTC: ERROR : CatalystError: build aborting due to kernel build error.
Traceback (most recent call last):
File "/usr/lib64/python3.4/site-packages/catalyst/base/stagebase.py", line 1530, in build_kernel
env=self.env)
File "/usr/lib64/python3.4/site-packages/catalyst/support.py", line 54, in cmd
print_traceback=False)
catalyst.support.CatalystError: cmd(['/usr/share/catalyst/targets/stage4/stage4-controller.sh', 'pre-kmerge']) exited 1
20 Mar 2017 08:31:55 UTC: ERROR : Exception running action sequence build_kernel
Traceback (most recent call last):
File "/usr/lib64/python3.4/site-packages/catalyst/base/stagebase.py", line 1530, in build_kernel
env=self.env)
File "/usr/lib64/python3.4/site-packages/catalyst/support.py", line 54, in cmd
print_traceback=False)
catalyst.support.CatalystError: cmd(['/usr/share/catalyst/targets/stage4/stage4-controller.sh', 'pre-kmerge']) exited 1
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib64/python3.4/site-packages/catalyst/base/stagebase.py", line 1412, in run
getattr(self, x)()
File "/usr/lib64/python3.4/site-packages/catalyst/base/stagebase.py", line 1538, in build_kernel
print_traceback=True)
catalyst.support.CatalystError: build aborting due to kernel build error.
20 Mar 2017 08:31:55 UTC: NOTICE : Cleaning up... Running unbind()
Command exited with non-zero status 2
584.36user 95.13system 13:22.63elapsed 84%CPU (0avgtext+0avgdata 344328maxresident)k
0inputs+5855568outputs (0major+113470573minor)pagefaults 0swaps
Full build log at /home/release/tmp/run/catalyst-auto.20170320.A92UTx/log/cloud_stage4-minimal.log
next reply other threads:[~2017-03-20 8:32 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-20 8:31 catalyst [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-10-26 3:26 [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - cloud/stage4-minimal.spec catalyst
2017-10-26 3:26 catalyst
2017-10-26 3:25 catalyst
2017-10-26 3:25 catalyst
2017-10-26 3:25 catalyst
2017-10-26 3:25 catalyst
2017-10-26 3:25 catalyst
2017-10-26 3:25 catalyst
2017-10-26 3:25 catalyst
2017-10-26 3:25 catalyst
2017-10-26 3:25 catalyst
2017-10-26 3:25 catalyst
2017-10-26 3:22 catalyst
2017-03-13 8:38 catalyst
2017-03-10 3:39 catalyst
2017-03-07 13:13 catalyst
2017-03-06 21:06 catalyst
2017-03-06 8:29 catalyst
2017-03-04 20:27 catalyst
2017-03-01 18:35 catalyst
2017-03-01 5:43 catalyst
2017-03-01 4:11 catalyst
2017-03-01 3:47 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=20170320083155.2263A13460F@thor.jmbsvicetto.name \
--to=catalyst@thor.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