From: mintsuki <mintsuki@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: limine-2.24
Date: Sat, 26 Jun 2021 16:06:00 +0200 [thread overview]
Message-ID: <20210626140600.ElzROLSsdWY05roGZxpy0ENJlKrAQf2lzzxJN_0muhY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31658@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1638 bytes --]
New comment by mintsuki on void-packages repository
https://github.com/void-linux/void-packages/pull/31658#issuecomment-869008021
Comment:
> Building a full gcc toolchain will end painfull. You can try to use add `cross-x86_64-linux-gnu` for `i686*` and `x86_64-musl` builds. (I initial forgot that we have it available on `i686` nowadays).
>
> So you can add this after checksum
>
> ```shell
> case "$XBPS_TARGET_MACHINE" in
> x86_64);;
> *) hostmakedepends+=" cross-x86_64-linux-gnu";;
> esac
> ```
>
> and this as do_build
>
> ```shell
> do_build() {
> if [ "$XBPS_TARGET_MACHINE" = "x86_64" ]; then
> make
> else
> CFLAGS="" make CROSS_COMPILE="x86_64-linux-gnu-" \
> CC="x86_64-linux-gnu-gcc" TOOLCHAIN="x86_64-linux-gnu" \
> CC_TOOLCHAIN="x86_64-linux-gnu-gcc"
> make bin/limine-install TOOLCHAIN="x86_64-linux-gnu"
> fi
> }
> ```
>
> The build system does all kinds of wonky assumptions, this should workaround most/all of them.
It needs a cross compiler on musl too, or alternatively an implementation of `stdint.h` that works. Using the provided cross compiler would be ideal.
The cross compiler *does* build, and if you check the CI, everything else builds fine too, except on `i686`, where I assume the build system passes `-mtune=i686` as part of the `CFLAGS` when it should not do that, as it will break stuff related to `gnu-efi`.
This can also easily be worked around by just unsetting the `CFLAGS` or stripping out the `-mtune` flag from them.
next prev parent reply other threads:[~2021-06-26 14:06 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-25 22:21 [PR PATCH] " mintsuki
2021-06-26 6:34 ` Anachron
2021-06-26 11:38 ` [PR PATCH] [Updated] " mintsuki
2021-06-26 11:51 ` mintsuki
2021-06-26 11:55 ` mintsuki
2021-06-26 11:55 ` [PR REVIEW] " Johnnynator
2021-06-26 11:55 ` Johnnynator
2021-06-26 11:57 ` mintsuki
2021-06-26 11:57 ` Johnnynator
2021-06-26 11:57 ` mintsuki
2021-06-26 11:58 ` [PR REVIEW] " Johnnynator
2021-06-26 12:00 ` [PR PATCH] [Updated] " mintsuki
2021-06-26 12:00 ` mintsuki
2021-06-26 12:04 ` [PR REVIEW] " mintsuki
2021-06-26 12:05 ` mintsuki
2021-06-26 12:21 ` mintsuki
2021-06-26 12:21 ` mintsuki
2021-06-26 12:23 ` [PR PATCH] [Updated] " mintsuki
2021-06-26 12:26 ` mintsuki
2021-06-26 12:28 ` mintsuki
2021-06-26 12:31 ` [PR PATCH] [Updated] " mintsuki
2021-06-26 12:34 ` mintsuki
2021-06-26 13:04 ` mintsuki
2021-06-26 13:12 ` [PR PATCH] [Updated] " mintsuki
2021-06-26 13:34 ` mintsuki
2021-06-26 13:44 ` [PR REVIEW] " Johnnynator
2021-06-26 13:44 ` Johnnynator
2021-06-26 13:59 ` mintsuki
2021-06-26 14:02 ` mintsuki
2021-06-26 14:03 ` mintsuki
2021-06-26 14:04 ` mintsuki
2021-06-26 14:05 ` mintsuki
2021-06-26 14:06 ` mintsuki [this message]
2021-06-26 14:11 ` [PR REVIEW] " Johnnynator
2021-06-26 14:11 ` Johnnynator
2021-06-26 14:16 ` Johnnynator
2021-06-26 15:02 ` [PR PATCH] [Updated] " mintsuki
2021-06-26 15:06 ` mintsuki
2021-06-26 15:10 ` mintsuki
2021-06-27 19:19 ` [PR REVIEW] " Johnnynator
2021-06-27 19:19 ` Johnnynator
2021-06-27 19:19 ` Johnnynator
2021-06-27 19:45 ` [PR PATCH] [Updated] " mintsuki
2021-06-27 19:49 ` mintsuki
2021-07-11 3:06 ` [PR PATCH] [Closed]: " mintsuki
2021-07-11 3:13 ` ericonr
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=20210626140600.ElzROLSsdWY05roGZxpy0ENJlKrAQf2lzzxJN_0muhY@z \
--to=mintsuki@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).