[Buildroot] [Bug 13621] New: Buildroot builds for i686 even though i486 is selected

[Buildroot] [Bug 13621] New: Buildroot builds for i686 even though i486 is selected

[bugzilla at busybox.net]

https://bugs.busybox.net/show_bug.cgi?id=13621

            Bug ID: 13621
           Summary: Buildroot builds for i686 even though i486 is selected
           Product: buildroot
           Version: 2021.02
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned at buildroot.uclibc.org
          Reporter: moelzerjens at gmail.com
                CC: buildroot at uclibc.org
  Target Milestone: ---

Created attachment 8801
  --> https://bugs.busybox.net/attachment.cgi?id=8801&action=edit
defconfig

Selecting i486 as target architecture variant results in a kernel that's built
for i686.

Steps to reproduce:

Build a image with the attached minimal defconfig and run `qemu-system-i386
-nographic -cpu 486 -kernel output/images/bzImage` results in `This kernel
requires an i686 CPU, but only detected an i486 CPU.`.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Buildroot] [Bug 13621] Buildroot builds for i686 even though i486 is selected

[bugzilla at busybox.net]

https://bugs.busybox.net/show_bug.cgi?id=13621

--- Comment #1 from Peter Seiderer <ps.report@gmx.net> ---
(In reply to moelzerjens from comment #0)

The buildroot kernel configure/make is called with the correct 'ARCH=i386' and
uses the kernel i386_defconfig without further specification of CPU type, which
defaults from the linux kernel configure (see e.g.
build/linux-5.11/arch/x86/Kconfig.cpu) to M686:

  choice
        prompt "Processor family"
        default M686 if X86_32
        default GENERIC_CPU if X86_64

For workaround specify the correct CPU either by configuring a custom linux
kernel config/defconfig file (or configure by 'make linux-menuconfig')...

Maybe something which can be improved in buildroot..., on the other side a very
special use-case ;-)

-- 
You are receiving this mail because:
You are on the CC list for the bug.