Issue: compiling in ubuntu

[carmenchu]

To begin, many thanks: following instructions in GitHub, I have succeeded in compiling a functional Sigil with plug-in support. A moral boost for a rank beginner to Linux!!
However, there was an error report, which appears also in sigil.ini

[mainwindow]
clipboardringhistory="Traceback (most recent call last):\n  File \"/usr/lib/python3.12/ctypes/__init__.py\", line 450, in __getattr__\n\n    dll = self._dlltype(name)\n          ^^^^^^^^^^^^^^^^^^^\n  File \"/usr/lib/python3.12/ctypes/__init__.py\", line 379, in __init__\n    self._handle = _dlopen(self._name, mode)\n                   ^^^^^^^^^^^^^^^^^^^^^^^^^\nOSError: /usr/lib/x86_64-linux-gnu/sigil/libhunspell.so: cannot open shared object file: No such file or directory\n\nDuring handling of the above exception, another exception occurred:\n\nTraceback (most recent call last):\n  File \"/usr/share/sigil/plugin_launchers/python/launcher.py\", line 317, in <module>\n    sys.exit(main())\n             ^^^^^^\n  File \"/usr/share/sigil/plugin_launchers/python/launcher.py\", line 281, in main\n    bc = ValidationContainer(rk)\n         ^^^^^^^^^^^^^^^^^^^^^^^\n  File \"/usr/share/sigil/plugin_launchers/python/validationcontainer.py\", line 41, in __init__\n    super(ValidationContainer, self).__init__(wrapper, debug)\n  File \"/usr/share/sigil/plugin_launchers/python/outputcontainer.py\", line 42, in __init__\n    self.hspell = HunspellChecker(wrapper.get_hunspell_path())\n\n                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n  File \"/usr/share/sigil/plugin_launchers/python/pluginhunspell.py\", line 49, in __init__\n    self.hunspell = cdll[hunspell_dllpath]\n                    ~~~~^^^^^^^^^^^^^^^^^^\n  File \"/usr/lib/python3.12/ctypes/__init__.py\", line 457, in __getitem__\n    return getattr(self, name)\n           ^^^^^^^^^^^^^^^^^^^\n  File \"/usr/lib/python3.12/ctypes/__init__.py\", line 452, in __getattr__\n    raise AttributeError(name)\nAttributeError: /usr/lib/x86_64-linux-gnu/sigil/libhunspell.so\n\n", "File \"/usr/lib/python3.12/ctypes/__init__.py\", line 452, in __getattr__\n    raise AttributeError(name)\nAttributeError: /usr/lib/x86_64-linux-gnu/sigil/libhunspell.so", sudo apt install default-jre, Thane
fullscreen=false

...
??

[KevinH]

The error message is:

OSError: /usr/lib/x86_64-linux-gnu/sigil/libhunspell.so: cannot open shared object file: No such file or directory

I took the liberty to reformat your error information to be more readable here:

[mainwindow]
clipboardringhistory="Traceback (most recent call last):
File \"/usr/lib/python3.12/ctypes/__init__.py\", line 450, in __getattr__

    dll = self._dlltype(name)
          ^^^^^^^^^^^^^^^^^^^
  File \"/usr/lib/python3.12/ctypes/__init__.py\", line 379, in __init__
    self._handle = _dlopen(self._name, mode)
                   ^^^^^^^^^^^^^^^^^^^^^^^^^
OSError: /usr/lib/x86_64-linux-gnu/sigil/libhunspell.so: cannot open shared object file: No such file or directory

During handling of the above exception, another exception occurred:\

Traceback (most recent call last):
  File \"/usr/share/sigil/plugin_launchers/python/launcher.py\", line 317, in <module>
    sys.exit(main())
             ^^^^^^
  File \"/usr/share/sigil/plugin_launchers/python/launcher.py\", line 281, in main
    bc = ValidationContainer(rk)
         ^^^^^^^^^^^^^^^^^^^^^^^
  File \"/usr/share/sigil/plugin_launchers/python/validationcontainer.py\", line 41, in __init__
    super(ValidationContainer, self).__init__(wrapper, debug)

  File \"/usr/share/sigil/plugin_launchers/python/outputcontainer.py\", line 42, in __init__
    self.hspell = HunspellChecker(wrapper.get_hunspell_path())
                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File \"/usr/share/sigil/plugin_launchers/python/pluginhunspell.py\", line 49, in __init__
    self.hunspell = cdll[hunspell_dllpath]
                    ~~~~^^^^^^^^^^^^^^^^^^
  File \"/usr/lib/python3.12/ctypes/__init__.py\", line 457, in __getitem__
    return getattr(self, name)
           ^^^^^^^^^^^^^^^^^^^
  File \"/usr/lib/python3.12/ctypes/__init__.py\", line 452, in __getattr__
    raise AttributeError(name)
AttributeError: /usr/lib/x86_64-linux-gnu/sigil/libhunspell.so", 
"File \"/usr/lib/python3.12/ctypes/__init__.py\", line 452, in __getattr__
    raise AttributeError(name)
AttributeError: /usr/lib/x86_64-linux-gnu/sigil/libhunspell.so", 
sudo apt install default-jre

The plugin cannot find the hunspell spellchecker library where it is supposed to be. Almost as it was never built.

