On Sat, 2017-07-29 at 00:23 +0100, Ken Moffat wrote: > I'm just flagging this up here, in the hope that somebody can help > me understand what the hell changed. > > I'm doing a fresh build of svn on one of my test machines - I've > built this same version of gimp-help several times this year, last > time used packages from late May including Python-2.7.13 which is > what I've got on this build. > > Today it decided to fail: > make[1]: Entering directory > '/scratch/working/gimp-help-2.8.2/quickreference' > /bin/mkdir -p xml > ../tools/xml2po.py -p po/de.po ./gimp-keys.xml > > xml/gimp-keys-de.xml > Traceback (most recent call last): > File "../tools/xml2po.py", line 190, in <module> > main(sys.argv[1:]) > File "../tools/xml2po.py", line 87, in main > from xml2po import Main > File "/scratch/working/gimp-help-2.8.2/tools/xml2po/__init__.py", > line 27, in <module> > import libxml2 > ImportError: No module named libxml2 > > and sure enough in the gimp-help-2.8.2/tools/xml2po/__init__.py file > the first things after the License are a string of imports: > import os > import sys > import re > import subprocess > import tempfile > import gettext > import libxml2 > > so on the face of it, it has always needed to import libxml2.py. > But in my log from the previous build it sailed through: > > make[1]: Entering directory > '/scratch/working/gimp-help-2.8.2/quickreference' > /bin/mkdir -p xml > ../tools/xml2po.py -p po/fr.po ./gimp-keys.xml > xml/gimp-keys-fr.xml > > The order in which it processes the languages there seems to be > random (make -j4), but in the current system the error was repeated for > several including fr. > > On a whim I tried using MAKEFLAGS of -j1, but all that did was make > it stop after the first such error (for 'ca' this time). > > AFAICS, I've never had the python libxml2 module installed when I've > built gimp-help before, although on the occasions when I've later > installed asymptote I've rebuilt Python so that I can get > _tkinter.so and I see that those installs did give me libxml2.py. > > As is usual with Python, I'm baffled. Can anybody offer any > theories for why this has suddenly failed, please ? Or, perhaps > more accurately, why it didn't fail in the past ? > > I note from the libxml2 instructions that Python is recommended so > that libxml2 will build and install a Python library module, but a > quick look at recent logs only shows libxml2-python documentation, > not a module. > > I suspect I'm going to have to rebuild Python2 after libxml2 has been > installed to now get gimp-help to build. > > TIA > > ĸen > -- > I live in a city. I know sparrows from starlings. After that > everything is a duck as far as I'm concerned. -- Monstrous Regiment
My first guess without looking at it to deeply would be that you've built libxml2 with python3 instead of python2 modules. use --with-python=/usr/bin/python2 to make sure that libxml2 builds with python2. Regards, Wayne -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
