From: Vincenzo Palazzo <vincenzopalazzodev@gmail.com>
To: Jeff Law <jeffreyalaw@gmail.com>
Cc: Andrew Pinski <pinskia@gmail.com>, gcc-patches@gcc.gnu.org
Subject: Re: [RFC PATCH 1/1] nix: add a simple flake nix shell
Date: Tue, 5 Dec 2023 02:38:13 +0100 [thread overview]
Message-ID: <CAKy8djQDdKFfKB2QU04iDeqb18hGyQ-o00jATaAxjdnGQuhDFg@mail.gmail.com> (raw)
In-Reply-To: <a6fd4532-271f-481b-a8c0-3d7b4ca67a38@gmail.com>
Ciao all,
>+1. I think this is best left to the distros.
What do you mean? this is not a package, it is an env shell in order
to build an work on GCC on NixOS.
NixOS has already the packages for GCC
Cheers,
Vincent.
On Tue, Dec 5, 2023 at 2:07 AM Jeff Law <jeffreyalaw@gmail.com> wrote:
>
>
>
> On 12/4/23 18:02, Andrew Pinski wrote:
> > On Mon, Dec 4, 2023 at 4:58 PM Vincenzo Palazzo
> > <vincenzopalazzodev@gmail.com> wrote:
> >>
> >> This commit is specifically targeting enhancements in
> >> Nix support for GCC development. This initiative stems
> >> from the recognized need within our community for a more
> >> streamlined and efficient development process when using Nix.
> >
> > I think this is wrong place for this.
> +1. I think this is best left to the distros.
>
> jeff
next prev parent reply other threads:[~2023-12-05 1:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-05 0:55 Vincenzo Palazzo
2023-12-05 1:02 ` Andrew Pinski
2023-12-05 1:07 ` Jeff Law
2023-12-05 1:38 ` Vincenzo Palazzo [this message]
2023-12-05 1:54 ` Jeff Law
2023-12-05 2:01 ` Vincenzo Palazzo
2023-12-05 2:02 ` Vincenzo Palazzo
2023-12-05 4:25 ` Eli Schwartz
2023-12-05 8:59 ` Richard Biener
2023-12-05 10:35 ` Vincenzo Palazzo
2023-12-05 12:43 ` Eli Schwartz
2023-12-11 16:10 ` Vincenzo Palazzo
2024-01-31 21:43 Vincenzo Palazzo
2024-01-31 22:19 ` Eli Schwartz
2024-02-01 21:04 ` Vincenzo Palazzo
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=CAKy8djQDdKFfKB2QU04iDeqb18hGyQ-o00jATaAxjdnGQuhDFg@mail.gmail.com \
--to=vincenzopalazzodev@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=pinskia@gmail.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).