From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: New package: j-807
Date: Sat, 28 Sep 2019 11:04:13 +0200 [thread overview]
Message-ID: <20190928090413.IPLVrqhpQTkiqYh_zrzogUrFTDMAt0b-C-XEHEVBQ20@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-14758@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1642 bytes --]
New comment by xelxebar on void-packages repository
https://github.com/void-linux/void-packages/pull/14758#issuecomment-536168266
Comment:
@Chocimier
Thanks for replying.
1. Excellent.
2. Fair enough. If there is no need to distinguish versions, then I guess it makes sense to remove the `${version}` directory from the install paths.
3. Hrm. Not sure I follow. The issue is that upstream supports *both* AVX and non-AVX architectures; however, the crossbuilds are not fine-grained enough to distinguish between those targets. Unless I am mistaken, this means we are forced to detect AVX support at install time.
Unfortunately, upstream seems to be using `fts.h` which musl explicitly chooses to not support. The [musl FAQ][0] gives a rationale and implies that the only way to support musl is by completely removing said libc calls.
In general, upstream seems to be interested in supporting a variety of build targets. The build system, however, implicitly assumes that the build host and target are the same, and it is doing some dirty things as well, like parsing CC to set different compile flags for gcc. This all makes cross-compilation break horribly, of course. I spent a long time munging patches to try and get things working, but I honestly don't really know what I'm doing.
6. One more question. Upstream has a collection of scripts they call 'addons'. These aren't tarred up at all, and require a separate, somewhat non-obvious installation from git. However, the J documentation acts as if these addons are installed by default. Any ideas on how to handle this?
[0]:https://wiki.musl-libc.org/faq.html
next prev parent reply other threads:[~2019-09-28 9:04 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-27 8:46 [PR PATCH] " voidlinux-github
2019-09-27 9:11 ` voidlinux-github
2019-09-27 9:17 ` [PR PATCH] [Updated] " voidlinux-github
2019-09-27 9:17 ` voidlinux-github
2019-09-27 9:18 ` voidlinux-github
2019-09-27 9:27 ` [PR PATCH] [Updated] " voidlinux-github
2019-09-27 9:27 ` voidlinux-github
2019-09-27 10:16 ` voidlinux-github
2019-09-27 10:16 ` voidlinux-github
2019-09-27 16:23 ` voidlinux-github
2019-09-27 16:59 ` voidlinux-github
2019-09-28 9:04 ` voidlinux-github [this message]
2019-09-28 14:40 ` voidlinux-github
2019-09-29 3:09 ` voidlinux-github
2019-09-29 3:10 ` voidlinux-github
2019-09-29 3:10 ` voidlinux-github
2019-09-29 3:52 ` voidlinux-github
2019-09-30 1:34 ` [PR PATCH] [Updated] " voidlinux-github
2019-09-30 1:34 ` voidlinux-github
2019-09-30 1:45 ` voidlinux-github
2019-09-30 3:30 ` [PR PATCH] [Updated] " voidlinux-github
2019-09-30 3:30 ` voidlinux-github
2019-09-30 9:07 ` voidlinux-github
2019-09-30 12:27 ` [PR PATCH] [Updated] " voidlinux-github
2019-09-30 12:27 ` voidlinux-github
2019-09-30 12:28 ` voidlinux-github
2019-09-30 15:07 ` voidlinux-github
2019-10-01 7:44 ` voidlinux-github
2019-10-01 16:20 ` voidlinux-github
2019-10-02 0:10 ` voidlinux-github
2019-10-02 22:01 ` voidlinux-github
2019-10-12 19:32 ` voidlinux-github
2019-10-23 6:43 ` voidlinux-github
2019-10-26 16:40 ` [PR PATCH] [Merged]: " voidlinux-github
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=20190928090413.IPLVrqhpQTkiqYh_zrzogUrFTDMAt0b-C-XEHEVBQ20@z \
--to=voidlinux-github@inbox.vuxu.org \
--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).