public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Eli Schwartz <eschwartz93@gmail.com>
To: Vincenzo Palazzo <vincenzopalazzodev@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 07:43:11 -0500	[thread overview]
Message-ID: <ec45876f-d023-43c4-9505-de05fc1e921a@gmail.com> (raw)
In-Reply-To: <CAKy8djTcQ2TgG75h_pWgyTOH6Ec0bA-kVeWe94J4h1BUHQmJmA@mail.gmail.com>

On 12/5/23 5:35 AM, Vincenzo Palazzo wrote:
>>> I see, but to me, this do not look like a distro build procedure,
>>> because you can use
>>> with any kind of system (OSX/UNIX) by using nix.
>>
>> But you can do the same with various other distro build procedures too?
>> e.g. Gentoo Prefix allows you to install a full-blown Gentoo anywhere
>> you like, "by using portage".
> 
> With a single difference on Gentoo you are allowed to put stuff in the
> global path and use
> it from a terminal like `$ pacman -Sy foo`. On nix os you do not,
> because the development environment
> is used for that.
> 
> So all the nice dependencies that gcc required to build can not be
> installed in NixOS global pat (e.g libc)
> so in NixOS you should define the development environment otherwise
> you can do the build. Instead in all
> the other systems that you mention you can do.


And yet, it seems your original point was that this doesn't qualify as a
"distro build procedure" because nix isn't specific to NixOS.

Are you backing down from that opinion and deciding that this proposal
is, indeed, after all specific to NixOS and only NixOS and is neither
needed nor used on any other distro?


> Please note that the flake.nix does not define how to build gcc, but
> just what are the dependencies
> that gcc is required in order to contribute to the compiler. In other
> words, is you run the flake.nix
> on NixOS or any other system you do not have gcc installed on your
> system, this is the job of the
> distro.


Its lack of completeness is surely an issue, but not the issue at hand
*here*. Why do you think the lack of completeness is a supporting
argument, rather than an opposing argument?


-- 
Eli Schwartz


  reply	other threads:[~2023-12-05 12:43 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
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 [this message]
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=ec45876f-d023-43c4-9505-de05fc1e921a@gmail.com \
    --to=eschwartz93@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=vincenzopalazzodev@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).