public inbox for gentoo-releng-autobuilds@lists.gentoo.org
 help / color / mirror / Atom feed
From: catalyst@thor.jmbsvicetto.name
To: jmbsvicetto@gmail.com,gentoo-releng-autobuilds@lists.gentoo.org
Subject: [gentoo-releng-autobuilds] [amd64-auto] Catalyst non-fatal build error - hardened/stage4-minimal.spec
Date: Mon, 18 Jun 2018 06:17:32 +0000 (UTC)	[thread overview]
Message-ID: <20180618061732.B2CAE649C5@thor.jmbsvicetto.name> (raw)




*** Running command: time catalyst -a -c /etc/catalyst/release/amd64-auto.conf -f hardened/stage4-minimal.spec
18 Jun 2018 06:16:17 UTC: NOTICE  : Loading configuration file: /etc/catalyst/release/amd64-auto.conf
18 Jun 2018 06:16:17 UTC: NOTICE  : conf_values[options] = {'clear-autoresume', 'bindist', 'pkgcache', 'preserve_libs'}
18 Jun 2018 06:16:17 UTC: NOTICE  : Processing spec file: hardened/stage4-minimal.spec
18 Jun 2018 06:16:17 UTC: NOTICE  : Using target: stage4
18 Jun 2018 06:16:17 UTC: NOTICE  : Source file specification matching setting is: loose
18 Jun 2018 06:16:17 UTC: NOTICE  : Accepted source file extensions search order: ['tar.xz', 'tpxz', 'xz', 'tar.bz2', 'bz2', 'tbz2', 'squashfs', 'sfs', 'tar.gz', 'gz', 'tar']
18 Jun 2018 06:16:18 UTC: NOTICE  : Source path set to /home/release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened-latest.tar.xz
18 Jun 2018 06:16:18 UTC: NOTICE  : --- Running action sequence: unpack
18 Jun 2018 06:16:18 UTC: NOTICE  : Clearing the chroot path ...
18 Jun 2018 06:16:18 UTC: NOTICE  : Emptying directory: /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20180618T002047Z
18 Jun 2018 06:16:18 UTC: NOTICE  : Starting auto from /home/release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened-latest.tar.xz
18 Jun 2018 06:16:18 UTC: NOTICE  : to /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20180618T002047Z (this may take some time) ..
18 Jun 2018 06:16:21 UTC: NOTICE  : --- Running action sequence: unpack_snapshot
18 Jun 2018 06:16:21 UTC: NOTICE  : Unpacking portage tree (this can take a long time) ...
18 Jun 2018 06:16:35 UTC: NOTICE  : --- Running action sequence: config_profile_link
18 Jun 2018 06:16:35 UTC: NOTICE  : --- Running action sequence: setup_confdir
18 Jun 2018 06:16:35 UTC: NOTICE  : --- Running action sequence: portage_overlay
18 Jun 2018 06:16:35 UTC: NOTICE  : --- Running action sequence: bind
18 Jun 2018 06:16:35 UTC: NOTICE  : --- Running action sequence: chroot_setup
18 Jun 2018 06:16:35 UTC: NOTICE  : Setting up chroot...
18 Jun 2018 06:16:35 UTC: WARNING : Overriding certain env variables may cause catastrophic failure.
18 Jun 2018 06:16:35 UTC: WARNING : If your build fails look here first as the possible problem.
18 Jun 2018 06:16:35 UTC: WARNING : Catalyst assumes you know what you are doing when setting these variables.
18 Jun 2018 06:16:35 UTC: WARNING : Catalyst Maintainers use VERY minimal envscripts, if used at all.
18 Jun 2018 06:16:35 UTC: WARNING : You have been warned.
18 Jun 2018 06:16:35 UTC: NOTICE  : Writing the stage make.conf to: /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20180618T002047Z/etc/portage/make.conf
18 Jun 2018 06:16:35 UTC: NOTICE  : STICKY-CONFIG is enabled
18 Jun 2018 06:16:35 UTC: NOTICE  : --- Running action sequence: setup_environment
18 Jun 2018 06:16:35 UTC: NOTICE  : --- Running action sequence: build_packages
Copying stage4-chroot.sh to /tmp
copying stage4-chroot.sh to /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20180618T002047Z/tmp
copying chroot-functions.sh to /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20180618T002047Z/tmp
Ensure the file has the executable bit set
Running stage4-chroot.sh in chroot:
    chroot /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20180618T002047Z /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 net-misc/dhcp sys-boot/grub sys-apps/dmidecode sys-apps/gptfdisk sys-apps/iproute2 sys-devel/bc sys-power/acpid
