Github messages for voidlinux
 help / color / mirror / Atom feed
From: q66 <q66@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: package ldc for aarch64 (and more)
Date: Fri, 31 Dec 2021 03:25:14 +0100	[thread overview]
Message-ID: <20211231022514.pklT-4eZUV11z01Wo-5IycHrm7FcZLqLROPC1Ho_GAY@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: 1145 bytes --]

New comment by q66 on void-packages repository

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

Comment:
I am opposed to requiring a D compiler to bootstrap a system, and since gcc will now require a D compiler to enable gdc, there is no way you can get around that (you either need an existing D compiler, or download some kind of binary snapshot during the build, and both options are bad for bootstrapping a Void system)

The situation is already bad with Ada, and I don't want to add more of the same to it, except worse because unlike Ada, GDC does not cover all targets we cover

D is not an important enough language to warrant the extra burden, barely anything uses it, and you will be imposing this on the toolchain maintainers in the distro

If you want GDC, build it separately as its own template, use binary snapshots to bootstrap, but don't have it affect the system compiler

you can use the same strategy for bootstrapping ldc; cross-compile snapshot builds of ldc, make tarballs of them, upload them somewhere, then use them to bootstrap ldc (same thing is done for e.g. rust, go, ...)

  parent reply	other threads:[~2021-12-31  2:25 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
2021-12-31  2:23 ` q66
2021-12-31  2:25 ` q66 [this message]
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=20211231022514.pklT-4eZUV11z01Wo-5IycHrm7FcZLqLROPC1Ho_GAY@z \
    --to=q66@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).