Summary: | sys-kernel/genkernel fails to compile kernel 4.14 | ||
---|---|---|---|
Product: | Gentoo Hosted Projects | Reporter: | Vit Pelcak <v.pelcak> |
Component: | genkernel | Assignee: | Gentoo Genkernel Maintainers <genkernel> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | cissusnar, devel, fabrizio.bertolacci, gentoo_bugs.nu_q5v, mudler, tb, tsmksubc |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
See Also: | https://bugs.gentoo.org/show_bug.cgi?id=641774 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Vit Pelcak
2017-11-16 18:15:01 UTC
4.14 no longer supports in-kernel firmware at all. I'll amend the check to forcibly bail out, but you need to migrate yourself as previously noted by genkernel. For the moment, disable FIRMWARE_INSTALL in your config. The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ba0de310141c3f0863688e7eae78bc8f591efce8 commit ba0de310141c3f0863688e7eae78bc8f591efce8 Author: Robin H. Johnson <robbat2@gentoo.org> AuthorDate: 2017-11-16 23:41:11 +0000 Commit: Robin H. Johnson <robbat2@gentoo.org> CommitDate: 2017-11-16 23:44:12 +0000 sys-kernel/genkernel: bump. Fixes: https://bugs.gentoo.org/637698 Fixes: https://bugs.gentoo.org/637446 Package-Manager: Portage-2.3.8, Repoman-2.3.3 sys-kernel/genkernel/Manifest | 1 + sys-kernel/genkernel/genkernel-3.5.2.4.ebuild | 165 ++++++++++++++++++++++++++ 2 files changed, 166 insertions(+) *** Bug 638018 has been marked as a duplicate of this bug. *** FIRMWARE="no" in /etc/genkernel.conf does NOT solve the problem. Upgrading to genkernel 3.5.2.4 solves the problem. (and thanks to the devs for the quick action) FIRMWARE_INSTALL=no is the workaround. Hello. Just a question, why was this bug changed from genkernel-next to genkernel? If genkernel-next no longer supported or was the summary where I forgot to explicitly mention genkernel-next misleading? Hello. Just a question, why was this bug changed from genkernel-next to genkernel? If genkernel-next no longer supported or was the summary where I forgot to explicitly mention genkernel-next misleading? (In reply to Vit Pelcak from comment #8) > Hello. > > Just a question, why was this bug changed from genkernel-next to genkernel? > > If genkernel-next no longer supported or was the summary where I forgot to > explicitly mention genkernel-next misleading? It was unclear and really affects both. genkernel-next should import this patch as well in a new release. CC'ing back the genkernel-next maintainer Nothing in the original report other than the component said genkernel-next. muddler: can you throw a small patch onto gk-next that changes the log destinations and bug reporting details? Just got bit by this bug when gentoo-sources 4.14.7 was marked stable...had to pull in genkernel 3.5.2.4 (still keyworded) to get it to build. *** Bug 641824 has been marked as a duplicate of this bug. *** Same here, with genkernel-next-66. Happens on compiling both 4.14.7 and 4.14.8-r1 kernels. Also hoping for a patch on genkernel-next. *** Bug 642022 has been marked as a duplicate of this bug. *** it would be nice if someone with proper permissions could change the subject to "sys-kernel/genkernel" instead of just "genkernel" so this will pop up on a search like this: https://bugs.gentoo.org/buglist.cgi?quicksearch=ALL%20sys-kernel%2Fgenkernel maybe is better to mask affected genkernels for the moment alicef: please don't reopen like this. This is fixed in ~arch versions already, and I'm trying to get a stable out the door. *** Bug 642438 has been marked as a duplicate of this bug. *** |