From: chloris-pale-green <chloris-pale-green@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: jruby-9.3.7.0
Date: Thu, 25 Aug 2022 18:10:23 +0200 [thread overview]
Message-ID: <20220825161023.QLZy7xoFKW_-YVP5OijEkmsPtTRCB-NO6l0_OU05J1U@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38900@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 597 bytes --]
New comment by chloris-pale-green on void-packages repository
https://github.com/void-linux/void-packages/pull/38900#issuecomment-1227479679
Comment:
> oh you didn't need to go through the trouble of making a whole VM, you can just [add another masterdir](https://github.com/void-linux/void-packages#building-for-musl)
Thank you for the tip. 😊 At first, I went with the method I knew well, but now I've tired the masterdir approach to test x86_64-musl build check error. I have no idea what the error means and I can build the package successfully in x86_64-musl masterdir on my machine.
next prev parent reply other threads:[~2022-08-25 16:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-25 6:47 [PR PATCH] " chloris-pale-green
2022-08-25 7:01 ` [PR PATCH] [Updated] " chloris-pale-green
2022-08-25 7:11 ` chloris-pale-green
2022-08-25 7:48 ` chloris-pale-green
2022-08-25 8:32 ` classabbyamp
2022-08-25 14:04 ` [PR PATCH] [Updated] " chloris-pale-green
2022-08-25 14:18 ` chloris-pale-green
2022-08-25 15:01 ` classabbyamp
2022-08-25 16:10 ` chloris-pale-green [this message]
2022-08-25 16:10 ` chloris-pale-green
2022-08-31 15:29 ` chloris-pale-green
2022-08-31 16:06 ` chloris-pale-green
2022-08-31 16:25 ` classabbyamp
2022-08-31 16:57 ` [PR PATCH] [Updated] " chloris-pale-green
2022-08-31 17:02 ` chloris-pale-green
2022-09-14 10:06 ` [PR PATCH] [Updated] " chloris-pale-green
2022-09-14 10:10 ` chloris-pale-green
2022-12-15 2:02 ` New package: jruby-9.3.8.0 github-actions
2022-12-30 1:58 ` [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=20220825161023.QLZy7xoFKW_-YVP5OijEkmsPtTRCB-NO6l0_OU05J1U@z \
--to=chloris-pale-green@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).