From: Marie-Joseph <Marie-Joseph@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: package ldc for aarch64 (and more)
Date: Fri, 31 Dec 2021 02:31:27 +0100 [thread overview]
Message-ID: <20211231013127.DUdcFDCy_ZPG3NjYATotbxYa7VtuAh4HC4oiUP8_hfg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34752@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1578 bytes --]
New comment by Marie-Joseph on void-packages repository
https://github.com/void-linux/void-packages/issues/34752#issuecomment-1003234652
Comment:
So I've managed to try some cross-compilation today, both of LDC and GDC.
For GDC compilation, I added a D build option. I had some trouble getting libisl downloaded. It seems the link in the current template stopped working sometime in the last couple days. I managed to find a different one that still works at https://libisl.sourceforge.io though. However, for some reason g++ gets passed the flag "-march=armv8-a" at some point, which is not a valid value for that flag. From what I can tell, that flag is only valid for x86* builds since valid options all seem to be code names or descriptors of various x86* architectures. Without digging into makefiles I don't think I can resolve that, so I moved on to trying to compile LDC with LDC.
The first problem with compiling LDC with LDC is that it requires the ldmd front-end. Void doesn't package the ldmd front-end. So I decided to try natively compiling it to get build artifacts to figure out how to package the ldmd front-end so I can do that and install it to use it to cross-build LDC with LDC. But unfortunately, it can't find a *bunch* of LLVM headers. Maybe because I'm using musl? In any case, resolving that particular issue seems even more time-consuming than getting GDC to compile.
So I'm going to take a break (I've been at this for the plurality of my waking hours since opening this issue) and when I come back I guess I'll be digging into makefiles.
next prev parent reply other threads:[~2021-12-31 1:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-29 6:09 [ISSUE] " Marie-Joseph
2021-12-30 19:59 ` sug0
2021-12-30 21:27 ` ericonr
2021-12-30 21:38 ` q66
2021-12-31 1:16 ` Marie-Joseph
2021-12-31 1:17 ` Marie-Joseph
2021-12-31 1:31 ` Marie-Joseph [this message]
2021-12-31 2:23 ` q66
2021-12-31 2:25 ` q66
2021-12-31 19:07 ` Marie-Joseph
2021-12-31 20:27 ` Marie-Joseph
2021-12-31 22:47 ` q66
2022-06-20 2:13 ` github-actions
2022-07-04 2:15 ` [ISSUE] [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=20211231013127.DUdcFDCy_ZPG3NjYATotbxYa7VtuAh4HC4oiUP8_hfg@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).