Github messages for voidlinux
 help / color / mirror / Atom feed
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:17:12 +0100	[thread overview]
Message-ID: <20211231011712.rjTqpBSRfF6WYFz3ynCRXRjTkJbpWQWxqX0SjhpF6rU@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: 1674 bytes --]

New comment by Marie-Joseph on void-packages repository

https://github.com/void-linux/void-packages/issues/34752#issuecomment-1003231801

Comment:
> Can you not cross-compile from a more powerful x86_64 machine?

Yes, but only on a laptop that I have to beg and plead to charge. So some days I can, some days I can't. I'll make a follow-up comment with insights I've gained since today is one day I could. Spoiler alert: many things are broken with cross-compilation.

> Does more recent GCC require a D compiler to build gdc? That would make this proposal a no go because it would make bootstrap way more complicated.

Yes, as of (2021-12-29) HEAD it will require a D compiler. If by bootstrap you mean the (build) system bootstrap, I'd like to have a way to only build GDC when doing so explicitly. I'll look into that once I can compile it at all. Although Ada is built by default with the gcc package, and it requires an extant compiler. Assuming a glibc host, we could similarly download one like the gnat switch allows for Ada. If you mean bootstrapping GDC itself, both other D compilers require a D compiler, which is the source of this being such an issue to begin with. DMD only supports x86_64 and i686; LDC currently builds with DMD, therefore LDC can only be built for x86_64. More commentary on this in my next comment.

> if gdc from 11.x is self-hosting and cannot build without another D compiler, i'm absolutely opposed to enabling it
> (also, even in the version in 10.x, it does not support all targets void has)

Both of these points apply to both in-tree D compilers. Adding GDC will actually make D in general available on more platforms.

  parent reply	other threads:[~2021-12-31  1:17 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 [this message]
2021-12-31  1:31 ` Marie-Joseph
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=20211231011712.rjTqpBSRfF6WYFz3ynCRXRjTkJbpWQWxqX0SjhpF6rU@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).