Re: [RFC] Adding Python as a possible language and it's usage

public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed

From: Segher Boessenkool <segher@kernel.crashing.org>
To: Paul Koning <paulkoning@comcast.net>
Cc: "Martin Liška" <mliska@suse.cz>,
	"Matthias Klose" <doko@ubuntu.com>,
	gcc@gcc.gnu.org
Subject: Re: [RFC] Adding Python as a possible language and it's usage
Date: Fri, 20 Jul 2018 17:59:00 -0000	[thread overview]
Message-ID: <20180720171108.GE16221@gate.crashing.org> (raw)
In-Reply-To: <CB08CB6B-AF03-4B4B-A2EB-540FBB1C8B99@comcast.net>

On Fri, Jul 20, 2018 at 12:54:36PM -0400, Paul Koning wrote:
> 
> 
> > On Jul 20, 2018, at 12:37 PM, Segher Boessenkool <segher@kernel.crashing.org> wrote:
> > 
> > On Fri, Jul 20, 2018 at 11:49:05AM +0200, Martin LiÅ¡ka wrote:
> >> Fully agree with that. Coming up with a new scripts written in python2 really
> >> makes no sense.
> > 
> > Then python cannot be a build requirement for GCC, since some of our
> > primary targets do not ship python3.
> 
> Is it required that GCC must build with only the stock support elements on the primary target platforms?

Not that I know.  But why should we make it hugely harder for essentially
no benefit?

All the arguments against awk were arguments against *the current scripts*.

And yes, we can (and perhaps should) rewrite those build scripts as C code,
just like all the other gen* we have.

> Or is it allowed to require installing prerequisites?  Yes, some platforms are so far behind they still don't ship Python 3, but installing it is straightforward.

Installing it is not straightforward at all.


Segher

next prev parent reply	other threads:[~2018-07-20 17:12 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-17 12:49 Martin Liška
2018-07-18  1:01 ` David Malcolm
2018-07-19 20:24   ` Karsten Merker
2018-07-20 10:02     ` Matthias Klose
2018-07-20 10:07     ` Martin Liška
2018-07-18  9:51 ` Richard Biener
2018-07-18 10:03   ` Richard Earnshaw (lists)
2018-07-18 10:56   ` David Malcolm
2018-07-18 11:08     ` Jakub Jelinek
2018-07-18 11:31     ` Jonathan Wakely
2018-07-18 12:06       ` Eric S. Raymond
2018-07-18 12:15         ` Jonathan Wakely
2018-07-18 12:50           ` Joel Sherrill
2018-07-18 14:29             ` Matthias Klose
2018-07-18 14:46               ` Janne Blomqvist
2018-07-20 10:01               ` Martin Liška
2018-07-20 16:54                 ` Segher Boessenkool
2018-07-20 17:12                   ` Paul Koning
2018-07-20 17:59                     ` Segher Boessenkool [this message]
2018-07-20 18:59                       ` Konovalov, Vadim
2018-07-20 20:09                         ` Matthias Klose
2018-07-20 20:15                           ` Konovalov, Vadim
2018-07-18 21:28           ` Eric S. Raymond
2018-07-23 14:31     ` Joseph Myers
2018-07-18 22:42   ` Segher Boessenkool
2018-07-19 12:28     ` Florian Weimer
2018-07-19 20:08       ` Richard Earnshaw (lists)
2018-07-20  9:49         ` Michael Clark
2018-07-19 15:56     ` Jeff Law
2018-07-19 16:12       ` Eric Gallager
2018-07-20 10:05       ` Martin Liška
2018-07-18 15:13 ` Boris Kolpackov
2018-07-18 16:56   ` Paul Koning
2018-07-18 17:29     ` Boris Kolpackov
2018-07-18 17:44       ` Paul Koning
2018-07-18 18:11         ` Matthias Klose
2018-07-20 11:04           ` Martin Liška
2018-07-19 14:47     ` Konovalov, Vadim
2018-07-23 14:21 ` Joseph Myers
2018-07-27 14:31 ` Michael Matz
2018-07-27 14:38   ` Michael Matz
2018-07-28  3:01     ` Matthias Klose
2018-07-27 14:54   ` Joseph Myers
2018-07-27 15:11     ` Michael Matz
2018-07-28  0:26       ` Paul Smith
2018-07-30 14:34         ` Joseph Myers
2018-07-28 12:11     ` Ramana Radhakrishnan
2018-07-28 17:23       ` David Malcolm
2018-07-30 14:51       ` Joseph Myers
2018-07-30 16:29         ` Andreas Schwab
2018-07-28  2:29 ` konsolebox
     [not found] <1531832440.64499.ezmlm@gcc.gnu.org>
2018-07-17 17:13 ` Basile Starynkevitch
2018-07-17 23:52   ` David Malcolm
2018-07-17 20:37 David Niklas
2018-07-18  0:23 ` David Malcolm
2018-07-18  0:38   ` Paul Koning
2018-07-18 16:41   ` doark
2018-07-18 17:22     ` doark

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=20180720171108.GE16221@gate.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=doko@ubuntu.com \
    --cc=gcc@gcc.gnu.org \
    --cc=mliska@suse.cz \
    --cc=paulkoning@comcast.net \
    /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).