I can confirm a segfault on startup. Your gdb attempt fails as /bin/sigil is just a wrapper script, you'd need to run gdb on /usr/lib/sigil/sigil (with the proper environment settings from the /bin/sigil script). But this does appear to be a bug that should go to the bug tracker if it's not already there yet - though collecting some more info here first might help in creating a detailed report.
So I looked further and checked one of the first advanced ports tolinux, Doom Legacy. This port ismore than 20 years old but there are still new releases. And to mysurprise it actually runs Sigil very fine. Just start it with
Sigil uses Qt as its application framework and embeds WebKit to renderHTML book contents. However, the Linux downloads are InstallJammer installers ratherthan standard RPM or Debian packages, and they bundle their own copy of thenecessary .so files, placing everything in /opt/sigil/.Presumably this installation choice is the result of structuring the codeto produce cross-platform packages for those OSes that cannot simply fetchthe necessary dependencies through their package managers. As a result ofthat choice, though, the installer weighs in at 20.5MB and you end up with someduplicate libraries. Hopefully distributions will eventually startpackaging Sigil themselves to avoid that duplication.
Dependencies can be explicitly requested using the ^ sigil. Note thatthe spec syntax is recursive. Anything we could specify about thetop-level package, we can also specify about a dependency using ^.
Packages can also be referred to from the command line by their packagehash. Using the spack find -lf command earlier we saw that the hashof our optimized installation of zlib (cppflags="-O3") began with64mns5m. We can now explicitly build with that package without typingthe entire spec, by using the / sigil to refer to it by hash. As withother tools like git, you do not need to specify an entire hash on thecommand line. You can specify just enough digits to identify a hashuniquely. If a hash prefix is ambiguous (i.e., two or more installedpackages share the prefix) then spack will report an error.
Spack packages can also have build options, called variants. Booleanvariants can be specified using the + and or -sigils. There are two sigils for False to avoid conflicts withshell parsing in different situations. Variants (boolean or otherwise)can also be specified using the same syntax as compiler flags. Herewe can install HDF5 without MPI support.