Github messages for voidlinux
 help / color / mirror / Atom feed
From: leahneukirchen <leahneukirchen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: racket: re-enable cross-compilation
Date: Sun, 16 Jan 2022 15:37:00 +0100	[thread overview]
Message-ID: <20220116143700.ObsHQr2PQLqwppjT-H6WnOVh5YHwAQUT9aLBAMBMXHE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34853@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1360 bytes --]

There's a merged pull request on the void-packages repository

racket: re-enable cross-compilation
https://github.com/void-linux/void-packages/pull/34853

Description:
* remove nocross
* expound precise arch support (based on Racket's Chez Scheme support)
* remove unneeded musl deps
* put documentation behind a switch (builds fine, takes too long for CI)

#### Testing the changes
- I tested the changes in this PR: **YES**

#### Local build testing
- I built this PR locally for these architectures:
  - aarch64-musl - native and cross
  - x86_64-musl - native

### Notes
Racket's architecture support is limited only by Chez Scheme. The Chez Scheme it uses supports all the architectures we do except MIPS and PowerPC64. However, when trying to cross-compile for PowerPC 32-bit musl, I found that an absolute boat load of dependencies had to be compiled first. This would make CI take way too long, so I've simply omitted all PowerPC platforms. It wasn't supported before anyway, so this is still progress.

I don't actually know for sure that building documentation would cause this to time out. However, I didn't want to risk it (it does take a really long time, I just didn't time it), and this still makes local Racket documentation more accessible than it was before. (I use local documentation heavily, so this is important to me.)


      parent reply	other threads:[~2022-01-16 14:37 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-04 21:28 [PR PATCH] " Marie-Joseph
2022-01-05  9:37 ` Marie-Joseph
2022-01-06  8:03 ` [PR PATCH] [Updated] " Marie-Joseph
2022-01-06  8:05 ` Marie-Joseph
2022-01-06 12:05 ` Marie-Joseph
2022-01-06 12:26 ` ericonr
2022-01-09 16:38 ` leahneukirchen
2022-01-09 17:14 ` q66
2022-01-09 17:15 ` q66
2022-01-09 17:16 ` q66
2022-01-09 17:24 ` leahneukirchen
2022-01-09 17:40 ` q66
2022-01-09 17:45 ` q66
2022-01-09 18:02 ` leahneukirchen
2022-01-10 22:43 ` Marie-Joseph
2022-01-10 22:49 ` Marie-Joseph
2022-01-10 22:55 ` Marie-Joseph
2022-01-10 23:07 ` Marie-Joseph
2022-01-10 23:13 ` Marie-Joseph
2022-01-14  1:03 ` Marie-Joseph
2022-01-14  2:41 ` q66
2022-01-14  8:21 ` [PR PATCH] [Updated] " Marie-Joseph
2022-01-14  8:25 ` Marie-Joseph
2022-01-14 16:46 ` leahneukirchen
2022-01-15  6:53 ` Marie-Joseph
2022-01-15  6:56 ` Marie-Joseph
2022-01-16 14:37 ` leahneukirchen [this message]

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=20220116143700.ObsHQr2PQLqwppjT-H6WnOVh5YHwAQUT9aLBAMBMXHE@z \
    --to=leahneukirchen@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).