Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
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 09:53:59 +0000	[thread overview]
Message-ID: <bug-11346-163-rYjE8yubLT@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-11346-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=11346

Thomas Petazzoni <thomas.petazzoni@free-electrons.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Assignee|unassigned at buildroot.uclibc |ps.report at gmx.net
                   |.org                        |

--- Comment #5 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> ---
Peter, how can we make progress with this issue? To me, it is weird that such
things are not auto-detected. It should be known by looking at the kernel
headers whether the getentropy() system call is supported or not. It shouldn't
be needed to explicitly tell Qt about this.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2018-11-02  9:53 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 [this message]
2018-11-02 14:45 ` bugzilla at busybox.net
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-rYjE8yubLT@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox