Make errors on Mint 22

[darkbreath]

Are these fatal to compilation/installation, or can I ignore the errors?

$ cmake -DUSE_SYSTEM_LIBS=1 -G "Unix Makefiles" -DCMAKE_BUILD_TYPE=Release ../sigil-src
-- The C compiler identification is GNU 13.2.0
-- The CXX compiler identification is GNU 13.2.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Trying to use System Libraries...
-- Found ZLIB: /usr/lib/x86_64-linux-gnu/libz.so (found version "1.3")  
-- Found PkgConfig: /usr/bin/pkg-config (found version "1.8.1") 
-- Found MiniZip: /usr/lib/x86_64-linux-gnu/libminizip.so
-- Checking for module 'hunspell'
--   Found hunspell, version 1.7.2
-- Checking for module 'libpcre2-16'
--   Found libpcre2-16, version 10.42
-- CMake version in use: 3.28.3
-- Using older findpython cmake module
-- Found PythonInterp: /usr/bin/python3 (found suitable version "3.12.3", minimum required is "3.4") 
-- Found PythonLibs: /usr/lib/x86_64-linux-gnu/libpython3.12.so (found suitable version "3.12.3", minimum required is "3.4") 
-- Using System ZLIB
-- Using System MiniZip
-- Using System Hunspell
-- Using System PCRE2
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Success
-- Found Threads: TRUE  
-- Performing Test HAVE_STDATOMIC
-- Performing Test HAVE_STDATOMIC - Success
-- Found WrapAtomic: TRUE  
-- Found OpenGL: /usr/lib/x86_64-linux-gnu/libOpenGL.so   
-- Found WrapOpenGL: TRUE  
-- Could NOT find XKB (missing: XKB_LIBRARY XKB_INCLUDE_DIR) (Required is at least version "0.5.0")
-- Found WrapVulkanHeaders: /usr/include  
-- Using older PYTHON_LIBRARIES CMAKE variable to link to Python
-- Configuring done (0.6s)
-- Generating done (0.0s)
-- Build files have been written to: (Redacted)

Anyway, I don't know if the compilation was the cause or if checkinstall was the cause (I used checkinstall instead of make), but I got this when I tried to install:

Installing with make install...

========================= Installation results ===========================
[  5%] Built target sigilgumbo
[  5%] Built target main
[  5%] Built target fluent
[  5%] Built target material
[  5%] Built target sigil_autogen_timestamp_deps
[  6%] Built target sigil_autogen
[100%] Built target sigil
Install the project...
-- Install configuration: "Release"
CMake Error at src/cmake_install.cmake:52 (file):
  file INSTALL destination: /usr/local/lib/sigil is not a directory.
Call Stack (most recent call first):
  cmake_install.cmake:49 (include)


make: *** [Makefile:100: install] Error 1

****  Installation failed. Aborting package creation.

Cleaning up...OK

Bye.

[Doitsu]

Did you maybe forget to add sudo?

sudo make install

[DiapDealer]

Definitely need sudo to install to the default prefix of /usr/local.

I don't see any errors in your configure output. If you're talking about the missing XKB message, that's not an error. There's a package that can be installed that makes it go away, but I forget what it is at the moment. It's not terribly important, but I'll track it down if I can.

[DiapDealer]

I also don't use checkinstall, so I don't know how that may affect things regarding sudo.

If you want to make the XKB message go away in the cmake configure, make sure the following two packages are installed:

libxkbcommon-dev (might already be installed, but check)
libxkbfile-dev

[darkbreath]

It's possible I forgot sudo on the checkinstall. I will test again.

The main reason I use checkinstall is because there's a consistent way to uninstall the app later. If the problem turns out not to be checkinstall rather than forgetting sudo, I might have to use "sudo make". can you please go over how to uninstall a copy of Sigil that was installed with "sudo make install"? I did a search but the post I found was from 2013: https://www.mobileread.com/forums/sh...d.php?t=225173

Is it still the case that deleting those 4 files/folders alone will uninstall Sigil completely? I know about the apt-get packages, but I'm not too worried about those because apt-get provides an easy way remove packages.

[DiapDealer]

Originally Posted by darkbreath

Is it still the case that deleting those 4 files/folders alone will uninstall Sigil completely?

It's a tiny bit different, but not much.

Delete 'sigil' from /usr/local/bin
Delete the entire sigil directory in /usr/local/share
Delete the entire sigil directory in /usr/local/lib
Delete 'sigil.png' from /usr/local/share/pixmaps
Delete 'sigil.desktop' from /usr/local/share/applications

Also note that whenever you use (sudo) make install, an install_manifest.txt file gets created (in the folder where make install was run) that contains all the files and where they were copied to.

I know of the benefits of checkinstall. It's just that working on Sigil as long as I have, it's quicker for me to manually delete a Sigil installation than it would be for me look up how to use checkinstall all over again.

