public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Wileam Yonatan Phan <wileamyp@outlook.com>
Cc: "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 16:26:59 +0100	[thread overview]
Message-ID: <CAH6eHdQ7tif+5-SaME5JC4ftaT5mLcMxvatj-_Bzoi91CZuXqg@mail.gmail.com> (raw)
In-Reply-To: <BY5PR14MB3911E24E418DDBC315A58EC3CEAB9@BY5PR14MB3911.namprd14.prod.outlook.com>

On Mon, 13 Jun 2022 at 14:34, Wileam Yonatan Phan wrote:
>
> Hi Jonathan,
>
> Thanks for the feedback. Regarding the linked page <
> https://gcc.gnu.org/wiki/InstallingGCC>
> if you're referring to the part that tells you to use your distro's package
> manager, yes that's indeed the simplest way to install GCC, but from pre-built
> binaries, not building directly from sources. But if you're referring to the
> example at the bottom of the page,

Yes, that's what I mean.

> this script does exactly that, but the build
> process is automated based on the build configuration file.

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

My point is just that there are already easier ways to do it, not only
by using spack or the OpenCoarrays build script.

N.B. your https://github.com/wyphan/gccprefab/blob/main/gcc12.cfg
config file says "Latest GCC 12 Release" but actually builds from the
tip of the branch, not a release.

  reply	other threads:[~2022-06-13 15:27 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 [this message]
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
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=CAH6eHdQ7tif+5-SaME5JC4ftaT5mLcMxvatj-_Bzoi91CZuXqg@mail.gmail.com \
    --to=jwakely.gcc@gmail.com \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --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).