Did you configure the build to use Sigil's version of the hunspell spellchecker or did you configure the build to use your system hunspell?


Have you thought about downloading and installing our latest released Sigil AppImage for Linux? It is prebuilt by us and released alongside our Windows and Mac versions of Sigil. It should work just fine on your system.

[DiapDealer]

Yes. The cmake options used when Sigil was built will prove useful.

Also, copying from the clipboard history of the Sigil ini seems like a long way around the barn. Surely the errors present in the PluginRunner dialog and/or the terminal Sigil is launched from as well?

Can I ask why you changed Sigil's default install prefix to /usr? The /usr prefix is typically reserved for packaged software from official repositories. The default prefix when using cmake to compile software is typically /usr/local unless specifically changed.

EDIT: Changing the prefix is probably the issue. If you'd used the default prefix of /usr/local everything should have worked fine. But since you specifically changed the prefix to /usr, the multi-arch lib subdirectory comes into play on Ubuntu (x86_64-linux-gnu). If you do decide to go with the /usr prefix (not something I really recommend), you will probably need to add -DCMAKE_INSTALL_LIBDIR=lib to your cmake configure before compiling Sigil. But it's probably better just to leave /usr to Ubuntu packaged software instead.

[philja]

Originally Posted by carmenchu

To begin, many thanks: following instructions in GitHub, I have succeeded in compiling a functional Sigil with plug-in support. A moral boost for a rank beginner to Linux!!

Like you, I was very pleased with learning how to compile Sigil for myself on Ubuntu.

But, as soon as the new AppImage for linux was launched, I found that I could have the latest version of Sigil up and running within two minutes of completing the download, including editing the launcher.

I recommend the AppImage to all linux users as a great time saver over compiling your own.

https://sigil-ebook.com/sigil/download/

or, if you want to check the download checksums (which is always good practice):

https://github.com/Sigil-Ebook/Sigil/releases/

[carmenchu]

1. So far as I know, I didn´t change a single default configuration from the instructions in GitHub. As a matter of fact, I only did copy-paste--and modified only when result was an error message. I.e.: changing python to python3 following an error prompt, or prefacing sudo to make when without gave error.
2. I had previously installed Sigil from the package for my distribution appearing in the links, but uninstalled it--because of lack of plug-in support--before compiling. However, not surprisingly, there were residuals in the preferences directory, among which a sigil.ini--new one sigil_v6.ini--which shows the same error code as in my original post. ??
3. Tried to install the appimage, but was unable to get it to work. Surely my fault--still wrestling with the OS... By the way:
how does one add an environment variable to ubuntu-mate-24.04.2? Unable to find a working instruction...
Again, many thanks!

[DiapDealer]

It definitely sounds like you have residual pieces of other installs getting in the way, but I'm confused about the need to modify the instructions "following an error prompt." All Ubuntu instructions already have python3-* indicated where necessary, and sudo indicated where required. There should be no `sudo make` needed.

The following command can be copied and pasted for convenience on Debian-based systems:

sudo apt-get install python3-dev python3-pip python3-lxml python3-six python3-css-parser python3-dulwich

Once the cmake configure command finishes with no errors, build Sigil with:

make (or make -j4 if you have plenty of processor cores)

Installing Sigil
If all goes well, install Sigil with:

sudo make install

[carmenchu]

Re:Quote
The substitution python --> python3 happened at some other point--perhaps creating the virtual environment for plugins?

[DiapDealer]

The only reason I can think of why the AppImage would not work for you (the AppImage is created using Ubuntu after all) is that you failed to make it executable after downloading it. You should be able to do that be right-clicking the AppImage and finding the "properties" tab (this will vary visually depending on your particular Desktop Environment) and checking the executable box.

Once that's done, it's simply a matter of double-clicking the AppImage to launch it (and making sure the "Use bundled Python" box is checked in Sigil's plugin preferences before trying any plugins).

[DiapDealer]

Originally Posted by carmenchu

Re:Quote
The substitution python --> python3 happened at some other point--perhaps creating the virtual environment for plugins?

Gotcha. I'll make a note of python3 being necessary on some distros in those virtual Python environment instructions. Thanks.

[carmenchu]

Thanks, DiapDealer. Please,
* Should I uninstall the compiled version of Sigil & delete its preferences, if trying the appimage?
* What about the environment variables? Terminal +
env SIGIL_ALLOW_CODEVIEW_DROP sigil
works without trouble on my system, but I am at loss to implement it to run from default launchers. Sorry--a beginner silly question, of course!

[KevinH]

You could deinstall the compiled version but no need to delete its Preferences.

The way to set an environment variable so it is kept across logouts in any unix is to edit your ~/.profile or ~/.bashrc file (depending on which your system uses) and add the following line:

export SIGIL_ALLOW_CODEVIEW_DROP=1

Your .bashrc or .profile is run once for every new login session, and it sets and exports any environment vars for all programs you run.

I am not a Ubuntu user so I have no idea whether it is your .bashrc or .profile file but it can not hurt to add it to both if both are present.

[carmenchu]

Thanks, Kevin! Both files present in [USER]--adding to .profile seems enough. The documentation/ examples for those files are referenced but not included anywhere--so, thanks again.