[darkbreath]

Thanks! I finally found the time to retry the checkinstall. I definitely didn't forget sudo this time, but I got the same error. It looks like there's some kind of incompatibility between 2.3.1 and the current version of checkinstall I have (1.6.2). I installed with sudo make install, which I normally try to avoid, but thankfully your installer has a sane uninstallation process. There are other app installers that require you to go through extreme terminal jiujitsu to undo. I also didn't know about the install_manifest.txt. Thanks!

Any chance you could add libxkbcommon-dev and libxkbfile-dev to the installation instructions, even if marked as optional? My concern is twofold: If the installation fails, one would wonder as I did whether that warning message was the cause. Even if the installation succeeds, it might have some subtle flaw that doesn't become obvious until much later.

Also, as a final check, are these 2 failures of the test plugin meaningful?:

Status: success

 
Verify sys.path settings manually
  /usr/local/share/sigil/plugin_launchers/python
  /usr/lib/python312.zip
  /usr/lib/python3.12
  /usr/lib/python3.12/lib-dynload
  /usr/local/lib/python3.12/dist-packages
  /usr/lib/python3/dist-packages
  /usr/lib/python3.12/dist-packages
  /home/(redacted))/.local/share/sigil-ebook/sigil/plugins/testplugin
 
Verifying proper Python packages are available
  Checking GUI modules
    Python Package: PyQt5 Missing
    Python Package: PyQt5 QtWebEngineWidgets Missing
    Python Package: tkinter (/usr/lib/python3.12/tkinter/__init__.py) Found
  Python Package: PIL (/usr/lib/python3/dist-packages/PIL/__init__.py) Found
  Python Package: cssselect (/usr/lib/python3/dist-packages/cssselect/__init__.py) Found
  Python Package: css-parser (/usr/lib/python3/dist-packages/css_parser/__init__.py) Found
  Python Package: html5lib (/usr/lib/python3/dist-packages/html5lib/__init__.py) Found
  Python Package: lxml (/usr/lib/python3/dist-packages/lxml/__init__.py) Found
  Python Package: regex (/usr/lib/python3/dist-packages/regex/__init__.py) Found
  Python Package: chardet (/usr/lib/python3/dist-packages/chardet/__init__.py) Found
  Python Package: six (/usr/lib/python3/dist-packages/six.py) Found
  Python Package: dulwich (/usr/lib/python3/dist-packages/dulwich/__init__.py) Found
  Python Package: urllib3 (/usr/lib/python3/dist-packages/urllib3/__init__.py) Found
 
Verifying Sigil Python Libraries can be found/loaded
  Sigil Python library: epub_utils Found
  Sigil Python library: quickparser Found
  Sigil Python library: hrefutils Found
  Sigil Python library: compatibility_utils Found
  Sigil Python library: sigil_bs4 Found
 
Verifying Hunspell Spell Checking
  Hunspell en_US affix file and dictionary Found
  Hunspell shared library Found
  Hunspell spellchecking works True
  
Verifying Sigil Gumbo Library operation
  Sigil Gumbo BS4 Adapter library Found
  Sigil BS4/Gumbo Parser works True
 
Verifying selected basic plugin interface elements
  bk.text_iter() works True
  Listing manifested files...
    Text/Section0001.xhtml
    Text/nav.xhtml
    Styles/sgc-nav.css
  bk.manifest_iter() works True
  bk.spine_iter() works True
  bk.other_iter() works True
  reading a non-manifest book file works True
  reading a specific OPF manifest id works True
  writing to a specific OPF manifest id works True
  Launcher Version 20240803
  ePub Version 3.0
  adding your own file to the manifest works True
  basename to id mapping works True
  deleting our added file works True
 
 
Failure -  2  Tests of Plugin Operations Failed

Are these the 2 failed plugin operations?:
1. Python Package: PyQt5 Missing
2. Python Package: PyQt5 QtWebEngineWidgets Missing

[DiapDealer]

I'll take the XKB stuff under advisement, but there are always going to be warnings like this that pop up over time. It's hard to keep up with them. And as already mentioned, there is no actual error being reported when the initial cmake can't find that particular library.

As to your reported missing PyQt5 modules, you must not be running the latest test plugin. Sigil 2.3.1 does not use Qt5 and v20 of the test plugin should be testing for PySide6 modules instead. If you ARE running v20 of the test plugin, then something in Sigil 2.3.0+'s plugin framework must have broken it. But v20 of the test plugin is properly looking for PySide6 modules in my usage.

[darkbreath]

Ok, fair point about the XKB stuff. I didn't realize this type of problem was so common. No pressure to add in all those trivial packages if so.

A better solution might be to just show me what real errors look like during the make process. Just to be clear, the only reason I was even looking for errors is because of the message "If there are no errors, you're ready to build." Instead of listing every trivial package, maybe you could just explain that message by showing the exact wording of what an error looks like. Any trivial package like the XKB ones wouldn't matter then, because the message associated with missing packages would presumably not match the wording of a true error.

