From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 130693 invoked by alias); 20 Jul 2018 16:54:43 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 130679 invoked by uid 89); 20 Jul 2018 16:54:43 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-2.8 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=UD:comcast.net, comcastnet, comcast.net, Hx-spam-relays-external:ESMTPA X-HELO: resqmta-po-11v.sys.comcast.net Received: from resqmta-po-11v.sys.comcast.net (HELO resqmta-po-11v.sys.comcast.net) (96.114.154.170) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 20 Jul 2018 16:54:42 +0000 Received: from resomta-po-01v.sys.comcast.net ([96.114.154.225]) by resqmta-po-11v.sys.comcast.net with ESMTP id gWzEfdRv0og6NgYfwfLEfO; Fri, 20 Jul 2018 16:54:40 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20161114; t=1532105680; bh=XxNW3uqaptr99bcnBQuAPpoMAF7O7fHPcmqL5ZBek4o=; h=Received:Received:Content-Type:Mime-Version:Subject:From:Date: Message-Id:To; b=GUd75H7/PeD5aJB3SreWh1GDF6sYgI5HQixql/nSy3KYgn23GLdRy/d1h3MSoGZec 3Xmkh7dhdLhLQZ6fceGJijMN3G0fnYe6ywT9gKs7yd2kqa3dQKDywj2VyN2lCn00U6 JQOEFX1bTTuZzjv3698VEeAXiiFtIc+TEEm5kjPSTETQIf6BjdAxlOm/xt3lobC54L oc/hU6anQoJCChoPMj9UlXmxIevnflBlDQEwfdoyiz2fJkN+m/E2MrYYGyv5eT2/Yn I1A7NSIguUwkC7ivIr3VFEztCNQ+FjdanuMVHN3IvfHhYJ7sChznHiMwLtTifKyIwf fmFGwy+jAmlOg== Received: from [192.168.10.125] ([73.60.223.101]) by resomta-po-01v.sys.comcast.net with ESMTPA id gYfufp3iHVGSOgYfvfvLiB; Fri, 20 Jul 2018 16:54:40 +0000 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: [RFC] Adding Python as a possible language and it's usage From: Paul Koning In-Reply-To: <20180720163717.GD16221@gate.crashing.org> Date: Fri, 20 Jul 2018 17:12:00 -0000 Cc: =?utf-8?Q?Martin_Li=C5=A1ka?= , Matthias Klose , gcc@gcc.gnu.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <1531911391.18413.114.camel@redhat.com> <20180718120625.GA19628@thyrsus.com> <64f2d86d-3b46-3ede-4782-9f6d5c4fb704@ubuntu.com> <61fca135-fd19-05ab-0560-1718b0aa0d8a@suse.cz> <20180720163717.GD16221@gate.crashing.org> To: Segher Boessenkool X-SW-Source: 2018-07/txt/msg00301.txt.bz2 > On Jul 20, 2018, at 12:37 PM, Segher Boessenkool wrote: >=20 > On Fri, Jul 20, 2018 at 11:49:05AM +0200, Martin Li=C5=A1ka wrote: >> Fully agree with that. Coming up with a new scripts written in python2 r= eally >> makes no sense. >=20 > 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? Or is it allowed to require installing prere= quisites? Yes, some platforms are so far behind they still don't ship Pyth= on 3, but installing it is straightforward. paul