From: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Issue with automake 1.16.4+ and python
Date: Wed, 22 Jun 2022 04:13:40 +0200 [thread overview]
Message-ID: <20220622021340.TF9B7QBm7P8rbn68i6MxpgiXI1K1XGLL-1HG1x25C-w@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33559@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2139 bytes --]
Closed issue by newbluemoon on void-packages repository
https://github.com/void-linux/void-packages/issues/33559
Description:
automake 1.16.4 made some changes to `python.m4` which leads to `$PYTHON_PREFIX` instead of `$prefix` ending up in pkg-config .pc files.
So far I have found two:
/usr/lib/pkgconfig/compizconfig-python.pc has a line
`pyexecdir=${PYTHON_EXEC_PREFIX}/lib/python3.10/site-packages`
and
/usr/lib/pkgconfig/xcb-proto.pc has
`pythondir=${pc_sysrootdir}${PYTHON_PREFIX}/lib/python3.10/site-packages`
xcb-proto is a dependency of polybar which fails to build right now because `$PYTHON_PREFIX` cannot be resolved.
There is a newer automake 1.16.5 where they again made some changes to `python.m4`, but the problem consists.
I found following patch (against 1.16.5) solves it (it actually reverts the lines to what they were before the change):
```
--- a/m4/python.m4 2021-10-04 04:51:12.000000000 +0200
+++ b/m4/python.m4 2021-10-15 08:38:08.575081215 +0200
@@ -263,7 +263,7 @@
case $am_cv_python_pythondir in
$am_py_prefix*)
am__strip_prefix=`echo "$am_py_prefix" | sed 's|.|.|g'`
- am_cv_python_pythondir=`echo "$am_cv_python_pythondir" | sed "s,^$am__strip_prefix,\\${PYTHON_PREFIX},"`
+ am_cv_python_pythondir=`echo "$am_cv_python_pythondir" | sed "s,^$am__strip_prefix,${PYTHON_PREFIX},"`
;;
*)
case $am_py_prefix in
@@ -305,7 +305,7 @@
case $am_cv_python_pyexecdir in
$am_py_exec_prefix*)
am__strip_prefix=`echo "$am_py_exec_prefix" | sed 's|.|.|g'`
- am_cv_python_pyexecdir=`echo "$am_cv_python_pyexecdir" | sed "s,^$am__strip_prefix,\\${PYTHON_EXEC_PREFIX},"`
+ am_cv_python_pyexecdir=`echo "$am_cv_python_pyexecdir" | sed "s,^$am__strip_prefix,${PYTHON_EXEC_PREFIX},"`
;;
*)
case $am_py_exec_prefix in
```
But I’m not sure about any implications. I filed a bug report upstream:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=51225
For reference:
https://git.savannah.gnu.org/cgit/automake.git/log/m4/python.m4
The problematic commits are the ones from 2021-05-18 and 2021-09-19.
prev parent reply other threads:[~2022-06-22 2:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-15 8:36 [ISSUE] " newbluemoon
2021-10-16 19:00 ` ahesford
2021-10-16 19:21 ` newbluemoon
2021-10-16 19:25 ` ahesford
2021-10-16 19:41 ` newbluemoon
2021-10-16 19:48 ` newbluemoon
2021-10-17 5:57 ` newbluemoon
2021-10-17 7:00 ` newbluemoon
2021-10-17 13:02 ` ahesford
2021-10-17 14:48 ` newbluemoon
2022-06-08 2:12 ` github-actions
2022-06-22 2:13 ` github-actions [this message]
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=20220622021340.TF9B7QBm7P8rbn68i6MxpgiXI1K1XGLL-1HG1x25C-w@z \
--to=ml@inbox.vuxu.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).