From: Wileam Yonatan Phan <wileamyp@outlook.com>
To: Damian Rouson <damian@archaeologic.codes>,
Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: "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 09:52:41 -0400 [thread overview]
Message-ID: <BY5PR14MB3911D64C5BB016D1CF095DA4CEAA9@BY5PR14MB3911.namprd14.prod.outlook.com> (raw)
In-Reply-To: <CAHS2gMwO=bPep7-kgbaOZhAm8r2Oy0gdKD-yos24kiD2Ve0NwA@mail.gmail.com>
Hi Jonathan,
I just pushed a commit to update the build script and config files to use the
release tags instead of the tip of the branch. Thanks again for pointing this
out!
Thanks,
Wil
---
Hi Damian,
That's indeed a tricky issue to implement with the build script if the user
doesn't have sudo rights to install software on the system using the package
manager. Maybe I can make the script download the tarballs and build them from
sources.
Full disclosure: the script currently assumes all prerequisites have been
successfully installed, but based on the discussion here, I can add several
lines to check for their existence using `command -v`.
I'll start working on this later tonight.
Thanks,
Wil
On Tue, 2022-06-14 at 04:16 -0700, Damian Rouson wrote:
> 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
>
>
>
next prev parent reply other threads:[~2022-06-14 13:52 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
2022-06-14 13:52 ` Wileam Yonatan Phan [this message]
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=BY5PR14MB3911D64C5BB016D1CF095DA4CEAA9@BY5PR14MB3911.namprd14.prod.outlook.com \
--to=wileamyp@outlook.com \
--cc=damian@archaeologic.codes \
--cc=fortran@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=jwakely.gcc@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).