From: Tom Tromey <tom@tromey.com>
To: Aditya Vidyadhar Kamath <akamath996@gmail.com>
Cc: ulrich.weigand@de.ibm.com, simon.marchi@polymtl.ca,
tom@tromey.com, gdb-patches@sourceware.org,
Aditya.Kamath1@ibm.com, sangamesh.swamy@in.ibm.com,
PRAJWAL.B.MEHENDARKAR@ibm.com
Subject: Re: [PATCH v1] Fix wrong build tree in python.exp path on AIX
Date: Fri, 21 Aug 2026 09:43:29 -0600 [thread overview]
Message-ID: <874ignscm6.fsf@tromey.com> (raw)
In-Reply-To: <20260730054826.89712-2-akamath996@gmail.com> (Aditya Vidyadhar Kamath's message of "Thu, 30 Jul 2026 11:18:27 +0530")
>>>>> Aditya Vidyadhar Kamath <akamath996@gmail.com> writes:
> From: Aditya Kamath <Aditya.Kamath1@ibm.com>
> Python records the path to the export file in LINKFORSHARED sysconfig
> variable as a build tree relative path: -Wl,bE:Modules/python.exp
> But this will fail in AIX. When configure runs python-config.py --ldflags to test for
> libpython, the linker cannot find Modules/python.exp, the link test
> fails, and GDB is built without Python support.
> So in this patch we fix the same by replacing the relative path with LIBPL/python.exp (e.g.
> /opt/freeware/lib64/python3.12/config-3.12/python.exp) on AIX only,
> where LIBPL is the installed config directory that already contains
> the file.
Thanks for the patch.
I don't really understand this, but (1) I didn't see any other
commentary on it and (2) it seems to be AIX-specific.
So, I think it is ok. I appreciate the comment in there.
It's fine if you want to apply this to the gdb-18 branch as well.
Approved-By: Tom Tromey <tom@tromey.com>
Tom
next prev parent reply other threads:[~2026-08-21 15:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-30 5:48 Aditya Vidyadhar Kamath
2026-08-21 15:43 ` Tom Tromey [this message]
2026-08-24 6:48 ` Aditya Kamath
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=874ignscm6.fsf@tromey.com \
--to=tom@tromey.com \
--cc=Aditya.Kamath1@ibm.com \
--cc=PRAJWAL.B.MEHENDARKAR@ibm.com \
--cc=akamath996@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=sangamesh.swamy@in.ibm.com \
--cc=simon.marchi@polymtl.ca \
--cc=ulrich.weigand@de.ibm.com \
/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