From: sirkhancision <sirkhancision@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: bash-language-server-4.8.3
Date: Fri, 17 Mar 2023 23:30:09 +0100 [thread overview]
Message-ID: <20230317223009.fN0PyUv0XU9wlg_5cKoOcvH7rBKtz0iygvP03GCHBOI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42818@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 418 bytes --]
New comment by sirkhancision on void-packages repository
https://github.com/void-linux/void-packages/pull/42818#issuecomment-1474468393
Comment:
> how did you build this for x86_64-musl when `archs="i686 x86_64"`?
My bad, I had built it before restricting the architectures, and I thought x86_64 meant both glibc and musl. It's corrected now, and limiting i686 to glibc, as building it in i686-musl fails for me.
next prev parent reply other threads:[~2023-03-17 22:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-17 7:31 [PR PATCH] " sirkhancision
2023-03-17 15:04 ` sirkhancision
2023-03-17 19:41 ` icp1994
2023-03-17 21:59 ` classabbyamp
2023-03-17 22:28 ` [PR PATCH] [Updated] " sirkhancision
2023-03-17 22:29 ` classabbyamp
2023-03-17 22:29 ` [PR REVIEW] " classabbyamp
2023-03-17 22:29 ` classabbyamp
2023-03-17 22:29 ` sirkhancision
2023-03-17 22:30 ` sirkhancision [this message]
2023-03-17 22:31 ` classabbyamp
2023-03-17 22:36 ` [PR REVIEW] " sirkhancision
2023-03-17 22:37 ` classabbyamp
2023-03-17 22:42 ` sirkhancision
2023-03-17 22:43 ` classabbyamp
2023-03-17 22:44 ` sirkhancision
2023-03-17 22:47 ` classabbyamp
2023-03-17 23:10 ` [PR PATCH] [Updated] " sirkhancision
2023-03-17 23:11 ` sirkhancision
2023-05-09 4:37 ` tjkirch
2023-05-09 18:22 ` [PR PATCH] [Updated] " sirkhancision
2023-05-10 14:46 ` [PR PATCH] [Merged]: New package: bash-language-server-4.9.1 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=20230317223009.fN0PyUv0XU9wlg_5cKoOcvH7rBKtz0iygvP03GCHBOI@z \
--to=sirkhancision@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).