From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 79538 invoked by alias); 19 Feb 2020 15:53:55 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 79530 invoked by uid 89); 19 Feb 2020 15:53:55 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-11.4 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.1 spammy=adhere, bunt, organisation, distributing X-HELO: mail-wr1-f67.google.com Received: from mail-wr1-f67.google.com (HELO mail-wr1-f67.google.com) (209.85.221.67) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 19 Feb 2020 15:53:53 +0000 Received: by mail-wr1-f67.google.com with SMTP id k11so1105600wrd.9 for ; Wed, 19 Feb 2020 07:53:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=embecosm.com; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=kqusMmZsw5qOXJh9HjqpRTSbWcF++m3hGZSOX/mXCPE=; b=ULgBDijh6j/Jum9/FPDemuYiRdZDW2gEQNQko1weRIf6CfMakjD5uy9meHl1FbPvHk PGr09sF4SUkO8KnCeb5cKBjq0asV7A3GjxnXl68PqUlxZXlGTnsxtCJ0B1tIFZCvIu10 cJKT6/cb5wSN0r0f8T8JxPt48vYpF/fngG0DRKHErhbgdeJb2Tuqzc4ahVfVqJ0Mplqm O1Y6On1F7XbroTZXZb8YgD6jr6WgOXIz0Jt+ft0b9/RsAiA3s+k8iVIJ7fDlGo2ileYd RkfqZNL4GJxy9OoFjCb7pYF2UM610U6/TPQ4YVPM2/hfs97bsd4zkcQ2QEEUVA4Pzoy7 xHUQ== Return-Path: Received: from localhost (host86-186-80-160.range86-186.btcentralplus.com. [86.186.80.160]) by smtp.gmail.com with ESMTPSA id s139sm294848wme.35.2020.02.19.07.53.50 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Wed, 19 Feb 2020 07:53:50 -0800 (PST) Date: Wed, 19 Feb 2020 15:53:00 -0000 From: Andrew Burgess To: Eli Zaretskii Cc: gdb-patches@sourceware.org, richard.bunt@arm.com Subject: Re: [PATCH] gdb: Allow more control over where to find python libraries Message-ID: <20200219155350.GC3317@embecosm.com> References: <20200206164617.7461-1-andrew.burgess@embecosm.com> <83lfpfftz8.fsf@gnu.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <83lfpfftz8.fsf@gnu.org> X-Fortune: You've been Berkeley'ed! X-Editor: GNU Emacs [ http://www.gnu.org/software/emacs ] User-Agent: Mutt/1.9.2 (2017-12-15) X-IsSubscribed: yes X-SW-Source: 2020-02/txt/msg00782.txt.bz2 * Eli Zaretskii [2020-02-06 20:31:23 +0200]: > > From: Andrew Burgess > > Cc: Richard Bunt , Andrew Burgess > > Date: Thu, 6 Feb 2020 16:46:17 +0000 > > > > The motivation behind this commit is to make it easier to bundle the > > Python libraries with GDB when linking GDB against a static > > libpython, the Python libraries will be manually added into the GDB > > installation tree, and GDB should be able to find them at run-time. > > The installation tree will look like this: > > > > . > > |-- bin/ > > |-- include/ > > |-- lib/ > > | `-- python3.8/ > > `-- share/ > > > > The benefit here is that the entire installation tree can be bundled > > into a single archive and copied to another machine with a different > > version of Python installed, and GDB will still work, including its > > Python support. > > This assumes that the Python libraries and support files are part of > the GDB distribution, right? But if those are distributed with GDB, > so should be their sources, to adhere to the license, no? Hi Eli, As Simon mentioned I don't think that I described my intentions very well. The intended use case for this situation is building the Python interpreter statically into GDB, and then placing Python's *.py files into a directory relative to the built GDB executable, and have GDB manage to find them. The use for this would be that at XXX organisation I can build a version of GDB, package it up into a tar-file and copy this onto several different machines, which might be running different OS versions. In this situation I don't think there's any licensing issue as the builds of GDB are not going outside the XXX organisation. If I did decide to distribute the pre-built GDB tar-files outside of XXX, then the source for GDB, and the source for Python would be made available also from XXX, but I didn't believe simply distributing two pre-built things in one package means I have to upstream merge the two projects - have I miss-understood? Thanks, Andrew