Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] PATCH 2019.11 stable release, glibc/gcc busybox incompatible
Date: Fri, 13 Dec 2019 16:07:22 +0100	[thread overview]
Message-ID: <87d0csgt79.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <TY2PR02MB3727097C4CD9FC2CE591C5C1C9540@TY2PR02MB3727.apcprd02.prod.outlook.com> (zhou qi's message of "Fri, 13 Dec 2019 14:55:39 +0000")

>>>>> "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

  reply	other threads:[~2019-12-13 15:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-13 14:55 [Buildroot] PATCH 2019.11 stable release, glibc/gcc busybox incompatible zhou qi
2019-12-13 15:07 ` Peter Korsgaard [this message]
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

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=87d0csgt79.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox