From: ThatGeekyWeeb <ThatGeekyWeeb@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New Package: clex
Date: Wed, 22 Jul 2020 01:46:46 +0200 [thread overview]
Message-ID: <20200721234646.qt-TS2y2mF8hZk5iBgvHO5xscrpxe-qCrhFwh9fYiv4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23693@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 611 bytes --]
New comment by ThatGeekyWeeb on void-packages repository
https://github.com/void-linux/void-packages/pull/23693#issuecomment-662162410
Comment:
> Why is it restricted to these architectures? If there is no good reason, remove the line.
> I restricted it as it fails to pass the checks on arm based arches, due to
> ` CLEX requires a CURSES library with a wide character support`
> I am currently unsure which dependency I need to add to fix said error, I'll work on fixing that.
I can confirm that arm arches now build fine!
> `makedepends="ncurses-devel ncurses-libtinfo-devel"`
works!
next prev parent reply other threads:[~2020-07-21 23:46 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-21 18:51 [PR PATCH] " ThatGeekyWeeb
2020-07-21 19:12 ` [PR PATCH] [Updated] " ThatGeekyWeeb
2020-07-21 20:46 ` jnbr
2020-07-21 20:50 ` [PR PATCH] [Updated] " ThatGeekyWeeb
2020-07-21 20:56 ` [PR REVIEW] " jnbr
2020-07-21 20:56 ` jnbr
2020-07-21 20:56 ` jnbr
2020-07-21 20:56 ` jnbr
2020-07-21 20:56 ` jnbr
2020-07-21 20:56 ` jnbr
2020-07-21 21:23 ` ThatGeekyWeeb
2020-07-21 22:00 ` ThatGeekyWeeb
2020-07-21 22:04 ` ericonr
2020-07-21 22:05 ` ericonr
2020-07-21 22:13 ` ThatGeekyWeeb
2020-07-21 22:27 ` [PR PATCH] [Updated] " ThatGeekyWeeb
2020-07-21 22:42 ` [PR REVIEW] " ericonr
2020-07-21 23:01 ` [PR PATCH] [Updated] " ThatGeekyWeeb
2020-07-21 23:46 ` ThatGeekyWeeb [this message]
2022-04-18 2:11 ` github-actions
2022-05-02 2:15 ` [PR PATCH] [Closed]: " github-actions
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=20200721234646.qt-TS2y2mF8hZk5iBgvHO5xscrpxe-qCrhFwh9fYiv4@z \
--to=thatgeekyweeb@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).