public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Wileam Yonatan Phan <wileamyp@outlook.com>
To: Jonathan Wakely <jwakely.gcc@gmail.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 09:34:21 -0400	[thread overview]
Message-ID: <BY5PR14MB3911E24E418DDBC315A58EC3CEAB9@BY5PR14MB3911.namprd14.prod.outlook.com> (raw)
In-Reply-To: <CAH6eHdT=jSq-2zJ0gYqpXaVGNvuUF1Kvun4bWyodQ1PQN_d+hw@mail.gmail.com>

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, this script does exactly that, but the build
process is automated based on the build configuration file.

Thanks again,
Wil

On Mon, 2022-06-13 at 12:59 +0100, Jonathan Wakely wrote:
> On Mon, 13 Jun 2022 at 02:51, Wileam Yonatan Phan via Gcc
> <
> gcc@gcc.gnu.org
> > wrote:
> > Hi everyone,
> > 
> > This weekend marks the end of the community bonding period for GSoC '22,
> > and
> > here’s my progress so far with the GSoC project on Fortran DO CONCURRENT.
> > 
> > I've initialized a GCC mirror on GitHub where I plan to track all patches
> > that
> > I will create during the GSoC:
> > <
> > https://github.com/wyphan/gfortran-do-concurrent
> > >
> > 
> > I met with Tobias over a MS Teams call on May 30, 2022. Together, we picked
> > GCC
> > PR# 102003 as a good starter issue to start delving into the Fortran parser
> > in
> > GCC. He also guided me through how to debug the compiler using gdb. Tobias,
> > thanks a lot for spending some of your (technically) vacation time with me!
> > 
> > In the meantime, I’ve implemented a simple build script system for GCC that
> > I
> > christen "GCCprefab". Before this build system existed, there are only two
> > relatively easy ways to build GCC painlessly:
> > 
> > 1. Using Spack package manager: `spack install gcc'
> > 2. Using the install script for OpenCoarrays
> > <
> > https://github.com/sourceryinstitute/OpenCoarrays
> > >
> 
> I disagree there are "only two" ways.
> 
> https://gcc.gnu.org/wiki/InstallingGCC
>  describes an arguably much simpler way.
> 


  reply	other threads:[~2022-06-13 13:34 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 [this message]
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
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=BY5PR14MB3911E24E418DDBC315A58EC3CEAB9@BY5PR14MB3911.namprd14.prod.outlook.com \
    --to=wileamyp@outlook.com \
    --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).