Path: csiph.com!weretis.net!feeder8.news.weretis.net!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod
From: Julian Gilbey <julian@d-and-j.net>
Newsgroups: linux.debian.maint.python
Subject: Re: Build and run-time triplets
Date: Thu, 09 Jun 2022 12:50:01 +0200
Message-ID: <EwnTH-3E7B-9@gated-at.bofh.it>
References: <EwbIR-3wrn-9@gated-at.bofh.it> <EwjQ5-3Bsn-7@gated-at.bofh.it> <Ewl5v-3Cb5-7@gated-at.bofh.it> <EwloR-3Cz8-5@gated-at.bofh.it> <EwmEh-3DkV-9@gated-at.bofh.it> <EwmXD-3Dvh-1@gated-at.bofh.it> <EwngZ-3DUN-9@gated-at.bofh.it>
X-Original-To: Andrey Rahmatullin <wrar@debian.org>
X-Mailbox-Line: From debian-python-request@lists.debian.org  Thu Jun  9 10:45:16 2022
Old-Return-Path: <julian@d-and-j.net>
X-Amavis-Spam-Status: No, score=-7.21 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, LDO_WHITELIST=-5, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
X-Policyd-Weight: using cached result; rate:hard: -4.6
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Mailing-List: <debian-python@lists.debian.org> archive/latest/20007
List-ID: <debian-python.lists.debian.org>
List-URL: <https://lists.debian.org/debian-python/>
List-Archive: https://lists.debian.org/msgid-search/YqHPLZ1f1+kMKvVa@d-and-j.net
Approved: robomod@news.nic.it
Lines: 23
Organization: linux.* mail to news gateway
Sender: robomod@news.nic.it
X-Original-Cc: debian-python@lists.debian.org
X-Original-Date: Thu, 9 Jun 2022 11:45:01 +0100
X-Original-Message-ID: <YqHPLZ1f1+kMKvVa@d-and-j.net>
X-Original-References: <YqEYHQLYKvGFmSAa@d-and-j.net> <YqGR3t+65uPJGTxk@belkar.wrar.name> <YqGkZDt/2GKkJV1l@d-and-j.net> <YqGpTXvqVuCglMqB@belkar.wrar.name> <YqG8tXr1bCHczVqd@momentum.pseudorandom.co.uk> <YqHApd5oSmYaJnd5@d-and-j.net> <YqHEuMMl5d+dB5SA@belkar.wrar.name>
Xref: csiph.com linux.debian.maint.python:14179

On Thu, Jun 09, 2022 at 03:00:24PM +0500, Andrey Rahmatullin wrote:
> > The build system here is the standard Python setup.py, except for this
> > library.  That is built by the following script:
> > 
> > ---
> > g++ -m64 -shared -o attach_linux_amd64.so -fPIC -nostartfiles attach.cpp
> > mv attach_linux_amd64.so ../attach_linux_amd64.so
> > echo Compiled amd64
> > ---
> > 
> > There's not even an attempt at working out ${libdir} or so on.
> Sure, it's not necessary to know the installation path at the compile and
> link time. It's only needed at the install time.

Ah, to clarify: this script compiles the library and sticks it into
the parent directory.  It is then installed with the rest of the
Python module via setup.py into /usr/lib/python3/dist-packages/...
So if I want to install it somewhere else, I will have to handle that
manually.

Best wishes,

   Julian