>>> Running pre-merge checks for sys-power/acpid-2.0.29-r1
 * 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 binary (1 of 10) sys-apps/dmidecode-3.1::gentoo
>>> Installing (1 of 10) sys-apps/dmidecode-3.1::gentoo
>>> Recording sys-apps/dmidecode in "world" favorites file...
>>> Emerging binary (2 of 10) sys-power/acpid-2.0.29-r1::gentoo
>>> Installing (2 of 10) sys-power/acpid-2.0.29-r1::gentoo
>>> Recording sys-power/acpid in "world" favorites file...
>>> Emerging binary (3 of 10) sys-libs/efivar-31::gentoo
>>> Installing (3 of 10) sys-libs/efivar-31::gentoo
>>> Emerging binary (4 of 10) virtual/libudev-232::gentoo
>>> Installing (4 of 10) virtual/libudev-232::gentoo
>>> Emerging binary (5 of 10) net-misc/dhcp-4.3.6_p1::gentoo
>>> Installing (5 of 10) net-misc/dhcp-4.3.6_p1::gentoo
>>> Recording net-misc/dhcp in "world" favorites file...
>>> Emerging binary (6 of 10) sys-apps/gptfdisk-1.0.1::gentoo
>>> Installing (6 of 10) sys-apps/gptfdisk-1.0.1::gentoo
>>> Recording sys-apps/gptfdisk in "world" favorites file...
>>> Emerging binary (7 of 10) sys-devel/bc-1.06.95-r2::gentoo
>>> Installing (7 of 10) sys-devel/bc-1.06.95-r2::gentoo
>>> Recording sys-devel/bc in "world" favorites file...
>>> Emerging binary (8 of 10) sys-apps/pciutils-3.4.1::gentoo
>>> Installing (8 of 10) sys-apps/pciutils-3.4.1::gentoo
>>> Emerging binary (9 of 10) sys-boot/efibootmgr-15::gentoo
>>> Installing (9 of 10) sys-boot/efibootmgr-15::gentoo
>>> Emerging binary (10 of 10) sys-boot/grub-2.02-r1::gentoo
>>> Installing (10 of 10) sys-boot/grub-2.02-r1::gentoo
>>> Recording sys-boot/grub in "world" favorites file...
 * Messages for package sys-power/acpid-2.0.29-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-power/acpid-2.0.29-r1:
 * 
 * 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 sys-boot/grub-2.02-r1:
 * 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






removing /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20180618T002047Z/tmp/stage4-chroot.sh from the chroot
removing /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20180618T002047Z/tmp/chroot-functions.sh from the chroot
18 Jun 2018 06:17:29 UTC: NOTICE  : --- Running action sequence: build_kernel
Copying pre-kmerge.sh to /tmp
copying pre-kmerge.sh to /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20180618T002047Z/tmp
copying chroot-functions.sh to /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20180618T002047Z/tmp
Ensure the file has the executable bit set
Running pre-kmerge.sh in chroot:
    chroot /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20180618T002047Z /tmp/pre-kmerge.sh
>>> Regenerating /etc/ld.so.cache...
emerge --quiet --usepkg --buildpkg --newuse --oneshot genkernel
[ebuild  N    ] sys-kernel/linux-firmware-20180103-r1 
[binary  N    ] app-arch/cpio-2.12-r1 
[ebuild   R   ] sys-apps/util-linux-2.30.2-r1 
[ebuild  N    ] sys-kernel/genkernel-3.5.3.3 

The following USE changes are necessary to proceed:
 (see "package.use" in the portage(5) man page for more details)
# required by sys-kernel/genkernel-3.5.3.3::gentoo
# required by genkernel (argument)
>=sys-apps/util-linux-2.30.2-r1 static-libs

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.
18 Jun 2018 06:17:32 UTC: ERROR   : CatalystError: cmd(['/usr/share/catalyst/targets/stage4/stage4-controller.sh', 'pre-kmerge']) exited 1
18 Jun 2018 06:17:32 UTC: ERROR   : CatalystError: build aborting due to kernel build error.
Traceback (most recent call last):
  File "/usr/lib64/python3.5/site-packages/catalyst/base/stagebase.py", line 1572, in build_kernel
    env=self.env)
  File "/usr/lib64/python3.5/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
