From: Jack <ostroffjh@users.sourceforge.net>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] new genkernel problem
Date: Fri, 05 Jun 2020 15:01:52 -0400 [thread overview]
Message-ID: <R4EVA36R.U2XPV3NI.3JPYGUJV@GDO5ZTP2.SGXOR6FS.BARIHTGW> (raw)
I'm currently running a 5.6.10 kernel, compiled with genkernel along
with an initramfs. That was compiled with gcc-9.3.0. Since then,
using gcc-10.1.0, I have not successfully run genkernel. Initially it
was kernel compile failures due to the -fnocommon bug. With a patch,
the kernel compile completed fine, and the patch is no longer needed
for 5.6.16 or 5.7.0. However, all recent attempts at running genkernel
fail during creation of initramfs. (This is genkernel-9999, re-emerged
yesterday.)
* Gentoo Linux Genkernel; Version 4.0.7-4-g06acd6f-git
* Using genkernel configuration from '/etc/genkernel.conf' ...
* Running with options: --lvm --firmware --microcode
--kernel-append-localversion=-gcc-10 all
* Working with Linux kernel 5.7.0-gentoo-x86_64-gcc-10-01 for x86_64
* Using kernel config file
'/etc/kernels/kernel-config-5.7.0-gentoo-x86_64-gcc-10-01' ...
*
* Note: The version above is subject to change (depends on config and
status of kernel sources).
* kernel: >> Initializing ...
* >> Running 'make clean' ...
* >> --no-mrproper is set; Skipping 'make mrproper' ...
* >> --no-oldconfig is set; Skipping 'make oldconfig' ...
* >> Running 'make olddefconfig' due to changed kernel options
...
* >> Kernel version has changed (probably due to config change)
since genkernel start:
* We are now building Linux kernel
5.7.0-gentoo-x86_64-gcc-10 for x86_64 ...
* >> Compiling 5.7.0-gentoo-x86_64-gcc-10 bzImage ...
* >> Compiling 5.7.0-gentoo-x86_64-gcc-10 modules ...
* >> Installing 5.7.0-gentoo-x86_64-gcc-10 modules (and
stripping) ...
* >> Generating module dependency data ...
* >> Compiling out-of-tree module(s) ...
* >> Saving config of successful build to
'/etc/kernels/kernel-config-5.7.0-gentoo-x86_64-gcc-10' ...
* initramfs: >> Initializing ...
* >> Appending devices cpio data ...
* >> Appending base_layout cpio data ...
* >> Appending auxilary cpio data ...
* >> Appending busybox cpio data ...
* >> Appending blkid cpio data ...
* >> Appending gpg cpio data ...
* ERROR: Command 'nice -n10 make -j8 --load-average 10 V=1' failed!
* ERROR: create_initramfs(): append_data(): append_gpg():
populate_binpkg(): gkbuild(): Failed to create binpkg of gnupg-1.4.23!
and, of course, I wouldn't really expect gcc-10 to be able to compile
gnupg-1.4.23. (The detailed log does show the multiple definition
errors.) That version of gnupg is coded in the ebuild, so hopefully
there is SOME reason for selecting it. Also - I now see that I can
give --no-gpg to genkernel to omit gnupg from the initramfs - that's
running now.
I'd be surprised if I am really the only one facing this, but I haven't
found any other reports. (It's quite possible my search-fu isn't.) I
don't know exactly when this started showing up, since I THOUGHT I had
run genkernel successfully since then, but although there are several
vmlinuz and sysmap files in /boot, there is only the single initramfs
which I currently boot with.
Thanks for any thoughts or suggestions.
Jack
next reply other threads:[~2020-06-05 19:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-05 19:01 Jack [this message]
2020-06-05 20:24 ` [gentoo-user] new genkernel problem Andrew Udvare
2020-06-05 20:48 ` Jack
2020-06-05 22:46 ` Neil Bothwick
2020-06-05 20:57 ` Dale
2020-06-05 22:51 ` Neil Bothwick
2020-06-06 15:13 ` Dale
2020-06-06 16:13 ` Neil Bothwick
2020-06-06 16:34 ` Dale
2020-06-06 17:20 ` Jack
2020-06-06 22:11 ` Neil Bothwick
2020-06-06 22:34 ` Dale
2020-06-06 23:55 ` Jack
2020-06-11 14:18 ` antlists
2020-06-11 17:04 ` madscientistatlarge
2020-06-11 22:08 ` madscientistatlarge
2020-06-12 17:19 ` antlists
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=R4EVA36R.U2XPV3NI.3JPYGUJV@GDO5ZTP2.SGXOR6FS.BARIHTGW \
--to=ostroffjh@users.sourceforge.net \
--cc=gentoo-user@lists.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