Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 597630 - Genkernel autoselects 64-bit cpu on 32-bit hardware
Summary: Genkernel autoselects 64-bit cpu on 32-bit hardware
Status: RESOLVED DUPLICATE of bug 595432
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: x86 All
: Normal blocker (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-10-20 17:08 UTC by Victor Fugazzotto
Modified: 2016-10-20 17:11 UTC (History)
1 user (show)

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


Attachments
genkernel log file (genkernel.log,261.93 KB, text/plain)
2016-10-20 17:08 UTC, Victor Fugazzotto
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Victor Fugazzotto 2016-10-20 17:08:19 UTC
Created attachment 450838 [details]
genkernel log file

Using a vmware virtual machine setup for "Other Linux 3.x kernel" (not 64-bit), and following the x86 handbook, genkernel all command fails after auto selecting 64-bit cpu.

log file ends with:

kernel/bounds.c:1:0: error: CPU you selected does not support x86-64 instruction set 
 /* 
 ^ 
Kbuild:44: recipe for target 'kernel/bounds.s' failed 
make[1]: *** [kernel/bounds.s] Error 1 
make[1]: *** Waiting for unfinished jobs.... 
Makefile:987: recipe for target 'prepare0' failed 
make: *** [prepare0] Error 2 
* Gentoo Linux Genkernel; Version 3.4.52.3[0m 
* Running with options: all 
* Using genkernel.conf from /etc/genkernel.conf 
* Sourcing arch-specific config.sh from /usr/share/genkernel/arch/x86/config.sh .. 
* Sourcing arch-specific modules_load from /usr/share/genkernel/arch/x86/modules_load .. 

* ERROR: Failed to compile the "prepare" target... 
* 
* -- Grepping log... -- 
* 
* 
* -- End log... --

Used x86 minimal iso from October 4
Used stage3 archive and portage snapshot downloaded on October 18
Comment 1 Ben Kohler gentoo-dev 2016-10-20 17:11:31 UTC

*** This bug has been marked as a duplicate of bug 595432 ***