From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] qemu-aarch64 applications misbehaving
Date: Tue, 20 Nov 2018 17:13:35 +0100 [thread overview]
Message-ID: <20181120171335.29820f02@windsurf> (raw)
In-Reply-To: <d2bbad73-b8a5-917a-1a10-a2b702cdcb34@googlemail.com>
Hello,
+Waldemar in Cc, as the uClibc-ng maintainer.
On Tue, 20 Nov 2018 14:55:32 +0100, Zeno Endemann wrote:
> > Hello,
> >
> > On Tue, 20 Nov 2018 00:11:13 -0200, Ricardo Martincoski wrote:
> >
> >> I confirm 'df' printing silly numbers with both these images:
> >> 2018.08.2 : https://gitlab.com/RicardoMartincoski/buildroot/-/jobs/122632959
> >> 2018.11-rc1 : https://gitlab.com/buildroot.org/buildroot/-/jobs/118747268
> >>
> >> On 2018.08.2 I also did this:
> >> make qemu_aarch64_virt_defconfig
> >> make menuconfig # and enable BR2_PACKAGE_HOST_QEMU_SYSTEM_MODE
> >> make host-qemu # to build qemu 2.12.1
> >> output/host/bin/qemu-system-aarch64 ...
> >> and the issue with 'df' still occurs.
> >
> > So you tested with the default C library, uClibc ? Could you test with
> > glibc ?
>
> Indeed, all problems were resolved by changing to glibc. Thanks!
OK, so there's a uClibc-ng bug somewhere. Waldemar ? :-)
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-11-20 16:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-20 13:55 [Buildroot] qemu-aarch64 applications misbehaving Zeno Endemann
2018-11-20 16:13 ` Thomas Petazzoni [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-11-19 16:04 Zeno Endemann
2018-11-20 2:11 ` Ricardo Martincoski
2018-11-20 10:39 ` Thomas Petazzoni
2018-12-03 8:16 ` Thomas Petazzoni
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=20181120171335.29820f02@windsurf \
--to=thomas.petazzoni@bootlin.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 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.