Package Details: miktex 25.4-1

Git Clone URL: https://aur.archlinux.org/miktex.git (read-only, click to copy)
Package Base: miktex
Description: a distribution of the TeX/LaTeX typesetting system
Upstream URL: https://miktex.org
Licenses: custom
Submitter: heavysink
Maintainer: heavysink (lilac)
Last Packager: lilac
Votes: 12
Popularity: 0.30
First Submitted: 2020-06-14 02:01 (UTC)
Last Updated: 2025-04-28 21:07 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 Next › Last »

Sven commented on 2022-07-28 19:09 (UTC)

Please don't hardcode -j2 in PKGBUILD. There's MAKEFLAGS in /etc/makepkg.conf. Also, I have 12 cores and 24 threads. My CPU is bored.

maniacata commented on 2022-05-27 08:50 (UTC) (edited on 2022-05-27 09:21 (UTC) by maniacata)

Looks like current binaries are using the wrong versions of icu and log4cxx.

miktex-console: error while loading shared libraries: liblog4cxx.so.12: cannot open shared object file: No such file or directory
miktex-console: error while loading shared libraries: libicui18n.so.70: cannot open shared object file: No such file or directory
# and so on

Use miktex-git to link the correct libraries, until newer binaries are released.

UPDATED:

I still need to build log4cxx 12, here's my PKGBUILD.

zeeshanali1993 commented on 2022-05-05 07:27 (UTC) (edited on 2022-05-05 07:27 (UTC) by zeeshanali1993)

kdesu is installed but still getting the following error:

No graphical sudo frontend is available. Please install 'pkexec', 'kdesu' (KDE) or 'gksu' (Gnome). 
Alternatively, you can enter 'sudo miktex-console --admin --finish-setup' in a terminal window.

loh.tar commented on 2022-01-31 19:42 (UTC)

The 'fop' package is not needed to build on Linux, only on Windows

loh.tar commented on 2022-01-29 18:58 (UTC)

Some of you had got the hint already from github, if heavysink not, here you are: https://github.com/MiKTeX/miktex/issues/917#issuecomment-1024964884

Sadly I'm not very lucky with the install in /opt and all the strange setup finish in Windows style. Before I may dig deeper, if it could be fixed, can I ask how well it works for you? (Yes, here is the wrong place for that...sorry)

Baenimyr commented on 2021-11-17 17:30 (UTC)

@heavysink You should split the build step in prepare and build functions. The prepare function configures CMake and the build function is just

build() {
    cmake --build "$srcdir/$pkgname-$pkgver/build" --
}

Note : use cmake commands instead of make because 'Unix Makefiles' is not the only generator.

heavysink commented on 2021-11-15 19:57 (UTC)

@CanadianEngineer Following https://github.com/MiKTeX/miktex/issues/917, it seems that the upstream dev do not want to fix that since Arch is "not supported" :-(. So I added options=('!buildflags') and it works now. The fix will be pushed by the buildbot lilac before tomorrow morning EST.

CanadianEngineer commented on 2021-11-15 00:46 (UTC) (edited on 2021-11-15 00:47 (UTC) by CanadianEngineer)

I was getting the 70% build error, and the recommended adjustment to the makepkg.conf worked for me. I'll list out the exact steps I took in hopes it helps someone else in the future!

The error I was getting:

[ 70%] Built target miktex-dvisvgm make: *** [Makefile:166: all] Error 2 ==> ERROR: A failure occurred in build(). Aborting...

As recommended, I edited my makepkg.conf file. I use vim, so be sure to use your favourite editor instead

sudo vim /etc/makepkg.conf

I replaced the CFLAG definition with this one:

CFLAGS="-march=x86-64 -mtune=generic -O2 -pipe -fno-plt -fexceptions \
        -Wp,-D_FORTIFY_SOURCE=2 -Wformat \
        -fstack-clash-protection -fcf-protection

reran the install yay -Sy miktex and it worked. I then went back to my makepkg.conf and replaced it with my original:

CFLAGS="-march=x86-64 -mtune=generic -O2 -pipe -fno-plt -fexceptions \                                                                                                                                                                    
        -Wp,-D_FORTIFY_SOURCE=2 -Wformat -Werror=format-security \
        -fstack-clash-protection -fcf-protection"

pmeier commented on 2021-10-12 11:02 (UTC)

  1. Can we create link to miktex-console in /usr/bin/? For example, if you try to switch to admin mode in the GUI, the error message tells you to use it, but it is not on path.
  2. Can we create link to initexmf, which is used multiple times in the "First Steps" section of the build instructions?
  3. Can we run initexmf --admin --mklinks to actually have a "working" LaTeX distribution on path after the installation?

Richardk2n commented on 2021-09-22 16:32 (UTC)

@5sdstyrofoam Could you be a little more specific about how it does not work? (Error messages for example?)

« First ‹ Previous 1 2 3 4 Next › Last »