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: Thu, 13 Sep 2018 12:23:42 +0000	[thread overview]
Message-ID: <bug-11346-163-LYK4TtcEoc@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 #4 from Philipp Richter <richterphilipp.pops@gmail.com> ---
(In reply to Peter Seiderer from comment #3)

I've tried that in the past but there's still too much missing or partially
implemented in mainline for it to work. I'm keeping an eye on
http://linux-meson.com/doku.php for S805, meson8b to see the progress. But then
again newer boards have a higher priority which is understandable.

I found out that on archlinux arm for qt5base they have :
-no-reduce-relocations
-no-feature-getentropy

enabled in the the configure options by default.

See:
https://github.com/archlinuxarm/PKGBUILDs/blob/master/extra/qt5-base/PKGBUILD

So I added -no-feature-getentropy to the custom configure options in buildroot
like this:

BR2_PACKAGE_QT5BASE_CUSTOM_CONF_OPTS="-no-feature-getentropy"

And it's all well now, working with latest qt5base.

No issue on Raspberry Pi btw so the culprit is of course the old kernel.

I'm not sure where to go with this now, it's an edge case of my particular
setup.

Maybe having an explicit config option appear on the qt5base package for
getentropy() might be useful for people restricted by an old kernel version ?

Or a hint on a wiki might be enough.

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

  parent reply	other threads:[~2018-09-13 12:23 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 [this message]
2018-11-02  9:53 ` bugzilla at busybox.net
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-LYK4TtcEoc@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