From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11346] qt5base-5.11.1 Assertion failed: ret == 0 after getentropy() inside fillBuffer() on arm
Date: Fri, 02 Nov 2018 14:45:25 +0000 [thread overview]
Message-ID: <bug-11346-163-xLIoI8OzVV@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-11346-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=11346
--- Comment #6 from Peter Seiderer <ps.report@gmx.net> ---
(In reply to Thomas Petazzoni from comment #5)
I believe Qt is using the glibc function/wrapper [1] and is already
checking for availability of it [2] at configure time and further assumes
the running kernel supports it (no returning ENOSYS, maybe this part
could be improved on the qt side), or add the -no-feature-getentropy
to buildroot if the selected kerne does not support it?
[1] http://man7.org/linux/man-pages/man3/getentropy.3.html
[2] http://code.qt.io/cgit/qt/qtbase.git/tree/config.tests/unix/getentropy
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2018-11-02 14:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-12 10:10 [Buildroot] [Bug 11346] New: qt5base-5.11.1 Assertion failed: ret == 0 after getentropy() inside fillBuffer() on arm bugzilla at busybox.net
2018-09-12 16:00 ` [Buildroot] [Bug 11346] " bugzilla at busybox.net
2018-09-12 16:23 ` bugzilla at busybox.net
2018-09-12 21:23 ` bugzilla at busybox.net
2018-09-13 12:23 ` bugzilla at busybox.net
2018-11-02 9:53 ` bugzilla at busybox.net
2018-11-02 14:45 ` bugzilla at busybox.net [this message]
2024-06-15 14:48 ` 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-11346-163-xLIoI8OzVV@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.