From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 13621] New: Buildroot builds for i686 even though i486 is selected
Date: Wed, 17 Mar 2021 14:19:03 +0000 [thread overview]
Message-ID: <bug-13621-163@https.bugs.busybox.net/> (raw)
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.
next reply other threads:[~2021-03-17 14:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-17 14:19 bugzilla at busybox.net [this message]
2021-03-18 21:08 ` [Buildroot] [Bug 13621] Buildroot builds for i686 even though i486 is selected bugzilla at busybox.net
2024-06-15 14:56 ` bugzilla
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-13621-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.