On Mon, 11 May 2020 09:44:54 -0700
stan <[email protected]> wrote:

> On Mon, 11 May 2020 11:30:26 -0500
> Justin Forbes <[email protected]> wrote:
> 
> > when building the kernel with multiple threads, it is entirely
> > possible that the failure happens in one thread, but the remaining
> > threads make noise while they continue their current task. The error
> > can end up a good bit higher in the build log. It is best to look
> > through the entire log.  The current 5.7 kernels do have some
> > changes to support GCC 10, but they should continue to build fine
> > on F31 as well, and the ELN builds of these kernels are doing
> > headers and tools as well, so the spec should be working with that
> > now.  
> 
> Thank you, I'll look into that.

This is the actual error.

arch/x86/kernel/setup.c: In function 'rh_check_supported':
arch/x86/kernel/setup.c:824:11: error: 'x86_hyper_type' undeclared (first use 
in this function); did you mean 'x86_hyper_init'?
  824 |  guest = (x86_hyper_type != X86_HYPER_NATIVE || 
boot_cpu_has(X86_FEATURE_HYPERVISOR));
      |           ^~~~~~~~~~~~~~
      |           x86_hyper_init
arch/x86/kernel/setup.c:824:11: note: each undeclared identifier is reported 
only once for each function it appears in
At top level:
arch/x86/kernel/setup.c:820:13: warning: 'rh_check_supported' defined but not 
used [-Wunused-function]
  820 | static void rh_check_supported(void)
      |             ^~~~~~~~~~~~~~~~~~
make[2]: *** [scripts/Makefile.build:267: arch/x86/kernel/setup.o] Error 1
make[1]: *** [scripts/Makefile.build:488: arch/x86/kernel] Error 2
make: *** [Makefile:1732: arch/x86] Error 2
make: *** Waiting for unfinished jobs....
_______________________________________________
kernel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/[email protected]

Reply via email to