On Sat, 17 Apr 2021 15:54:38 +0200, Achim Gratz > Lemures Lemniscati via Cygwin-apps writes: > > (2) The situation occurs at testing to load just-built modules > > /usr/bin/python3.6 -c 'import xapian' > > /usr/bin/python3.6 -O -c 'import xapian' > > > > And weirdly, only first runs will crash. > > That symptom indicates that probably BLODA injects itself into the image > when it detectes a new DLL and then stops doing that when it has > determined that DLL to be benign. For many reasons you should exclude > your build directories from getting subjected to that sort of behaviour > (if you can do that), this is just one of them. > > > (4) With this patch, modules for python 3.6 on i686 will be built > > successfully. > > Although both two dummy runs in [1] are expected to crash, > > they don't crash, weirdly. > > AS long as the workaround gets you a successful build I'd not worry too > much about it. Just document somehwere that it's a workaround and what > problem it was trying to solve.
Thank you, Achim. Now, I've prepared cygport files for xapian-core and xapian-bindings: https://github.com/cygwin-lem/xapian-core-cygport/tree/n_1.4.18-1 https://github.com/cygwin-lem/xapian-bindings-cygport/tree/n_1.4.18-1 And their test packages (added python 3.8 modules, dropped python 2.7 modules): https://cygwin-lem.github.io/xapian-core-cygport/ https://cygwin-lem.github.io/xapian-bindings-cygport/ Regards, Lem