18 Jun 2018 06:17:32 UTC: ERROR   : Exception running action sequence build_kernel
Traceback (most recent call last):
  File "/usr/lib64/python3.5/site-packages/catalyst/base/stagebase.py", line 1572, in build_kernel
    env=self.env)
  File "/usr/lib64/python3.5/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.5/site-packages/catalyst/base/stagebase.py", line 1454, in run
    getattr(self, x)()
  File "/usr/lib64/python3.5/site-packages/catalyst/base/stagebase.py", line 1580, in build_kernel
    print_traceback=True)
catalyst.support.CatalystError: build aborting due to kernel build error.
18 Jun 2018 06:17:32 UTC: NOTICE  : Cleaning up... Running unbind()
Command exited with non-zero status 2
44.84user 6.06system 1:14.96elapsed 67%CPU (0avgtext+0avgdata 349444maxresident)k
8inputs+3315792outputs (0major+2056152minor)pagefaults 0swaps



Full build log at /home/release/tmp/run/catalyst-auto.20180618T002047Z.NJqE12/log/hardened_stage4-minimal.log


             reply	other threads:[~2018-06-18  6:17 UTC|newest]

Thread overview: 83+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-18  6:17 catalyst [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-09-28  3:00 [gentoo-releng-autobuilds] [amd64-auto] Catalyst non-fatal build error - hardened/stage4-minimal.spec catalyst
2020-09-21  3:00 catalyst
2020-09-14  3:00 catalyst
2020-09-07  3:00 catalyst
2020-08-31  3:00 catalyst
2020-08-24  3:00 catalyst
2020-08-17  3:00 catalyst
2020-08-10  3:02 catalyst
2020-08-03  3:00 catalyst
2020-07-27  3:00 catalyst
2020-07-20  3:00 catalyst
2020-07-13  3:00 catalyst
2020-07-06  3:00 catalyst
2020-06-29  4:11 catalyst
2020-06-29  3:00 catalyst
2020-06-22  3:00 catalyst
2020-06-18  0:33 catalyst
2020-06-15  3:00 catalyst
2020-06-15  0:35 catalyst
2020-06-08  3:00 catalyst
2020-06-01  3:00 catalyst
2020-05-25  3:00 catalyst
2020-05-18  3:00 catalyst
2020-05-15 14:29 catalyst
2020-05-12 16:56 catalyst
2020-05-11 16:26 catalyst
2020-05-11 11:34 catalyst
2020-05-11  3:01 catalyst
2020-05-04  3:13 catalyst
2020-04-27  3:00 catalyst
2020-04-13  4:01 catalyst
2020-04-06  3:58 catalyst
2020-03-30  3:59 catalyst
2020-03-23  3:57 catalyst
2020-03-16  3:56 catalyst
2020-03-09  3:57 catalyst
2020-03-02  3:54 catalyst
2020-02-24  3:44 catalyst
2020-02-17  3:42 catalyst
2020-02-10  3:37 catalyst
2020-02-03  3:38 catalyst
2020-01-27  3:38 catalyst
2020-01-20  3:39 catalyst
2020-01-13  3:40 catalyst
2019-12-30  6:15 catalyst
2019-12-09  1:58 catalyst
2019-07-16  3:38 catalyst
2019-07-16  3:01 catalyst
2019-07-16  2:56 catalyst
2019-07-16  2:51 catalyst
2019-05-31 11:23 catalyst
2019-05-30 11:34 catalyst
2019-05-29 17:54 catalyst
2019-05-27 11:54 catalyst
2018-09-25  3:03 catalyst
2018-09-24 20:07 catalyst
2018-08-14 16:27 catalyst
2018-08-11  9:51 catalyst
2018-08-11  9:48 catalyst
2018-07-16 22:32 catalyst
2018-07-16 22:31 catalyst
2018-07-02  9:49 catalyst
2018-06-28  5:18 catalyst
2018-06-25 16:21 catalyst
2018-06-15 22:17 catalyst
2018-05-30  2:37 catalyst
2018-02-21  0:01 catalyst
2018-02-06 10:15 catalyst
2018-02-06  3:20 catalyst
2018-02-03 21:34 catalyst
2018-02-02  4:27 catalyst
2018-01-05  9:23 catalyst
2018-01-04 13:37 catalyst
2018-01-01 11:17 catalyst
2017-12-28 18:04 catalyst
2017-12-26 21:58 catalyst
2017-12-24 21:59 catalyst
2017-12-23  3:45 catalyst
2017-12-21 21:58 catalyst
2017-12-19 21:54 catalyst
2017-12-17 22:45 catalyst
2017-12-15  7:26 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=20180618061732.B2CAE649C5@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