Bug 588356 – dev-build/kbuild-0.1.9998_pre20131130 build failure with i686 userspace and x86_64 kernel

• Status: UNCONFIRMED
• Product: Gentoo Linux

[Description John Stein 2016-07-08 21:37:01 UTC]

Created attachment 440096 [details]
emerge error log, dev-util/kbuild-0.1.9998_pre20131130

I have been building many packages just fine until I:
 emerge x11-base/xorg-drivers

Failed with this final comment:
 Failed to emerge dev-util/kbuild-0.1.9998_pre20131130, Log file:
 '/var/log/portage/build/dev-util/kbuild-0.1.9998_pre20131130:20160708-204208.log'

I have attached the log.

Thank you much for your time,
Aksornsri

[Comment 1 John Stein 2016-07-08 21:48:13 UTC]

Created attachment 440098 [details]
current USE flags for the build

[Comment 2 John Stein 2016-07-09 13:52:43 UTC]

Created attachment 440180 [details]
emerge--info post as instructed by fail comment

[Comment 3 John Stein 2016-07-09 13:54:23 UTC]

Created attachment 440182 [details]
emerge -pqv post as instructed by fail comment

[Comment 4 John Stein 2016-07-09 14:02:16 UTC]

Am receiving this error comment in the build output:
 error: CPU you selected does not support x86-64 instruction set

This is strange because I am using:
 CFLAGS="-O2 -march=i686 -pipe"
and
 CHOST="i686-pc-linux-gnu"
in my make.conf.

Thanks,
John Stein

[Comment 5 Adam Feldman 2016-07-11 00:23:35 UTC]

Please leave the assessment of importance to bug wranglers and maintainers.  For most cases, it is more of an internal-use-only setting and doesn't cause bugs to be assessed faster.

[Comment 6 Zac Medico 2016-07-11 00:39:17 UTC]

(In reply to John Stein from comment #4)
> Am receiving this error comment in the build output:
>  error: CPU you selected does not support x86-64 instruction set
> 
> This is strange because I am using:
>  CFLAGS="-O2 -march=i686 -pipe"
> and
>  CHOST="i686-pc-linux-gnu"
> in my make.conf.

For many packages you have to run emerge under the linux32 command, which causes uname to report i686. Otherwise, things that rely on the uname will misbehave.