all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ashvith Shetty <ashvithshetty10@gmail.com>
To: Adam Faiz <adam.faiz@disroot.org>
Cc: 72494@debbugs.gnu.org
Subject: [bug#72494] [PATCH v4] gnu: Add c3c-bootstrap.
Date: Mon, 12 Aug 2024 18:38:42 +0000	[thread overview]
Message-ID: <CA+n6Bx9jcG3Enw=17wyze2cYbxhZN_YQVp4c0kwHjOJKRosYog@mail.gmail.com> (raw)
In-Reply-To: <8f0c2986-b790-86fa-7217-5491d6f7208f@disroot.org>

[-- Attachment #1: Type: text/plain, Size: 519 bytes --]

Hi Adam,
I've actually got my own patch ready with similar substitution and complete
set of tests, which I've not submitted yet. The reason for this is that
I've talked to the maintainer of the project, and according to them, this
substitution is a bad idea. Another reason is that it does not work in a
pure, ephemeral environment, unless `gcc` and `ld` is provided as either a
propagated input, or a side-by package. And there's also the issue with
using an alternative compiler and linker, which isn't working well.

[-- Attachment #2: Type: text/html, Size: 644 bytes --]

      reply	other threads:[~2024-08-12 18:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-06 11:02 [bug#72494] [PATCH 0/1] Add C3 Ashvith Shetty
2024-08-06 11:04 ` [bug#72494] [PATCH 1/1] gnu: Add C3 1.6.1 Ashvith Shetty
2024-08-06 15:07 ` [bug#72494] [PATCH 0/1] Add C3 Adam Faiz via Guix-patches via
2024-08-06 19:32 ` [bug#72494] [PATCH v1] gnu: Add C3 1.6.1 Ashvith Shetty
2024-08-06 19:37 ` [bug#72494] [PATCH v2] " Ashvith Shetty
2024-08-07  6:36 ` [bug#72494] [PATCH v3] gnu: Add c3c-bootstrap Adam Faiz via Guix-patches via
2024-08-10 17:59   ` Ashvith Shetty
2024-08-11 14:47     ` Adam Faiz via Guix-patches via
2024-08-11 14:57 ` [bug#72494] [PATCH v4] " Adam Faiz via Guix-patches via
2024-08-12 18:38   ` Ashvith Shetty [this message]

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='CA+n6Bx9jcG3Enw=17wyze2cYbxhZN_YQVp4c0kwHjOJKRosYog@mail.gmail.com' \
    --to=ashvithshetty10@gmail.com \
    --cc=72494@debbugs.gnu.org \
    --cc=adam.faiz@disroot.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. 
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.