From: Marie-Joseph <Marie-Joseph@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: racket: re-enable cross-compilation
Date: Tue, 11 Jan 2022 00:07:31 +0100 [thread overview]
Message-ID: <20220110230731.9ljNqQWNw9GZRhWBzYhAlI2oIMtrPiApF_g0ThC4f5o@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: 574 bytes --]
New comment by Marie-Joseph on void-packages repository
https://github.com/void-linux/void-packages/pull/34853#issuecomment-1009434203
Comment:
I just noticed that in line 49, that `-m64` flag only gets by CI because cross builds use 64-bit hosts. That'll be changed to `-m${XBPS_WORDSIZE}`.
If anyone notices other things like that in the values passed to `env`, please let me know. I literally just copied the env passed to configure in the default build and changed the libraries and binaries to host versions (so instead of eg aarch64-musl-gcc it's just gcc, etc).
next prev parent reply other threads:[~2022-01-10 23:07 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 [this message]
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 ` [PR PATCH] [Merged]: " leahneukirchen
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=20220110230731.9ljNqQWNw9GZRhWBzYhAlI2oIMtrPiApF_g0ThC4f5o@z \
--to=marie-joseph@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).