* [Buildroot] PATCH 2019.11 stable release, glibc/gcc busybox incompatible
@ 2019-12-13 14:55 zhou qi
2019-12-13 15:07 ` Peter Korsgaard
0 siblings, 1 reply; 6+ messages in thread
From: zhou qi @ 2019-12-13 14:55 UTC (permalink / raw)
To: buildroot
I may found a bug of 2019.11 release, plz someone (developers) test it.
I found use the 2019.11 release to build i386 image have following error for busybox/gcc
traps: xxx[xxx] general protection ip:xxx sp:xxx error:0 in libc.so[xxx+xxx]
I added a patch to busybox(in dir packages/busybox/), then the error does not shown again. The patch just remove
all busybox i386 specific build flags. Here is the content of it.
--- busybox-1.31.1.orig/arch/i386/Makefile 2019-06-10 18:50:53.000000000 +0800
+++ busybox-1.31.1/arch/i386/Makefile 2019-12-12 09:50:28.072043566 +0800
@@ -4,10 +4,10 @@
# Allow i486 insns (basically, bswap insn)
# Do not try to tune for 486+ (might add padding)
-CFLAGS += $(call cc-option,-march=i486 -mtune=i386,)
+# CFLAGS += $(call cc-option,-march=i486 -mtune=i386,)
-ifeq ($(CONFIG_STACK_OPTIMIZATION_386),y)
+# ifeq ($(CONFIG_STACK_OPTIMIZATION_386),y)
# -mpreferred-stack-boundary=2 is essential in preventing gcc 4.2.x
# from aligning stack to 16 bytes. (Which is gcc's way of supporting SSE).
-CFLAGS += $(call cc-option,-mpreferred-stack-boundary=2,)
-endif
+# CFLAGS += $(call cc-option,-mpreferred-stack-boundary=2,)
+# endif
And I tried to downgrade the gcc version, it could fixed the issue too.
Here is the procedure to reproduce the bug.
I downloaded 2019.11 stable release from https://buildroot.org/downloads/buildroot-2019.11.tar.gz
And use the following command to build a simple i386 image.
1. make pc_x86_64_defconfig
2. make menuconfig
# chang arch to i386, change libc to glibc save the config, then type
1. make
use qemu to test:
sudo ~/opt/qemu-4.1.1/bin/qemu-system-x86_64 --enable-kvm output/images/disk.img -m 512 -boot d -usb -device usb-tablet -soundhw sb16 -monitor stdio -cpu qemu64 -vga std
after boot, type some some busybox command, the you I get those errors:
traps: xxx[xxx] general protection ip:xxx sp:xxx error:0 in libc.so[xxx+xxx]
here is the links how I get those patch.
https://github.com/openwrt/openwrt/commit/7a97588bc6ae70a134456833d4d489148e38a5aa
https://github.com/openwrt/openwrt/commit/b8d9a064f08614ac6f6b0ec26eab1450cf8b7544
Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20191213/60bdcad2/attachment.html>
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Buildroot] PATCH 2019.11 stable release, glibc/gcc busybox incompatible
2019-12-13 14:55 [Buildroot] PATCH 2019.11 stable release, glibc/gcc busybox incompatible zhou qi
@ 2019-12-13 15:07 ` Peter Korsgaard
2019-12-13 15:30 ` zhou qi
0 siblings, 1 reply; 6+ messages in thread
From: Peter Korsgaard @ 2019-12-13 15:07 UTC (permalink / raw)
To: buildroot
>>>>> "zhou" == zhou qi <atmgnd@outlook.com> writes:
> I may found a bug of 2019.11 release, plz someone (developers) test it.
> I found use the 2019.11 release to build i386 image have following error for busybox/gcc
> I downloaded 2019.11 stable release from https://buildroot.org/downloads/buildroot-2019.11.tar.gz
> And use the following command to build a simple i386 image.
> 1. make pc_x86_64_defconfig
> 2. make menuconfig
> # chang arch to i386, change libc to glibc save the config, then type
I take it you have left the CPU variant alone, E.G. still nocona?
> 1. make
> use qemu to test:
> sudo ~/opt/qemu-4.1.1/bin/qemu-system-x86_64 --enable-kvm output/images/disk.img -m 512 -boot d -usb -device usb-tablet -soundhw sb16 -monitor stdio -cpu qemu64 -vga std
On what hardware and OS are you running this?
--
Bye, Peter Korsgaard
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Buildroot] PATCH 2019.11 stable release, glibc/gcc busybox incompatible
2019-12-13 15:07 ` Peter Korsgaard
@ 2019-12-13 15:30 ` zhou qi
2019-12-13 15:41 ` zhou qi
0 siblings, 1 reply; 6+ messages in thread
From: zhou qi @ 2019-12-13 15:30 UTC (permalink / raw)
To: buildroot
I build on ubuntu 19.04 64bit, intel i3 cpu.
Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10
________________________________
From: Peter Korsgaard <jacmet@gmail.com> on behalf of Peter Korsgaard <peter@korsgaard.com>
Sent: Friday, December 13, 2019 11:07:22 PM
To: zhou qi <atmgnd@outlook.com>
Cc: buildroot at busybox.net <buildroot@busybox.net>
Subject: Re: PATCH 2019.11 stable release, glibc/gcc busybox incompatible
>>>>> "zhou" == zhou qi <atmgnd@outlook.com> writes:
> I may found a bug of 2019.11 release, plz someone (developers) test it.
> I found use the 2019.11 release to build i386 image have following error for busybox/gcc
> I downloaded 2019.11 stable release from https://buildroot.org/downloads/buildroot-2019.11.tar.gz
> And use the following command to build a simple i386 image.
> 1. make pc_x86_64_defconfig
> 2. make menuconfig
> # chang arch to i386, change libc to glibc save the config, then type
I take it you have left the CPU variant alone, E.G. still nocona?
> 1. make
> use qemu to test:
> sudo ~/opt/qemu-4.1.1/bin/qemu-system-x86_64 --enable-kvm output/images/disk.img -m 512 -boot d -usb -device usb-tablet -soundhw sb16 -monitor stdio -cpu qemu64 -vga std
On what hardware and OS are you running this?
--
Bye, Peter Korsgaard
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20191213/7e75e55d/attachment.html>
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Buildroot] PATCH 2019.11 stable release, glibc/gcc busybox incompatible
2019-12-13 15:30 ` zhou qi
@ 2019-12-13 15:41 ` zhou qi
2019-12-14 14:52 ` Peter Korsgaard
0 siblings, 1 reply; 6+ messages in thread
From: zhou qi @ 2019-12-13 15:41 UTC (permalink / raw)
To: buildroot
And Yes, the CPU variant or E.G.
Only arch to i386, libc to glibc
Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10
________________________________
From: zhou qi <atmgnd@outlook.com>
Sent: Friday, December 13, 2019 11:30:25 PM
To: Peter Korsgaard <peter@korsgaard.com>
Cc: buildroot at busybox.net <buildroot@busybox.net>
Subject: RE: PATCH 2019.11 stable release, glibc/gcc busybox incompatible
I build on ubuntu 19.04 64bit, intel i3 cpu.
Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10
________________________________
From: Peter Korsgaard <jacmet@gmail.com> on behalf of Peter Korsgaard <peter@korsgaard.com>
Sent: Friday, December 13, 2019 11:07:22 PM
To: zhou qi <atmgnd@outlook.com>
Cc: buildroot at busybox.net <buildroot@busybox.net>
Subject: Re: PATCH 2019.11 stable release, glibc/gcc busybox incompatible
>>>>> "zhou" == zhou qi <atmgnd@outlook.com> writes:
> I may found a bug of 2019.11 release, plz someone (developers) test it.
> I found use the 2019.11 release to build i386 image have following error for busybox/gcc
> I downloaded 2019.11 stable release from https://buildroot.org/downloads/buildroot-2019.11.tar.gz
> And use the following command to build a simple i386 image.
> 1. make pc_x86_64_defconfig
> 2. make menuconfig
> # chang arch to i386, change libc to glibc save the config, then type
I take it you have left the CPU variant alone, E.G. still nocona?
> 1. make
> use qemu to test:
> sudo ~/opt/qemu-4.1.1/bin/qemu-system-x86_64 --enable-kvm output/images/disk.img -m 512 -boot d -usb -device usb-tablet -soundhw sb16 -monitor stdio -cpu qemu64 -vga std
On what hardware and OS are you running this?
--
Bye, Peter Korsgaard
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20191213/9ed35eb1/attachment.html>
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Buildroot] PATCH 2019.11 stable release, glibc/gcc busybox incompatible
2019-12-13 15:41 ` zhou qi
@ 2019-12-14 14:52 ` Peter Korsgaard
2019-12-14 14:59 ` zhou qi
0 siblings, 1 reply; 6+ messages in thread
From: Peter Korsgaard @ 2019-12-14 14:52 UTC (permalink / raw)
To: buildroot
>>>>> "zhou" == zhou qi <atmgnd@outlook.com> writes:
> And Yes, the CPU variant or E.G.
> Only arch to i386, libc to glibc
Interesting. I can reproduce it as well, but only with
-enable-kvm. Without -enable-kvm it works fine here. Maybe it is a bug
in kvm?
Notice that we do have a dedicated i386 qemu defconfig
(qemu_x86_defconfig). I just tried building that with glibc and that
runs without issues here with/without -enable-kvm.
--
Bye, Peter Korsgaard
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Buildroot] PATCH 2019.11 stable release, glibc/gcc busybox incompatible
2019-12-14 14:52 ` Peter Korsgaard
@ 2019-12-14 14:59 ` zhou qi
0 siblings, 0 replies; 6+ messages in thread
From: zhou qi @ 2019-12-14 14:59 UTC (permalink / raw)
To: buildroot
I don?t so, I tested using a real i3 cpu(6th), get this error too.
traps: xxx[xxx] general protection ip ...
Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10
________________________________
From: Peter Korsgaard <jacmet@gmail.com> on behalf of Peter Korsgaard <peter@korsgaard.com>
Sent: Saturday, December 14, 2019 10:52:16 PM
To: zhou qi <atmgnd@outlook.com>
Cc: buildroot at busybox.net <buildroot@busybox.net>
Subject: Re: PATCH 2019.11 stable release, glibc/gcc busybox incompatible
>>>>> "zhou" == zhou qi <atmgnd@outlook.com> writes:
> And Yes, the CPU variant or E.G.
> Only arch to i386, libc to glibc
Interesting. I can reproduce it as well, but only with
-enable-kvm. Without -enable-kvm it works fine here. Maybe it is a bug
in kvm?
Notice that we do have a dedicated i386 qemu defconfig
(qemu_x86_defconfig). I just tried building that with glibc and that
runs without issues here with/without -enable-kvm.
--
Bye, Peter Korsgaard
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20191214/266129b3/attachment.html>
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2019-12-14 14:59 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2019-12-13 14:55 [Buildroot] PATCH 2019.11 stable release, glibc/gcc busybox incompatible zhou qi
2019-12-13 15:07 ` Peter Korsgaard
2019-12-13 15:30 ` zhou qi
2019-12-13 15:41 ` zhou qi
2019-12-14 14:52 ` Peter Korsgaard
2019-12-14 14:59 ` zhou qi
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox