[Xapian-tickets] [Xapian] #818: Build issue with 1.14.4 under python 3.12

Xapian nobody at xapian.org
Sun Jun 26 00:24:58 BST 2022


#818: Build issue with 1.14.4 under python 3.12
--------------------------------------+------------------------------------
 Reporter:  rouilj                    |             Owner:  Richard Boulton
     Type:  defect                    |            Status:  new
 Priority:  normal                    |         Milestone:
Component:  Xapian-bindings (Python)  |           Version:  1.4.14
 Severity:  normal                    |        Resolution:
 Keywords:                            |        Blocked By:
 Blocking:                            |  Operating System:  Linux
--------------------------------------+------------------------------------
Comment (by rouilj):

 Hi Olly:

 Thanks for your feedback. I am using 1.4.14 because that is what is
 supplied with Ubuntu 20.04:

   https://ubuntu.pkgs.org/20.04/ubuntu-universe-
 amd64/libxapian30_1.4.14-2_amd64.deb.html

 Ubuntu 20.04 is the newest build environment for travis ci and is the
 default for GitHub actions
 as well. Github was only able to release a beta of 22.04 Ubuntu last
 month.

 My Python 3.11 build works fine because I modify the configure script to
 use:
 {{{
   python3.11 -c 'import
 sysconfig;print(sysconfig.get_config_vars("EXT_SUFFIX")[0])'
 }}}
 which can be seen at:

   https://app.travis-ci.com/github/roundup-
 tracker/roundup/jobs/574465489#L785

 with the value:
 {{{
   PYTHON3_SO=`$PYTHON3 -c 'import
 sysconfig;print(sysconfig.get_config_vars("EXT_SUFFIX")[0])'`
 }}}

 The deprecation warnings I referred to aren't related (AFAICT) to
 distutils. They are g++
 compiler warnings. For example:
 {{{
 xapian_wrap.cc: In constructor
 ‘XapianSWIG_Python_Thread_Block::XapianSWIG_Python_Thread_Block()’:
 xapian_wrap.cc:87:32: warning: ‘int PyEval_ThreadsInitialized()’ is
 deprecated [-Wdeprecated-declarations]
    87 |  if (PyEval_ThreadsInitialized()) {
       |                                ^
 ...
 }}}

 Thoughts on why the macro expansion seems to be going wrong? Anything I
 can turn on to get
 more info for debugging.
-- 
Ticket URL: <https://trac.xapian.org/ticket/818#comment:2>
Xapian <https://xapian.org/>
Xapian


More information about the Xapian-tickets mailing list