Also, you were right. I was mistakenly running version 19 of the test plugin because the build page for Linux (https://github.com/Sigil-Ebook/Sigil...ng_on_Linux.md) still linked directly to it. Maybe instead of a direct link you could just tell people to look for it under the docs folder in the repo. That would spare you the trouble of remembering to update the link every time there's a new version of the test plugin.

[DiapDealer]

Originally Posted by darkbreath

Also, you were right. I was mistakenly running version 19 of the test plugin because the build page for Linux (https://github.com/Sigil-Ebook/Sigil...ng_on_Linux.md) still linked directly to it. Maybe instead of a direct link you could just tell people to look for it under the docs folder in the repo. That would spare you the trouble of remembering to update the link every time there's a new version of the test plugin.

Yes. I'll fix that ASAP. I didn't realize there was a direct link in the documentation. Thanks!

[darkbreath]

Awesome! Speaking of errors, if I did run into a true error during the cmake step, would I know about it? All I took away is that "Could not find XKB" (despite the part of the line about a required package) was NOT an error.

If I see "Build files have been written", is it safe to conclude there were no true errors?

[KevinH]

You typically see a message that says "error" and the build process stops prematurely.

[darkbreath]

I ran version 20 of the plugin, but I get similar errors for a different version of QT:

Status: success

 
Verify sys.path settings manually
  /usr/local/share/sigil/plugin_launchers/python
  /usr/lib/python312.zip
  /usr/lib/python3.12
  /usr/lib/python3.12/lib-dynload
  /usr/local/lib/python3.12/dist-packages
  /usr/lib/python3/dist-packages
  /usr/lib/python3.12/dist-packages
  /home/(redacted)/.local/share/sigil-ebook/sigil/plugins/testplugin
 
Verifying proper Python packages are available
  Checking GUI modules
    Python Package: PySide6 Missing
    Python Package: PySide6 QtWebEngineWidgets Missing
    Python Package: tkinter (/usr/lib/python3.12/tkinter/__init__.py) Found
  Python Package: PIL (/usr/lib/python3/dist-packages/PIL/__init__.py) Found
  Python Package: cssselect (/usr/lib/python3/dist-packages/cssselect/__init__.py) Found
  Python Package: css-parser (/usr/lib/python3/dist-packages/css_parser/__init__.py) Found
  Python Package: html5lib (/usr/lib/python3/dist-packages/html5lib/__init__.py) Found
  Python Package: lxml (/usr/lib/python3/dist-packages/lxml/__init__.py) Found
  Python Package: regex (/usr/lib/python3/dist-packages/regex/__init__.py) Found
  Python Package: chardet (/usr/lib/python3/dist-packages/chardet/__init__.py) Found
  Python Package: six (/usr/lib/python3/dist-packages/six.py) Found
  Python Package: dulwich (/usr/lib/python3/dist-packages/dulwich/__init__.py) Found
  Python Package: urllib3 (/usr/lib/python3/dist-packages/urllib3/__init__.py) Found
 
Verifying Sigil Python Libraries can be found/loaded
  Sigil Python library: epub_utils Found
  Sigil Python library: quickparser Found
  Sigil Python library: hrefutils Found
  Sigil Python library: compatibility_utils Found
  Sigil Python library: sigil_bs4 Found
 
Verifying Hunspell Spell Checking
  Hunspell en_US affix file and dictionary Found
  Hunspell shared library Found
  Hunspell spellchecking works True
  
Verifying Sigil Gumbo Library operation
  Sigil Gumbo BS4 Adapter library Found
  Sigil BS4/Gumbo Parser works True
 
Verifying selected basic plugin interface elements
  bk.text_iter() works True
  Listing manifested files...
    Text/Section0001.xhtml
    Text/nav.xhtml
    Styles/sgc-nav.css
  bk.manifest_iter() works True
  bk.spine_iter() works True
  bk.other_iter() works True
  reading a non-manifest book file works True
  reading a specific OPF manifest id works True
  writing to a specific OPF manifest id works True
  Launcher Version 20240803
  ePub Version 3.0
  adding your own file to the manifest works True
  basename to id mapping works True
  deleting our added file works True
 
 
Failure -  2  Tests of Plugin Operations Failed

[DiapDealer]

Yes. That's because the PySide6 python module is missing. Many (but not all) third-party plugins with GUI interfaces will need that module to work.

It's mentioned in the Getting Python 3.9+ section of the build documentation.

[darkbreath]

Ah I see it. I didn't fully understand that part of the instructions at first, but I did some reading about pip afterward, and I see what it meant now.

When I tried to install the package, I ran into that PEP 668 error and realized that I could potentially break os Python packages if I proceeded. Is there another option such as maybe installing a version of Python in Conda or some other virtual environment, then pointing Sigil there?