From: Elliott Mitchell <ehem+xen@m5p.com>
To: Marek Marczykowski-G??recki <marmarek@invisiblethingslab.com>
Cc: Wei Liu <wl@xen.org>,
xen-devel@lists.xenproject.org, Ian Jackson <iwj@xenproject.org>
Subject: Re: [SECOND RESEND] [PATCH] tools/python: Pass linker to Python build process
Date: Wed, 14 Oct 2020 21:03:39 -0700 [thread overview]
Message-ID: <20201015040339.GB5803@mattapan.m5p.com> (raw)
In-Reply-To: <20201015010259.GR151766@mail-itl>
On Thu, Oct 15, 2020 at 03:02:59AM +0200, Marek Marczykowski-G??recki wrote:
> On Tue, Oct 13, 2020 at 01:26:06PM +0000, Wei Liu wrote:
> > On Sun, Oct 11, 2020 at 06:11:39PM -0700, Elliott Mitchell wrote:
> > > Having looked around a bit, I believe this is a Python 2/3 compatibility
> > > issue. "distutils" for Python 2 likely lacked a separate $LDSHARED or
> > > $LD variable, whereas Python 3 does have this. Alas this is pointless
> > > due to the above (unless you can cause distutils.py to do the final link
> > > step separately).
> >
> > I think this is well-reasoned but I don't have time to figure out and
> > verify the details.
>
> Yes, it looks like distutils in Python 2 was even more limited than
> the one in Python 3.
Actually feels like two steps forward, one step back. Separate
$LDSHARED, yet $CFLAGS is appended to $LDFLAGS during invocation.
Architecture name is included the output Python extension filename, yet
the only way to override requires writing Python code. I've got ideas
to workaround this, but they're rather gross.
--
(\___(\___(\______ --=> 8-) EHM <=-- ______/)___/)___/)
\BS ( | ehem+sigmsg@m5p.com PGP 87145445 | ) /
\_CS\ | _____ -O #include <stddisclaimer.h> O- _____ | / _/
8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445
next prev parent reply other threads:[~2020-10-15 4:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-12 1:11 [SECOND RESEND] [PATCH] tools/python: Pass linker to Python build process Elliott Mitchell
2020-10-13 13:26 ` Wei Liu
2020-10-15 1:02 ` Marek Marczykowski-Górecki
2020-10-15 4:03 ` Elliott Mitchell [this message]
2020-10-15 1:01 ` Marek Marczykowski-Górecki
2020-10-16 13:25 ` Wei Liu
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=20201015040339.GB5803@mattapan.m5p.com \
--to=ehem+xen@m5p.com \
--cc=iwj@xenproject.org \
--cc=marmarek@invisiblethingslab.com \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.org \
/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 NNTP newsgroup(s).