View Single Post
Old 11-25-2015, 04:07 PM   #33
AlPe
Digital Amanuensis
AlPe ought to be getting tired of karma fortunes by now.AlPe ought to be getting tired of karma fortunes by now.AlPe ought to be getting tired of karma fortunes by now.AlPe ought to be getting tired of karma fortunes by now.AlPe ought to be getting tired of karma fortunes by now.AlPe ought to be getting tired of karma fortunes by now.AlPe ought to be getting tired of karma fortunes by now.AlPe ought to be getting tired of karma fortunes by now.AlPe ought to be getting tired of karma fortunes by now.AlPe ought to be getting tired of karma fortunes by now.AlPe ought to be getting tired of karma fortunes by now.
 
AlPe's Avatar
 
Posts: 727
Karma: 1446357
Join Date: Dec 2011
Location: Turin, Italy
Device: Several eReaders and tablets
Speaking of issues building Sigil 0.9.0 from source on Debian (Jessie):

I built Sigil 0.9.0 from source following https://github.com/Sigil-Ebook/Sigil...dingOnLinux.md (using the Release ZIP, not cloning from GitHub), and the cmake -> make -> make install completed without a problem.

When I launch the compiled sigil executable I get a dialog saying "error in xmlprocessor repairXML" (which I believe comes from: https://github.com/Sigil-Ebook/Sigil...ource.cpp#L103 ). It seems a problem running Python and/or BeautifulSoup.

So I tried:

1. setting explicitly the CMAKE options for Python paths (since my default Python is 2.7, albeit CMAKE picked Python 3.4 correctly at the first try)

2. building in a virtualenv with Python 3.4 only

3. installing into a local, unprivileged directory instead of the default /usr/... privileged directory

but in all cases I get the same error.

BeautifulSoup (and all the other suggested Python modules) are installed and available for Python 3.4, I tried importing them one by one and they work in the Python interpreter.

The only difference w.r.t. the guide is that I am using Qt5.5.1, installed in /opt/ using the graphical installer.

Any ideas?
AlPe is offline   Reply With Quote