From: "orbea" <orbea@riseup.net>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/libressl:master commit in: dev-qt/qtbase/
Date: Thu, 28 Sep 2023 16:55:46 +0000 (UTC) [thread overview]
Message-ID: <1695920100.4b6142a6a563a9562c6de691a8cdedbe43164673.orbea@gentoo> (raw)
commit: 4b6142a6a563a9562c6de691a8cdedbe43164673
Author: orbea <orbea <AT> riseup <DOT> net>
AuthorDate: Thu Sep 28 16:55:00 2023 +0000
Commit: orbea <orbea <AT> riseup <DOT> net>
CommitDate: Thu Sep 28 16:55:00 2023 +0000
URL: https://gitweb.gentoo.org/repo/proj/libressl.git/commit/?id=4b6142a6
dev-qt/qtbase: keyword 6.5.2-r2 for ~hppa, ~loong
Signed-off-by: orbea <orbea <AT> riseup.net>
dev-qt/qtbase/qtbase-6.5.2-r2.ebuild | 26 ++++++++++++++++++++------
1 file changed, 20 insertions(+), 6 deletions(-)
diff --git a/dev-qt/qtbase/qtbase-6.5.2-r2.ebuild b/dev-qt/qtbase/qtbase-6.5.2-r2.ebuild
index 34dd3d1..9a24676 100644
--- a/dev-qt/qtbase/qtbase-6.5.2-r2.ebuild
+++ b/dev-qt/qtbase/qtbase-6.5.2-r2.ebuild
@@ -8,7 +8,7 @@ inherit flag-o-matic qt6-build toolchain-funcs
DESCRIPTION="Cross-platform application development framework"
if [[ ${QT6_BUILD_TYPE} == release ]]; then
- KEYWORDS="amd64 ~arm ~arm64 ~x86"
+ KEYWORDS="amd64 ~arm ~arm64 ~hppa ~loong ~x86"
fi
declare -A QT6_IUSE=(
@@ -86,7 +86,10 @@ RDEPEND="
eglfs? ( media-libs/mesa[gbm(+)] )
evdev? ( sys-libs/mtdev )
libinput? ( dev-libs/libinput:= )
- opengl? ( media-libs/libglvnd[X?] )
+ opengl? (
+ gles2-only? ( media-libs/libglvnd )
+ !gles2-only? ( media-libs/libglvnd[X?] )
+ )
tslib? ( x11-libs/tslib )
widgets? (
cups? ( net-print/cups )
@@ -130,7 +133,9 @@ PDEPEND="
"
PATCHES=(
- "${FILESDIR}/${PN}-6.5.0-libressl.patch"
+ "${FILESDIR}"/${PN}-6.5.0-libressl.patch
+ "${FILESDIR}"/${PN}-6.5.2-hppa-forkfd-grow-stack.patch
+ "${FILESDIR}"/${PN}-6.5.2-no-glx.patch
"${FILESDIR}"/${PN}-6.5.2-no-symlink-check.patch
"${FILESDIR}"/${P}-CVE-2023-38197.patch
"${FILESDIR}"/${P}-tests-gcc13.patch
@@ -285,7 +290,7 @@ src_test() {
tst_qsctpsocket
# these can be flaky depending on the environment/toolchain
tst_qlogging # backtrace log test can easily vary
- tst_qrawfont # can be affected by available fonts
+ tst_q{,raw}font # affected by available fonts / settings (bug #914737)
tst_qstorageinfo # checks mounted filesystems
# flaky due to using different test framework and fails with USE=-gui
tst_selftests
@@ -300,17 +305,26 @@ src_test() {
tst_qglyphrun
tst_qvectornd
tst_rcc
- # similarly, but on armv7 (bug #914028)
+ # similarly, but on armv7 and potentially others (bug #914028)
tst_qlineedit
tst_qpainter
+ # likewise, known failing at least on BE arches (bug #914033,914371)
+ tst_qimagereader
+ tst_qimagewriter
+ tst_qpluginloader
# partially broken on llvm-musl, needs looking into but skip to have
- # a baseline for regressions (like above, rest of dev-qt is fine)
+ # a baseline for regressions (rest of dev-qt still passes with musl)
$(usev elibc_musl '
tst_qfiledialog2
tst_qicoimageformat
tst_qimagereader
tst_qimage
')
+ # fails due to hppa's NaN handling, needs looking into (bug #914371)
+ $(usev hppa '
+ tst_qcborvalue
+ tst_qnumeric
+ ')
# note: for linux, upstream only really runs+maintains tests for amd64
# https://doc.qt.io/qt-6/supported-platforms.html
)
next reply other threads:[~2023-09-28 16:55 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-28 16:55 orbea [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-08-01 17:58 [gentoo-commits] repo/proj/libressl:master commit in: dev-qt/qtbase/ orbea
2024-07-22 4:44 orbea
2024-07-22 4:44 orbea
2024-07-10 13:30 orbea
2024-07-05 2:04 orbea
2024-06-28 21:14 orbea
2024-06-11 19:21 orbea
2024-05-31 0:59 orbea
2024-04-22 23:44 orbea
2024-04-02 18:50 orbea
2024-04-02 18:50 orbea
2024-03-24 15:22 orbea
2024-02-20 18:29 orbea
2024-02-16 15:02 orbea
2024-01-25 15:33 orbea
2024-01-20 15:34 orbea
2023-12-29 15:34 orbea
2023-12-06 4:58 orbea
2023-11-07 14:36 orbea
2023-10-22 16:54 orbea
2023-09-17 16:22 orbea
2023-05-23 13:17 orbea
2023-04-13 2:19 orbea
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=1695920100.4b6142a6a563a9562c6de691a8cdedbe43164673.orbea@gentoo \
--to=orbea@riseup.net \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/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