From: ar-jan <ar-jan@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: qscintilla-qt5 update to 2.12.1, new package python3-pyqt5-qsci
Date: Sun, 29 Jan 2023 14:19:19 +0100 [thread overview]
Message-ID: <20230129131919.r9nqaaTxdYxFEztp7r43hPMPhw9Zxl0hworZW2UGapI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31620@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 807 bytes --]
New comment by ar-jan on void-packages repository
https://github.com/void-linux/void-packages/pull/31620#issuecomment-1407661908
Comment:
Compilation on ARM no longer works:
> => python3-pyqt5-qsci-2.12.1_1: running do_configure ...
> Querying qmake about your Qt installation...
> Checking to see if the Qsci bindings can be built...
> sip-build: '/builddir/python3-pyqt5-qsci-2.12.1/Python/build/cfgtest_Qsci/./Qsci' didn't create any output
> => ERROR: python3-pyqt5-qsci-2.12.1_1: do_configure: 'sip-build --no-make ${_qt:+--qmake "$XBPS_WRAPPERDIR/sip-qmake"} --api-dir /usr/share/$_qt/qsci/api/python $configure_args --build-dir "$sip_builddir"' exited with 1
> => ERROR: in do_configure() at common/build-style/sip-build.sh:124
I am using this in #41812 so I'm hoping this can get in.
next prev parent reply other threads:[~2023-01-29 13:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-23 0:46 [PR PATCH] " sgn
2021-06-23 1:09 ` [PR PATCH] [Updated] " sgn
2022-05-23 2:12 ` github-actions
2022-06-04 19:58 ` gabriel-russo
2022-09-03 2:14 ` github-actions
2022-09-03 2:18 ` sgn
2022-11-06 11:12 ` ar-jan
2023-01-29 13:19 ` ar-jan [this message]
2023-04-30 1:53 ` github-actions
2023-04-30 11:31 ` ar-jan
2023-06-24 13:20 ` ar-jan
2023-06-24 16:53 ` [PR PATCH] [Updated] " sgn
2023-06-24 16:54 ` sgn
2023-07-25 2:38 ` classabbyamp
2023-07-25 2:38 ` classabbyamp
2023-07-25 2:59 ` qscintilla-qt5 update to 2.14.1, " classabbyamp
2023-07-25 8:01 ` ar-jan
2023-07-25 8:04 ` [PR PATCH] [Merged]: " classabbyamp
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=20230129131919.r9nqaaTxdYxFEztp7r43hPMPhw9Zxl0hworZW2UGapI@z \
--to=ar-jan@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).