From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 49219 invoked by alias); 20 Jul 2018 10:07:06 -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 49210 invoked by uid 89); 20 Jul 2018 10:07:05 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_PASS autolearn=ham version=3.3.2 spammy=boriscodesynthesiscom, U*boris, Boris, sk:boris@c X-HELO: mx1.suse.de Received: from mx2.suse.de (HELO mx1.suse.de) (195.135.220.15) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 20 Jul 2018 10:07:04 +0000 Received: from relay1.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 30101AD09; Fri, 20 Jul 2018 10:07:02 +0000 (UTC) Subject: Re: [RFC] Adding Python as a possible language and it's usage To: Matthias Klose , gcc@gcc.gnu.org References: <520C9D38-57F0-47BB-9701-5C6E1611F001@comcast.net> <5F57D904-E6F7-410F-B83D-F0BFFB92C888@comcast.net> From: =?UTF-8?Q?Martin_Li=c5=a1ka?= Message-ID: <034512e0-a9a8-36d5-be9c-6230ea65a486@suse.cz> Date: Fri, 20 Jul 2018 11:04:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2018-07/txt/msg00295.txt.bz2 On 07/18/2018 08:03 PM, Matthias Klose wrote: > On 18.07.2018 19:29, Paul Koning wrote: >> >> >>> On Jul 18, 2018, at 1:22 PM, Boris Kolpackov wrote: >>> >>> Paul Koning writes: >>> >>>>> On Jul 18, 2018, at 11:13 AM, Boris Kolpackov wrote: >>>>> >>>>> I wonder what will be the expected way to obtain a suitable version of >>>>> Python if one is not available on the build machine? With awk I can >>>>> build it from source pretty much anywhere. Is building newer versions >>>>> of Python on older targets a similarly straightforward process (somehow >>>>> I doubt it)? What about Windows? >>>> >>>> It's the same sort of thing: untar the sources, configure, make, make >>>> install. > > Windows binaries and MacOSX binaries are available from upstream. The build > process on *ix targets is autoconf based and easy as for awk/gawk. > >>> Will this also install all the Python packages one might plausible want >>> to use in GCC? > > some extension modules depend on external libraries, but even if those don't > exist, the build succeeds without building these extension modules. The sources > come with embedded libs for zlib, libmpdec, libexpat. They don't include > libffi (only in 3.7), libsqlite, libgdbm, libbluetooth, libdb. I suppose the > usage of such modules should be banned by policy. The only needed thing is any > of libdb (Berkley/SleepyCat) or gdbm to build the anydbm module which might be > necessary. > >> It installs the entire standard Python library (corresponding to the 1800+ pages of the library manual). I expect that will easily cover anything GCC might want to do. > > The current usage of awk and perl doesn't include any third party libraries. > That's where the usage of Python should start with. Thank you Matthias for explanation of dependencies problematics. I can confirm that option handling scripts can easily work without any fancy modules. Martin > > Matthias >