l.rei...@ucl.ac.uk writes:

 > I first tried to install it using Method 1
 > (https://docs.mailman3.org/en/latest/install/virtualenv.html#set-up-xapian),
 > however, xapian_wheel_builder.sh seems to just exit right as it
 > starts "preparing xapian wheel...".

I suppose this probably includes an invocation of "python -m build ...".
Try editing the xapian_wheel_builder.sh script to add the "-v" option
after "build" to try to get more information about what it did and (I
hope) why it didn't.  Not sure if multiple "-v" gives more information.

I believe you could also use the distutils build instead of wheel, and
ask pip to install that into the venv.  (I could be wrong, one of the
motivations for wheels was handling installation of binary Python
modules and auxiliary DSOs better.)

 > I ended up installing Xapian 1.4.29 from source and symlinking
 > xapian in the venv as per Method 2.

Method 2 is Debian-specific (it depends on Xapian and python-xapian
both being packaged).  What exactly did you do?

 > Has anyone else encountered this before?

I've done the python-xapian build and install for an Ubuntu host with
no problem.  I used the Ubuntu Xapian package and installed
python-xapian directly into the site-packages directory in the venv,
though.

I did need to work out a g++ version compatibility problem.  I assume
you're building the Python bindings in the same tree and at the same
time as the main application?  If so, you shouldn't have a problem
with library version mismatches.

-- 
GNU Mailman consultant (installation, migration, customization)
Sirius Open Source    https://www.siriusopensource.com/
Software systems consulting in Europe, North America, and Japan
_______________________________________________
Mailman-users mailing list -- mailman-users@mailman3.org
To unsubscribe send an email to mailman-users-le...@mailman3.org
https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
Archived at: 
https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/4AEHIYKC6SMHA7YVRAZNPJA54I3KMPRU/

This message sent to arch...@mail-archive.com

Reply via email to