From: Damian Rouson <damian@archaeologic.codes>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: Wileam Yonatan Phan <wileamyp@outlook.com>,
"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>,
"fortran@gcc.gnu.org List" <fortran@gcc.gnu.org>
Subject: Re: GSoC Blog Post 0 - GCCprefab build system
Date: Mon, 13 Jun 2022 17:37:22 -0700 [thread overview]
Message-ID: <CAHS2gMwXDUAgU8bQuVqFEwvUu6XvdfNbK=cSgEsLNWq+ptJs1Q@mail.gmail.com> (raw)
In-Reply-To: <CAH6eHdQ7tif+5-SaME5JC4ftaT5mLcMxvatj-_Bzoi91CZuXqg@mail.gmail.com>
On Mon, Jun 13, 2022 at 8:27 AM Jonathan Wakely via Fortran <
fortran@gcc.gnu.org> wrote:
>
> Yes, it does that, but takes 400 lines of shell script to do so.
>
> If you want "relatively easy ways to build GCC painlessly" then you
> can do it with nine lines of shell commands.
>
> Or in about 80, for any non-prehistoric version, with no config file
> needed (just a single option to the script, the release number or
> snapshot name to build):
>
> https://gist.github.com/jwakely/95b3a790157f55d75e18f577e12b50d7#file-build_gcc_versions-sh
Do the above 9 lines or 80 lines include the entire prerequisite software
stack or just the ones that the download_prerequisites script downloads?
If I recall correctly, building gfortran also requires flex and building
flex requires bison and building bison requires m4 and the
download_prerequisites script didn't download any of those the last time I
checked.
I realize that building gfortran from source comes very easily to GCC
developers, especially if they do it regularly. I've encountered a lot of
people who found it challenging, including myself initially, which was the
reason for incorporating the capability into the OpenCoarrays installer.
Damian
next prev parent reply other threads:[~2022-06-14 0:37 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 [this message]
2022-06-14 8:53 ` Jonathan Wakely
2022-06-14 11:16 ` Damian Rouson
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='CAHS2gMwXDUAgU8bQuVqFEwvUu6XvdfNbK=cSgEsLNWq+ptJs1Q@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).