Arch Linux User Repository

Since libmupdf updated to v1.24.2-1 in the Arch repo sioyek is not able to load the library with the error:

sioyek: error while loading shared libraries: libmupdf.so.24.1: cannot open shared object file: No such file or directory

Running sioyek after installing this package gives me the following error:

cannot create context: incompatible header (1.23.7) and library (1.23.10) versions
could not create mupdf context

sioyek-git does work for me.

@TomHu I think this should be a separate package and not be included here...

Would you be able to include: https://github.com/ahrm/sioyek-python-extensions

into the package?

Since libmupdf 1.23.3-2, that library is built shared, instead of static. This means also that libmupdf-third.a is no longer available, which in turn means this build fails.

I fixed this by just adding this in the prepare step:

sed -i 's/-lmupdf-third//' pdf_viewer_build_config.pro

I've been having issues with https://github.com/ahrm/sioyek/issues/539 and was able to fix them with https://github.com/MithicSpirit/aur-sioyek-mupdf-fix. Lmk if you're interested in merging those changes here (obviously make sure to undo some of them like maintainer field, pkgname change, pkgrel drop); if not, I'll probably publish them as a separate package here soon.

EDIT: you might want to uncomment that line in prepare(). I commented it while testing and never bothered to see if it actually mattered or not.

EDIT 2: note that this also removes the need for the patch from before.

@MithicSpirit I have indeed mounted ~/.cache as a separate partition with the option noexec. Thank you for the hint. I think this explains my issue.

@aexl Hi, it seems like that there is a bug about libmupdf causing crash on specific pdf file. And I posted details in GitHub issue. Version: sioyek 2.0.0-3.

@Dominik Ah, that's a different issue than the one I had. Mine was with gcc failing to compile the project due to it attempting to use an undefined function (one that was missing from the newer version of mupdf). Have you perchance configured pikaur and paru to use a different partition for compilation? If the partition has noexec set then it would fail. It seems that compilation is occurring in ~/.cache, and I know some people like to use a different partition for that to make it ephemeral.

@MithicSpirit

I don't think the error occurs due to an inconsistency with pikaur. I had the same issue with paru.

The error which I reported here on 2023-08-02 is still the same. There seem to be missing permissions to run line 35 in ./build_linux.sh. Pikaur is using the latest PKGBUILD:

:: AUR package will be installed:
 sioyek                                                     -> 2.0.0-3

:: Starting the build:
==> Making package: sioyek 2.0.0-3 (Sat Sep  2 09:47:05 2023)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Downloading sioyek-2.0.0.tar.gz...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100 4785k    0 4785k    0     0  3516k      0 --:--:--  0:00:01 --:--:-- 7217k
  -> Found mupdf-1.23.0.patch
==> Validating source files with sha256sums...
    sioyek-2.0.0.tar.gz ... Passed
    mupdf-1.23.0.patch ... Passed
==> Extracting sources...
  -> Extracting sioyek-2.0.0.tar.gz with bsdtar
==> Starting prepare()...
patching file pdf_viewer/document_view.cpp
patching file pdf_viewer/main_widget.cpp
patching file pdf_viewer/utils.cpp
patching file pdf_viewer/utils.h
==> Starting build()...
/home/niggi/.cache/pikaur/build/sioyek/PKGBUILD: line 35: ./build_linux.sh: Permission denied
==> ERROR: A failure occurred in build().
    Aborting...

Command 'sudo --user=#1000 --preserve-env=EDITOR -- makepkg --force' failed to execute.