https://bugs.kde.org/show_bug.cgi?id=470381
--- Comment #2 from hqu...@outlook.com --- Created attachment 160673 --> https://bugs.kde.org/attachment.cgi?id=160673&action=edit Screenshot showing that the julia backend works with symlink I attached a screenshot showing that the julia backend is really working and that the executable is a symlink. However, if I do the following, I get an error `Julia session can't login due internal julia problem with missing internal file - "/home/joshua/kde/src/lib/julia/sys.so"` 1. link julia to the current directory `ln -s $(which julia) ./julia` 2. add current directory to path `PATH=$(pwd):$PATH` 3. run cantor and select julia backend 4. try 1+1 From https://invent.kde.org/education/cantor/-/blob/670993d7bf38afcacd2914509d621761dd8e4e60/src/backends/julia/juliaserver/juliaserver.cpp#L27, the error occurs since the .so file cannot be found and the fallback path is `../lib/julia/sys.so`. So, I guess that the issue with symlinks depends on whether you also correctly symlink the lib/julia/sys.so file. However, the official installation instructions (https://julialang.org/downloads/platform/#linux_and_freebsd) for julia only recommends linking the julia binary and has no suggestions for also linking the shared library. Perhaps the restriction for symlinks could be removed and canonicalPath() could be used instead of dir().absolutePath() on line 32. (documentation for canonicalPath https://doc.qt.io/qt-5/qfileinfo.html#canonicalPath). This replacement allows the julia symlink in my current directory (which is on my path) to work. -- You are receiving this mail because: You are watching all bug changes.
