public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Damian Rouson <damian@archaeologic.codes>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: Wileam Yonatan Phan <wileamyp@outlook.com>,
	"fortran@gcc.gnu.org List" <fortran@gcc.gnu.org>,
	 "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: GSoC Blog Post 0 - GCCprefab build system
Date: Tue, 14 Jun 2022 04:16:16 -0700	[thread overview]
Message-ID: <CAHS2gMwO=bPep7-kgbaOZhAm8r2Oy0gdKD-yos24kiD2Ve0NwA@mail.gmail.com> (raw)
In-Reply-To: <CAH6eHdR0KEn=2fUQE678cOEKr6UgrkepJPst-KPVMy74LuU3kg@mail.gmail.com>

On Mon, Jun 13, 2022 at 8:27 AM Jonathan Wakely via Fortran <
fortran@gcc.gnu.org> wrote:

>
> It doesn't include them, but they are standard system packages that
> everybody can install without downloading the sources and building
> them from scratch.


unless the person is on a system on which they are not preinstalled and a
system for which the person doesn’t have the sudo privileges that package
managers often require.  What I’m describing is the norm for a lot of
government employees and even many people at private corporations with
strict security policies.  For what it’s worth, I’ve been assisting someone
who contacted me with this very issue over the past few days.  Building the
entire stack from source is the least painful option for this person.

You still need to have the other prerequisites listed at
> https://gcc.gnu.org/install/prerequisites.html


That is a long and daunting list for a newcomer.  I’ve listened to gfortran
developers describe building gfortran as “easy” for more than a decade
now.  Simply
saying it’s easy doesn’t make it so. I don’t know that I’ve ever met
someone who described the process as easy unless that person was a gfortran
developer.

Damian

<https://gcc.gnu.org/install/prerequisites.html>
>

  reply	other threads:[~2022-06-14 11:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-13  1:50 Wileam Yonatan Phan
2022-06-13 11:59 ` Jonathan Wakely
2022-06-13 13:34   ` Wileam Yonatan Phan
2022-06-13 15:26     ` Jonathan Wakely
2022-06-13 17:12       ` Wileam Yonatan Phan
2022-06-13 17:38         ` Jonathan Wakely
2022-06-14  0:37       ` Damian Rouson
2022-06-14  8:53         ` Jonathan Wakely
2022-06-14 11:16           ` Damian Rouson [this message]
2022-06-14 13:52             ` Wileam Yonatan Phan
2022-06-17 18:45       ` Bernhard Reutner-Fischer
2022-06-17 19:55         ` Jakub Jelinek
2022-06-18 19:24           ` Bernhard Reutner-Fischer
2022-06-17 20:07         ` Jonathan Wakely

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='CAHS2gMwO=bPep7-kgbaOZhAm8r2Oy0gdKD-yos24kiD2Ve0NwA@mail.gmail.com' \
    --to=damian@archaeologic.codes \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=jwakely.gcc@gmail.com \
    --cc=wileamyp@outlook.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).