Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 682650 - sys-kernel/gentoo-sources-5.0.7 USE=default-gold fails to compile
Summary: sys-kernel/gentoo-sources-5.0.7 USE=default-gold fails to compile
Status: CONFIRMED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo Kernel Bug Wranglers and Kernel Maintainers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-04-06 07:36 UTC by mael
Modified: 2019-06-30 15:18 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description mael 2019-04-06 07:36:32 UTC
hi, both the newest updates on gentoo-sources (5.0.6 and 5.0.7) do not compile on my box!

i use also the binutils gold linker by default since binutils 2.31.1 via the "default-gold" use-flag.

i tested recompiling the kernels with default-gold disabled and it works as expected!

should we mask the "default-gold" useflag for gentoo-sources?
Comment 1 Jérôme Borme 2019-04-07 13:18:49 UTC
I had a similar issues after an upgrade to dev-libs/elfutils-0.176. The kernel compiles again after reverting to elfutils-0.170-r1. (I also have USE=gold)
Comment 2 Mike Pagano gentoo-dev 2019-06-10 19:54:40 UTC
5.0.X is EOL, but this should be fixed in >= 5.1.7

Have you moved to this series, yet?
Comment 3 Jérôme Borme 2019-06-30 15:01:13 UTC
binutils-2.32-r1 USE=gold
elfutils-0.176-r1
genkernel-3.5.3.3

-> cannot compile the kernel, gentoo-sources 5.1.15

According to external website:

https://unix.stackexchange.com/questions/483434/objdump-file-format-not-recognized

the problem is connected to bug 671650

I still can compile the kernel when reverting to elfutils-0.173-r1

With elfutils-0.176, here is the error with genkernel

* ERROR: Failed to compile the "bzImage" target...
*
* -- Grepping log... --
*
*objdump: arch/x86/kernel/acpi/cppc_msr.o: impossible d'initialiser le statut de décompression de la section .debug_info
*objdump: arch/x86/kernel/acpi/cppc_msr.o: format de fichier non reconnu
*objdump: mm/swap_cgroup.o: impossible d'initialiser le statut de décompression de la section .debug_info
*objdump: mm/swap_cgroup.o: impossible d'initialiser le statut de décompression de la section .debug_info
*objdump: mm/swap_cgroup.o: format de fichier non reconnu
*  CC      mm/memory-failure.o
*--
*  CC      kernel/irq/autoprobe.o
*objdump: arch/x86/kernel/apic/apic_noop.o: impossible d'initialiser le statut de décompression de la section .debug_info
*objdump: arch/x86/kernel/apic/apic_noop.o: impossible d'initialiser le statut de décompression de la section .debug_info
*objdump: arch/x86/kernel/apic/apic_noop.o: format de fichier non reconnu
*  CC      arch/x86/kernel/apic/vector.o
*objdump: mm/memory-failure.o: impossible d'initialiser le statut de décompression de la section .debug_info
*objdump: mm/memory-failure.o: impossible d'initialiser le statut de décompression de la section .debug_info
*objdump: mm/memory-failure.o: format de fichier non reconnu
*--
*ld: arch/x86/kernel/head_64.o: impossible d'initialiser le statut de décompression de la section .debug_line
*ld: arch/x86/kernel/head_64.o: impossible d'initialiser le statut de décompression de la section .debug_line
*ld: arch/x86/kernel/head_64.o: impossible d'initialiser le statut de décompression de la section .debug_line
*ld: arch/x86/kernel/head_64.o: impossible d'initialiser le statut de décompression de la section .debug_line
*arch/x86/kernel/head_64.o: file not recognized: format de fichier non reconnu
*make: *** [Makefile:1029: vmlinux] Error 1
Comment 4 Jérôme Borme 2019-06-30 15:18:39 UTC
Sorry for the noise. I found the correct place to report my problem is bug 671760.