From list+sbo at vahedi.org Sun Mar 1 19:10:59 2026 From: list+sbo at vahedi.org (Shahab Vahedi) Date: Sun, 01 Mar 2026 19:10:59 +0000 Subject: [Slackbuilds-users] Missing "lld" on x86 Slackware-15.0 Message-ID: I need to pick your brain on something. There is this program called Bear that recently moved their code base from C++ to Rust. When building it, I noticed that the build fails on i586 version of Slackware-15.0 [1], but is fine on x86_64 variant. I have narrowed down the problem to missing "lld" binary on x86 Slackware (llvm-13) [2]. Indeed, Slackware64-15.0's llvm package (llvm-13 again) provides the "lld" linker. At first I thought maybe I could get away with having a link from "lld" to "ld", but that was not a success [3]. The linking phase really needs the "lld" tool. I finally managed to have "lld" on x86 Slackware-15.0 by installing llvm-22.1 package from the "extra" repository. That package does provide the "lld" binary. Moreover, I was not in the mood for compiling "llvm-opt", so I did not try that, but I'm going to _assume_ that it also provides the "lld" tool. After having "lld" on the system, the build went just fine. To summarise the situation: 1. Bear builds fine on Slackware64-15.0 because there is lld 2. Bear faild to build on Slackware-15.0 since there's no lld 3. The linking process does really need lld (cannot be bypassed) Now, what should I do with this? - Shall I add "llvm-opt", to the "REQUIRES" field and explain in the README that is only needed for x86 variants? Please keep in mind that I actually haven't tried "llvm-opt" but the pre-built package of llvm-22.1 from the "extra" repository. - Should I create two separate packages (Bear vs Bear32)? I'm not in favour of this option. - Or maybe something else? -Shahab [1] https://github.com/SlackBuildsOrg/slackbuilds/pull/14530#issuecomment-3975967832 [2] the problem manifests itself during the linking phase as note: collect2: fatal error: cannot find 'ld' compilation terminated. what actually is not found is "lld" and not "ld". [3] If "ld" is used instead of "lld", the "ld" will return an error /usr/bin/ld: anonymous version tag cannot be combined with other version tags collect2: error: ld returned 1 exit status From fsleg at t-rg.ws Sun Mar 1 19:33:02 2026 From: fsleg at t-rg.ws (fsLeg) Date: Sun, 01 Mar 2026 22:33:02 +0300 Subject: [Slackbuilds-users] Missing "lld" on x86 Slackware-15.0 In-Reply-To: References: Message-ID: <22844667-6E09-4BA8-A5C3-93AD12D31F80@t-rg.ws> I had a problem with linkers just recently. Some of them I worked around by using a different linker. Slackware 15.0 ships 3 linkers: BFD, LLD and GOLD. ScummVM SlackBuild used a BFD linker for x86 architecture for a while for the same reason. So try other linkers first. Slackware-current no longer has GOLD (binutils deprecated it), but it ships MOLD as the third option. MOLD is on SBo for Slackware 15.0, so you could also try that. I looked up how to change a linker for Rust-based projects, and it seems you just need to supply something like RUSTFLAGS="-C link-arg='-fuse-ld=bfd'" when calling `cargo build`. On March 1, 2026 22:10:59 GMT+03:00, Shahab Vahedi via SlackBuilds-users wrote: >I need to pick your brain on something. There is this program >called Bear that recently moved their code base from C++ to Rust. >When building it, I noticed that the build fails on i586 version >of Slackware-15.0 [1], but is fine on x86_64 variant. > >I have narrowed down the problem to missing "lld" binary on x86 >Slackware (llvm-13) [2]. Indeed, Slackware64-15.0's llvm package >(llvm-13 again) provides the "lld" linker. > >At first I thought maybe I could get away with having a link >from "lld" to "ld", but that was not a success [3]. The linking >phase really needs the "lld" tool. > >I finally managed to have "lld" on x86 Slackware-15.0 by installing >llvm-22.1 package from the "extra" repository. From fourtysixandtwo at sliderr.net Sun Mar 1 19:36:47 2026 From: fourtysixandtwo at sliderr.net (fourtysixandtwo) Date: Sun, 1 Mar 2026 12:36:47 -0700 Subject: [Slackbuilds-users] Missing "lld" on x86 Slackware-15.0 In-Reply-To: References: Message-ID: It's up to you, but I've gone with "i?86) ARCH=i686 ;;" for cargo-vendor-filterer after the i586 issue was reported to me. Support for i586 with rust is not high on their priority list. https://doc.rust-lang.org/rustc/platform-support.html If you do want to have it work, I would note the added dep in the README and maybe an if statement in the slackbuild for that situation. But I believe that there are not many i586 users for rust builds. Cheers On Sun, Mar 1, 2026 at 12:11?PM Shahab Vahedi via SlackBuilds-users wrote: > > I need to pick your brain on something. There is this program > called Bear that recently moved their code base from C++ to Rust. > When building it, I noticed that the build fails on i586 version > of Slackware-15.0 [1], but is fine on x86_64 variant. > > I have narrowed down the problem to missing "lld" binary on x86 > Slackware (llvm-13) [2]. Indeed, Slackware64-15.0's llvm package > (llvm-13 again) provides the "lld" linker. > > At first I thought maybe I could get away with having a link > from "lld" to "ld", but that was not a success [3]. The linking > phase really needs the "lld" tool. > > I finally managed to have "lld" on x86 Slackware-15.0 by installing > llvm-22.1 package from the "extra" repository. That package does > provide the "lld" binary. Moreover, I was not in the mood for > compiling "llvm-opt", so I did not try that, but I'm going to > _assume_ that it also provides the "lld" tool. > > After having "lld" on the system, the build went just fine. > > To summarise the situation: > > 1. Bear builds fine on Slackware64-15.0 because there is lld > 2. Bear faild to build on Slackware-15.0 since there's no lld > 3. The linking process does really need lld (cannot be bypassed) > > Now, what should I do with this? > > - Shall I add "llvm-opt", to the "REQUIRES" field and explain > in the README that is only needed for x86 variants? Please keep > in mind that I actually haven't tried "llvm-opt" but the pre-built > package of llvm-22.1 from the "extra" repository. > > - Should I create two separate packages (Bear vs Bear32)? > I'm not in favour of this option. > > - Or maybe something else? > > > -Shahab > > [1] > https://github.com/SlackBuildsOrg/slackbuilds/pull/14530#issuecomment-3975967832 > > [2] > the problem manifests itself during the linking phase as > note: collect2: fatal error: cannot find 'ld' > compilation terminated. > what actually is not found is "lld" and not "ld". > > [3] > If "ld" is used instead of "lld", the "ld" will return an error > /usr/bin/ld: anonymous version tag cannot be combined with other version tags > collect2: error: ld returned 1 exit status > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > From list+sbo at vahedi.org Sun Mar 1 20:15:15 2026 From: list+sbo at vahedi.org (Shahab Vahedi) Date: Sun, 01 Mar 2026 20:15:15 +0000 Subject: [Slackbuilds-users] Missing "lld" on x86 Slackware-15.0 In-Reply-To: <22844667-6E09-4BA8-A5C3-93AD12D31F80@t-rg.ws> References: <22844667-6E09-4BA8-A5C3-93AD12D31F80@t-rg.ws> Message-ID: First of all, I think this is a (packaging) issue on Slackware side. How come the same package (llvm-13) provides /usr/bin/lld on Slacware64-15.0 but not on Slackware-15.0? If you upgrade it to llvm-21.2, it's there again. That involves prioritising "extra" in your /etc/slackpkg/slackpkg.conf though. > On March 1, 2026, fsLeg wrote: > Slackware 15.0 ships 3 linkers: BFD, LLD and GOLD Stock Slackware-15.0 (x86) does NOT come with LLD. That's my whole issue. If you have it, please check your packages entries to see which one provides it. > So try other linkers first I tried both BFD and GOLD, and they choke on linking phase (different errors). The build must really be done with LLD. > I looked up how to change a linker for Rust-based projects,... > RUSTFLAGS="-C link-arg='-fuse-ld=bfd'" The source code itself is enforcing LLD [1] and all for a good reason (See my previous point): cat intercept-preload/build.rst ... // Force using lld // https://users.rust-lang.org/t/how-to-use-linker-version-scripts-in-rust-1-54 println!("cargo:rustc-cdylib-link-arg=-fuse-ld=lld"); ... [1] https://github.com/rizsotto/Bear/blob/master/intercept-preload/build.rs#L71 > On March 1, fourtysixandtwo wrote: > I've gone with "i?86) ARCH=i686 ;;" for cargo-vendor-filterer after > the i586 issue was reported to me. OK, I'll do it for my SlackBuild as well. > Support for i586 with rust is not high on their priority list. > I believe that there are not many i586 users for rust builds. I think Rust support for i586, i686, and x86 in general in this particular issue (missing "lld" on Slackware-15.0) is irrelevant here. -Shahab From fsleg at t-rg.ws Sun Mar 1 20:32:21 2026 From: fsleg at t-rg.ws (fsLeg) Date: Sun, 1 Mar 2026 23:32:21 +0300 Subject: [Slackbuilds-users] Missing "lld" on x86 Slackware-15.0 In-Reply-To: References: <22844667-6E09-4BA8-A5C3-93AD12D31F80@t-rg.ws> Message-ID: <5a5ee470-4e44-4e87-a0d9-34122e82c921@t-rg.ws> On 3/1/26 23:15, Shahab Vahedi via SlackBuilds-users wrote: > First of all, I think this is a (packaging) issue on > Slackware side. How come the same package (llvm-13) provides > /usr/bin/lld on Slacware64-15.0 but not on Slackware-15.0? > If you upgrade it to llvm-21.2, it's there again. That involves > prioritising "extra" in your /etc/slackpkg/slackpkg.conf though. Well, the missing LLD in 32 bit Slackware is something so be brought up on LQ, not here. Maybe Pat will see it and rebuild llvm-13 to include LLD. Or maybe LLD from llvm-13 just doesn't build on 32 bit Slackware. > I think Rust support for i586, i686, and x86 in general in this > particular issue (missing "lld" on Slackware-15.0) is irrelevant > here. There's always an option of marking x86 as unsupported. There's plenty of scripts on SBo that require Slackware64 and barely anyone runs 32 bit systems anymore. I had to mark PrismLauncher as 64 bit only even though there's nothing preventing it from compiling on a 32 bit system, it's just that SBo only has a 64 bit version of its main dependency, qt6, despite it being possible to have qt6 on a 32 bit system, Slackware-current is a proof of that. From list+sbo at vahedi.org Sun Mar 1 20:48:24 2026 From: list+sbo at vahedi.org (Shahab Vahedi) Date: Sun, 01 Mar 2026 20:48:24 +0000 Subject: [Slackbuilds-users] Missing "lld" on x86 Slackware-15.0 In-Reply-To: <5a5ee470-4e44-4e87-a0d9-34122e82c921@t-rg.ws> References: <22844667-6E09-4BA8-A5C3-93AD12D31F80@t-rg.ws> <5a5ee470-4e44-4e87-a0d9-34122e82c921@t-rg.ws> Message-ID: <61acc4fcdb75f5e60553596465a5f6b276f15c56@vahedi.org> On 1-Mar-2026, fsLeg wrote: > Well, the missing LLD in 32 bit Slackware is something so be brought up on LQ, not here. Maybe Pat will see it and rebuild llvm-13 to include LLD. Or maybe LLD from llvm-13 just doesn't build on 32 bit Slackware. If I find some time I'll try to raise it on LQ. Thanks for the suggestion! Finally I managed to solve the issue by actually relying on "rust-opt". Luckily, there is an "ld.lld" provided by Rust itself /opt/rust/lib/rustlib/i686-unknown-linux-gnu/bin/gcc-ld/ld.lld In my SlackBuild, I add that to the PATH under "i?86" systems. -Shahab From arnaud.garcia-fernandez at laposte.net Sun Mar 1 22:23:47 2026 From: arnaud.garcia-fernandez at laposte.net (Arnaud) Date: Sun, 01 Mar 2026 22:23:47 +0000 Subject: [Slackbuilds-users] Qt6, slackware32, current, and unsupported stuff Message-ID: <459384F5-26A9-42A2-8965-0166DC96CA76@laposte.net> Hi, I too am facing a question regarding 32bits and unsupported stuff. It concerns dustrac and gargoyle, which both are now relying on qt6. That makes them UNSUPPORTED on slackware 15.0, the 32bits version. However, Slackware-current does ship an i686 version of qt6, making those 2 games perfectly supported in the future of old CPUs. That does bear the question of what I ought to do today, while waiting for current to go stable. - keep older version, as they work ; - make a gargoyle32, and a dustrac32 package stuck in the past ; - update and lie about 32bit being unsupported, since it is currently the case, but won't be in the future ; - ask Patrick for a release ; - call Obi-Wan Kenobi for help. I've done something for focuswriter, creating a focuswriter-qt6 package, keeping focuswriter stuck. That kind of made sense because qt6 is overly painful to build. But most of those solutions are, or will be, painful for package tracking, or not nice for 32bits systems which would loose packages that were ok before. I'm almost ready to make some hybrid SlackBuild, with different download versions for 32 and 64, and a wrong version for the 32bit package, so it always builds. But that'd be a bigger lie... And does anyone know why we can't have qt6 for ix86 on SBo ? - Yth. -- -------------- next part -------------- An HTML attachment was scrubbed... URL: From bencollver at riseup.net Sun Mar 1 22:55:19 2026 From: bencollver at riseup.net (Ben Collver) Date: Sun, 1 Mar 2026 14:55:19 -0800 Subject: [Slackbuilds-users] orphaning office/wink and audio/sfarkxtc Message-ID: <20260301225519.GC1799@rainbow> Greetings, I no longer use office/wink nor audio/sfarkxtc. In fact, i had forgotten they had my name on them. Would someone else like to take over their maintenance? Thank you, -Ben From urchlay at slackware.uk Sun Mar 1 23:02:28 2026 From: urchlay at slackware.uk (B. Watson) Date: Sun, 1 Mar 2026 18:02:28 -0500 (EST) Subject: [Slackbuilds-users] orphaning office/wink and audio/sfarkxtc In-Reply-To: <20260301225519.GC1799@rainbow> References: <20260301225519.GC1799@rainbow> Message-ID: On Sun, 1 Mar 2026, Ben Collver wrote: > I no longer use office/wink nor audio/sfarkxtc. > In fact, i had forgotten they had my name on them. > Would someone else like to take over their maintenance? I'll take sfarkxtc. I've used it in the past, might need it again someday. From willysr at slackbuilds.org Mon Mar 2 04:58:39 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 2 Mar 2026 11:58:39 +0700 Subject: [Slackbuilds-users] Qt6, slackware32, current, and unsupported stuff In-Reply-To: <459384F5-26A9-42A2-8965-0166DC96CA76@laposte.net> References: <459384F5-26A9-42A2-8965-0166DC96CA76@laposte.net> Message-ID: <20260302115839.2de6c124@office64.slackie.org> >And does anyone know why we can't have qt6 for ix86 on SBo ? If anyone can send a PR for me to test for i586 build on Qt6, feel free to do so :) -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 870 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Mon Mar 2 06:47:30 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 2 Mar 2026 13:47:30 +0700 Subject: [Slackbuilds-users] Missing "lld" on x86 Slackware-15.0 In-Reply-To: <61acc4fcdb75f5e60553596465a5f6b276f15c56@vahedi.org> References: <22844667-6E09-4BA8-A5C3-93AD12D31F80@t-rg.ws> <5a5ee470-4e44-4e87-a0d9-34122e82c921@t-rg.ws> <61acc4fcdb75f5e60553596465a5f6b276f15c56@vahedi.org> Message-ID: <20260302134730.2f656f20@office64.slackie.org> >Finally I managed to solve the issue by actually relying on "rust-opt". >Luckily, there is an "ld.lld" provided by Rust itself > > /opt/rust/lib/rustlib/i686-unknown-linux-gnu/bin/gcc-ld/ld.lld > >In my SlackBuild, I add that to the PATH under "i?86" systems. Unfortunately, it doesn't work with BEAR on i586 https://github.com/SlackBuildsOrg/slackbuilds/pull/14585 -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 870 bytes Desc: OpenPGP digital signature URL: From dchmelik at gmail.com Mon Mar 2 07:59:38 2026 From: dchmelik at gmail.com (David Chmelik) Date: Sun, 1 Mar 2026 23:59:38 -0800 Subject: [Slackbuilds-users] orphaned academic, games (mathics, tome-sx) builds In-Reply-To: References: Message-ID: <26e6e8b2-29a3-f2a4-01fa-c74a1a8158b8@gmail.com> orphaned (uploaded those changes including abridging game GitHub URL): * academic/mathics * games/tome-sx available possibly (if anyone can handle the changes: * games/crawl * games/tome-ah * libraries/grx The grx library should be replaced by mgrx because now is completely different, and mgrx continues what the original is for... nothing depends on these; just wanted to make available a general graphics programming library to install safer. From dguptill at accesswave.ca Fri Mar 6 04:17:00 2026 From: dguptill at accesswave.ca (Douglas Guptill) Date: Fri, 6 Mar 2026 00:17:00 -0400 Subject: [Slackbuilds-users] pdfstudioviewer 2024.0.1 : typo in slackbuild script? Message-ID: Hello: I was looking for something to edit a fillable pdf file, and came across pdfstudioviwer. Downloaded the SBo and tried it. The build output included ..... opt/pdfstudioviewer2024/updater chmod: cannot operate on dangling symlink './usr/bin/pdfstudioviewer' [Note: this part of the build was not running as user root. My SlackBuilds are split into 2 parts; everything up to makepkg, which runs as a normal user, and the makepkg, which runs as root. ] which I concluded came from line 67 in the SlackBuild script ln -s /opt/$PRGNAM$YEAR/$PRGNAM$YEAR $PKG/usr/bin/$PRGNAM So I inserted a "$PKG" in that line ln -s $PKG/opt/$PRGNAM$YEAR/$PRGNAM$YEAR $PKG/usr/bin/$PRGNAM and all went well. I now have a working pdfstudioviewer. Is there anything further I can do to help? Regards, Douglas. -- Bold character derived from stubborn patience and adversity. == Douglas Guptill, B.Sc., CCP, M.Comp.Sci., THB From willysr at slackbuilds.org Fri Mar 6 05:17:54 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 6 Mar 2026 12:17:54 +0700 Subject: [Slackbuilds-users] pdfstudioviewer 2024.0.1 : typo in slackbuild script? In-Reply-To: References: Message-ID: <20260306121754.5bcacfce@office64.slackie.org> >The build output included > > ..... > opt/pdfstudioviewer2024/updater > chmod: cannot operate on dangling symlink './usr/bin/pdfstudioviewer' > > [Note: this part of the build was not running as user root. > My SlackBuilds are split into 2 parts; everything up to makepkg, > which runs as a normal user, and the makepkg, which runs as root. > ] > >which I concluded came from line 67 in the SlackBuild script > > ln -s /opt/$PRGNAM$YEAR/$PRGNAM$YEAR $PKG/usr/bin/$PRGNAM > >So I inserted a "$PKG" in that line > > ln -s $PKG/opt/$PRGNAM$YEAR/$PRGNAM$YEAR $PKG/usr/bin/$PRGNAM > >and all went well. I now have a working pdfstudioviewer. > >Is there anything further I can do to help? The code is correct in the first place if you put $PKG in the first part of ln, it will have a link to temporary build directory instead of coming from root directory when you install the package. You can try to remove the /tmp/SBo directory and see if you have a broken link on /usr/bin/ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 870 bytes Desc: OpenPGP digital signature URL: From zhu.qunying at gmail.com Fri Mar 6 05:35:24 2026 From: zhu.qunying at gmail.com (Qun-Ying) Date: Thu, 5 Mar 2026 21:35:24 -0800 Subject: [Slackbuilds-users] Please remove PortfolioPerformance-bin Message-ID: Hi, Please remove "PortfolioPerformance-bin", there is a typo in the build script. I would submit another one. -- Qun-Ying -------------- next part -------------- An HTML attachment was scrubbed... URL: From dguptill at accesswave.ca Fri Mar 6 05:45:03 2026 From: dguptill at accesswave.ca (Douglas Guptill) Date: Fri, 6 Mar 2026 01:45:03 -0400 Subject: [Slackbuilds-users] pdfstudioviewer 2024.0.1 : typo in slackbuild script? In-Reply-To: <20260306121754.5bcacfce@office64.slackie.org> References: <20260306121754.5bcacfce@office64.slackie.org> Message-ID: Hello: On Fri, Mar 06, 2026 at 12:17:54PM +0700, Willy Sudiarto Raharjo wrote: > >The build output included > > > > ..... > > opt/pdfstudioviewer2024/updater > > chmod: cannot operate on dangling symlink './usr/bin/pdfstudioviewer' > > > > [Note: this part of the build was not running as user root. > > My SlackBuilds are split into 2 parts; everything up to makepkg, > > which runs as a normal user, and the makepkg, which runs as root. > > ] > > > >which I concluded came from line 67 in the SlackBuild script > > > > ln -s /opt/$PRGNAM$YEAR/$PRGNAM$YEAR $PKG/usr/bin/$PRGNAM > > > >So I inserted a "$PKG" in that line > > > > ln -s $PKG/opt/$PRGNAM$YEAR/$PRGNAM$YEAR $PKG/usr/bin/$PRGNAM > > > >and all went well. I now have a working pdfstudioviewer. > > > >Is there anything further I can do to help? > > > The code is correct in the first place > if you put $PKG in the first part of ln, it will have a link to > temporary build directory instead of coming from root directory when > you install the package. > > You can try to remove the /tmp/SBo directory and see if you have a > broken link on /usr/bin/ You are correct. bash-5.1$ ls -l /usr/bin/pdfstudioviewer lrwxrwxrwx 1 root root 85 Mar 5 00:25 /usr/bin/pdfstudioviewer -> /tmp/SBo/package-pdfstudioviewer-2024.0.1/opt/pdfstudioviewer2024/pdfstudioviewer2024 Thank you for the correction. Sorry for the noise, and for my incorrect suggestion of a mistake in the SlackBuild script. Regards, Douglas. -- Bold character derived from stubborn patience and adversity. == Douglas Guptill, B.Sc., CCP, M.Comp.Sci., THB From dguptill at accesswave.ca Fri Mar 6 12:15:17 2026 From: dguptill at accesswave.ca (Douglas Guptill) Date: Fri, 6 Mar 2026 08:15:17 -0400 Subject: [Slackbuilds-users] pdfstudioviewer 2024.0.1 : typo in slackbuild script? In-Reply-To: References: <20260306121754.5bcacfce@office64.slackie.org> Message-ID: Hello again, another thought about the SlackBuild for pdfstudioviewer: On Fri, Mar 06, 2026 at 01:45:03AM -0400, Douglas Guptill wrote: > Hello: > > On Fri, Mar 06, 2026 at 12:17:54PM +0700, Willy Sudiarto Raharjo wrote: > > >The build output included > > > > > > ..... > > > opt/pdfstudioviewer2024/updater > > > chmod: cannot operate on dangling symlink './usr/bin/pdfstudioviewer' > > > > > > [Note: this part of the build was not running as user root. > > > My SlackBuilds are split into 2 parts; everything up to makepkg, > > > which runs as a normal user, and the makepkg, which runs as root. > > > ] > > > > > >which I concluded came from line 67 in the SlackBuild script > > > > > > ln -s /opt/$PRGNAM$YEAR/$PRGNAM$YEAR $PKG/usr/bin/$PRGNAM > > > > > >So I inserted a "$PKG" in that line > > > > > > ln -s $PKG/opt/$PRGNAM$YEAR/$PRGNAM$YEAR $PKG/usr/bin/$PRGNAM > > > > > >and all went well. I now have a working pdfstudioviewer. > > > > > >Is there anything further I can do to help? > > > > > > The code is correct in the first place > > if you put $PKG in the first part of ln, it will have a link to > > temporary build directory instead of coming from root directory when > > you install the package. > > > > You can try to remove the /tmp/SBo directory and see if you have a > > broken link on /usr/bin/ > > You are correct. > > bash-5.1$ ls -l /usr/bin/pdfstudioviewer > lrwxrwxrwx 1 root root 85 Mar 5 00:25 /usr/bin/pdfstudioviewer -> /tmp/SBo/package-pdfstudioviewer-2024.0.1/opt/pdfstudioviewer2024/pdfstudioviewer2024 > > Thank you for the correction. > > Sorry for the noise, and for my incorrect suggestion of a mistake in > the SlackBuild script. If the philosophy behind slackbuilds is to install into $PKG, then hand $PKG to makepkg (which makes the package), and then hand the package to installpkg (which does the actual install), then an alternate approach to the current slackbuild might be: 1) remove line 67 2) put a similar line in doinst.sh ln -sf /opt/pdfstudioviewer2024/pdfstudioviewer2024 /usr/bin/pdfstudioviewer2024 My understanding is that the current SlackBuild installs a file in /opt during the package build phase. Even if the package is never installed. Unless I _really_ don't understand what is going on... Regards, Douglas. -- Bold character derived from stubborn patience and adversity. == Douglas Guptill, B.Sc., CCP, M.Comp.Sci., THB From fsleg at t-rg.ws Fri Mar 6 12:25:12 2026 From: fsleg at t-rg.ws (fsLeg) Date: Fri, 06 Mar 2026 15:25:12 +0300 Subject: [Slackbuilds-users] pdfstudioviewer 2024.0.1 : typo in slackbuild script? In-Reply-To: References: <20260306121754.5bcacfce@office64.slackie.org> Message-ID: makepkg already removes all symlinks and appends their creation into doinst.sh. If you use `makepkg -l y` that is, which is default for vanilla SBo SlackBuilds. Try reading `man makepkg`. Also read `man ln`. The actual link which is put somewhere is the second argument, the path is the first one, and path doesn't have to exist in case of symlinks. So you can create a symlink that points to a location that doesn't currently exist but you know will exist later. Another option is to use a relative path instead of an absolute one, although the same applies here too. On March 6, 2026 15:15:17 GMT+03:00, Douglas Guptill wrote: >If the philosophy behind slackbuilds is to install into $PKG, then >hand $PKG to makepkg (which makes the package), and then hand the >package to installpkg (which does the actual install), then an >alternate approach to the current slackbuild might be: > > 1) remove line 67 > 2) put a similar line in doinst.sh > ln -sf /opt/pdfstudioviewer2024/pdfstudioviewer2024 /usr/bin/pdfstudioviewer2024 > >My understanding is that the current SlackBuild installs a file in >/opt during the package build phase. Even if the package is never >installed. > >Unless I _really_ don't understand what is going on... > >Regards, >Douglas. From j+sbo-users at maschinengott.de Fri Mar 6 17:47:48 2026 From: j+sbo-users at maschinengott.de (j12i) Date: Fri, 6 Mar 2026 18:47:48 +0100 Subject: [Slackbuilds-users] upcoming deno 2.7.2 Message-ID: fourtysixandtwo asked on LQ: > Just pushed an update to my branch for deno-2.7.2. Builds fine on current here, but would appreciate further testing. > https://git.slackbuilds.org/slackbuilds/patch/?id=8db38df450567d5a04221ae24b316f75264580ca This deno build works fine for me on -current, but on 15.0 I get error messages like the attached (at runtime) and don't get the benefit that deno brings for yt-dlp. This is with urchlay's 'yt-dlp-bin' SBo, upgraded to 2026.03.03. (I also built rust-opt and deno in a 15.0 LXC container on my -current machine, for on my 15.0 machine it would take hours. But I don't think that should matter.) -------------- next part -------------- [youtube] [jsc:deno] Solving JS challenges using deno WARNING: [youtube] [jsc] Error solving 2 challenge requests using "deno" provider: Error running deno process (returncode: 1): error: Uncaught (in promise) "found 0 n function possibilities". requests = [JsChallengeRequest(type=, input=NChallengeInput(player_url='https://www.youtube.com/s/player/6c5cb4f4/tv-player-ias.vflset/tv-player-ias.js', challenges=['F5ybDdMdId_aF98p', 'yQ4K07wXS3PsZD5m', '7SQOIEhMhu9L0o8u']), video_id='dmVAmlpbnD4'), JsChallengeRequest(type=, input=SigChallengeInput(player_url='https://www.youtube.com/s/player/6c5cb4f4/tv-player-ias.vflset/tv-player-ias.js', challenges=['\x00\x01\x02\x03\x04\x05\x06\x07\x08\t\n\x0b\x0c\r\x0e\x0f\x10\x11\x12\x13\x14\x15\x16\x17\x18\x19\ x1a\x1b\x1c\x1d\x1e\x1f !"#$%&\'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\\]^_`abcdefghij', '\x00\x01\x02\x03\x04\x05\x06\x07\x08\t\n\x0b\x0c\r\x0e\x0f\x10\x11\x12\x13\x14\x15\x16\x17\x18\x19\ x1a\x1b\x1c\x1d\x1e\x1f !"#$%&\'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\\]^_`abcdef']), video_id='dmVAmlpbnD4')] Please report this issue on https://github.com/yt-dlp/yt-dlp/issues?q= , filling out the appropriate issue template. Confirm you are on the latest version using yt-dlp -U WARNING: [youtube] dmVAmlpbnD4: Signature solving failed: Some formats may be missing. Ensure you have a supported JavaScript runtime and challenge solver script distribution installed. Review any warnings presented before this message. For more details, refer to https://github.com/yt-dlp/yt-dlp/wiki/EJS WARNING: [youtube] dmVAmlpbnD4: n challenge solving failed: Some formats may be missing. Ensure you have a supported JavaScript runtime and challenge solver script distribution installed. Review any warnings presented before this message. For more details, refer to https://github.com/yt-dlp/yt-dlp/wiki/EJS From fourtysixandtwo at sliderr.net Fri Mar 6 20:10:34 2026 From: fourtysixandtwo at sliderr.net (fourtysixandtwo) Date: Fri, 6 Mar 2026 13:10:34 -0700 Subject: [Slackbuilds-users] upcoming deno 2.7.2 In-Reply-To: References: Message-ID: I noticed that when I was testing deno-2.7.4 yesterday. Urchlay also updated yt-dlp-bin to 2026.03.03 for the fix after I let him know. You'll see both in our branches here https://git.slackbuilds.org/slackbuilds/ Cheers On Fri, Mar 6, 2026 at 10:48?AM j12i wrote: > > fourtysixandtwo asked on LQ: > > Just pushed an update to my branch for deno-2.7.2. Builds fine on > current here, but would appreciate further testing. > > > https://git.slackbuilds.org/slackbuilds/patch/?id=8db38df450567d5a04221ae24b316f75264580ca > > This deno build works fine for me on -current, but on 15.0 I get error > messages like the attached (at runtime) and don't get the benefit that > deno brings for yt-dlp. > > This is with urchlay's 'yt-dlp-bin' SBo, upgraded to 2026.03.03. > > (I also built rust-opt and deno in a 15.0 LXC container on my -current > machine, for on my 15.0 machine it would take hours. But I don't think > that should matter.)_______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > From j+sbo-users at maschinengott.de Fri Mar 6 22:01:48 2026 From: j+sbo-users at maschinengott.de (j+sbo-users at maschinengott.de) Date: Fri, 6 Mar 2026 23:01:48 +0100 Subject: [Slackbuilds-users] upcoming deno 2.7.2 In-Reply-To: References: Message-ID: <3dd84603-a161-49b6-928b-3cf56667ccef@maschinengott.de> Huh! I thought I was already using yt-dlp-bin-2026.03.03 but I wasn't. I had built, but not installed it. All working well now! Am 06.03.26 um 21:10 schrieb fourtysixandtwo: > I noticed that when I was testing deno-2.7.4 yesterday. Urchlay also > updated yt-dlp-bin to 2026.03.03 for the fix after I let him know. > > You'll see both in our branches here https://git.slackbuilds.org/slackbuilds/ > > Cheers > > On Fri, Mar 6, 2026 at 10:48?AM j12i wrote: >> >> fourtysixandtwo asked on LQ: >> > Just pushed an update to my branch for deno-2.7.2. Builds fine on >> current here, but would appreciate further testing. >> > >> https://git.slackbuilds.org/slackbuilds/patch/?id=8db38df450567d5a04221ae24b316f75264580ca >> >> This deno build works fine for me on -current, but on 15.0 I get error >> messages like the attached (at runtime) and don't get the benefit that >> deno brings for yt-dlp. >> >> This is with urchlay's 'yt-dlp-bin' SBo, upgraded to 2026.03.03. >> >> (I also built rust-opt and deno in a 15.0 LXC container on my -current >> machine, for on my 15.0 machine it would take hours. But I don't think >> that should matter.)_______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - https://slackbuilds.org/faq/ >> > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > From j+sbo-users at maschinengott.de Fri Mar 6 22:03:42 2026 From: j+sbo-users at maschinengott.de (j+sbo-users at maschinengott.de) Date: Fri, 6 Mar 2026 23:03:42 +0100 Subject: [Slackbuilds-users] upcoming deno 2.7.2 In-Reply-To: <3dd84603-a161-49b6-928b-3cf56667ccef@maschinengott.de> References: <3dd84603-a161-49b6-928b-3cf56667ccef@maschinengott.de> Message-ID: <38f9999c-68bb-4476-a39a-d3d9697f95ef@maschinengott.de> addendum: with deno 2.7.4 From willysr at slackbuilds.org Sat Mar 7 05:48:57 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 7 Mar 2026 12:48:57 +0700 Subject: [Slackbuilds-users] Updates : 20260307.1 Message-ID: <20260307124857.66f4e0f1@home.slackie.org> Sat Mar 7 05:28:39 UTC 2026 academic/booktab: Added (Textbook Media Manager). academic/cdo: Updated for version 2.6.0. academic/gpredict: updated for version 2.4 academic/mathics: Orphaned. academic/ncview: Fix compilation with latest netcdf academic/x48ng: Removed unneeded script audio/coppwr: Updated for version 1.7.1, new maintainer. audio/reaper: Updated for version 7.62 audio/sfarkxtc: Updated for version 20181208, new maintainer. desktop/SiriKali: Updated for version 1.8.6. desktop/awf: Updated for version 4.0.0. desktop/human-gtk-theme: Updated for version 3.0.0. desktop/qtile: Update README (change info on wlroots version requirement) desktop/yad: Updated for version 14.2. development/Bear: Updated for version 4.0.3. development/MinForth: Fixed script development/SQLAlchemy: Updated for version 2.0.48. development/SmallBASIC: Updated for version 12.33 development/a68g: Updated for version 3.10.11 development/antigravity: Updated for version 1.20.3 development/aws-cdk: Updated for version 2.1109.0. development/cursor: Updated for version 2.5.26 development/deno: Updated for version 2.7.4. development/diffoscope: updated for version 313 development/electron-bin: Updated for version 40.7.0 development/jujutsu: Updated for version 0.39.0 development/kForth-64: Fix script development/mrustc: Updated for version 0.12.0. development/nodejs22: Updated for version 22.22.1. development/notepadqq: Removed unneeded patch development/obsidian: updated for version 1.12.4 development/poedit: Updated for version 3.8.2. development/qb64: Removed unneeded script development/sbcl: Updated for version 2.6.2 development/sbt: Updated for version 1.12.5 development/sourcegit: Updated for version 2026.05 development/terraform: Updated for version 1.14.6 development/tracy: updated for version 0.13.1 development/vscode-bin: Updated for version 1.110.0. development/zope.interface: updated for version 8.2 development/zope.sqlalchemy: updated for version 4.1 development/zope.testing: updated for version 6.1 development/zxbasic: Updated for version 1.18.7 development/zxtext2p: Fixed script games/ags: updated for version 3.6.2.16 games/dustrac: updated for version 2.2.0 games/endless-sky: updated for version 0.11.0 games/fheroes2: Updated for version 1.1.14. games/freeciv: updated for version 3.2.3 games/gargoyle: updated for version 2026.1.1 games/mame: Updated for version 0.286. games/ppsspp: Updated for version 1.20.1. games/scummvm: Removed gold linker games/shattered-pixel-dungeon: Updated for version 3.3.7. games/space-invaders: Updated for version 1.4 games/tome-sx: Orphaned. gis/proj: Updated for version 9.8.0. graphics/converseen: Updated for version 0.15.2.1. graphics/graphviz: updated for version 14.1.2 ham/hackrf: Updated for version 2026.01.3. libraries/LucenePlusPlus: Use git source. libraries/allegro: updated for version 5.2.11.3 libraries/libaec: Updated for version 1.1.6. libraries/libjodycode: updated for version 4.1.2 libraries/libvirt-python: Updated for version 11.10.0 libraries/libvirt: Updated for version 11.10.0 libraries/python3-pymdstat: Updated for version 0.5.1. libraries/webkit2gtk4.1: Fix build. libraries/wxWidgets: Updated for version 3.2.10. libraries/zlib-ng: updated for version 2.3.3 libraries/zope.component: updated for version 7.1 libraries/zope.hookable: updated for version 8.2 libraries/zope.i18nmessageid: updated for version 8.2 libraries/zope.proxy: updated for version 7.1 libraries/zope.security: updated for version 8.3 library/netcdf: Updated for version 4.10.0. misc/SecLists: Added (Pentesting Tools). misc/ollama: Updated for version 0.17.6. misc/simh-classic: Removed unneeded patch misc/tinytldr: Fix script misc/yubioath-desktop: Updated for version 7.3.2. multimedia/iptvnator: Updated for version 0.19.0. network/AdGuardHome: Updated for version 0.107.72. network/abdownloadmanager-bin: Updated for version 1.8.7 network/brave-browser: update 1.87.191 network/copyparty: updated for version 1.20.10 network/dnsproxy-bin: Updated for version 0.79.0. network/dropbox: Updated for version 243.4.6956. network/easyrsa: Updated for version 3.2.5. network/element-desktop: Updated for version 1.12.11. network/gobuster: Added (Brute Force Tool). network/neomutt: Update script. network/ngrok: Fix MD5SUM. network/ocserv: Updated for version 1.4.1. network/opera: Updated for version 128.0.5807.37 network/rclone-src: Added (Cloud Storage). network/rustdesk: Updated for version 1.4.6. network/signal-desktop: Updated for version 8.1.0. network/syncthingtray-bin: Updated for version 2.0.8. network/teams-for-linux: Updated for version 2.7.9. network/teamviewer: Updated for version 15.75.4. network/telegram: Updated for version 6.6.2. network/vivaldi: Updated for version 7.8.3925.76. network/yt-dlp-bin: Updated for version 2026.03.03. network/zeek: Updated for version 8.0.6. network/zen-browser: Updated for version 1.19b office/abiword: Updated for version 3.0.8. office/grisbi: updated for version 3.90.1 office/ledger-live: Updated for version 2.143.0 office/miktex: Updated for version 26.2. office/onlyoffice-desktopeditors: Updated for version 9.3.1 office/qownnotes: Updated for version 26.3.4. office/smoffice2021: Fixed SBo tools complaints office/wps-office-dicts: Updated for version 26.2.2.1 perl/perl-Date-Manip: Updated for version 6.99. perl/perl-Mail-DMARC: Updated for version 1.20260301. perl/perl-Module-Build-Tiny: Updated for version 0.053. python/Flask: Updated for version 3.1.3. python/python2-nuitka: Updated for version 4.0.2 python/python2-prefixed: Fixed script python/python3-BTrees: updated for version 6.3 python/python3-ZConfig: updated for version 4.3 python/python3-ZODB: updated for version 6.2 python/python3-alembic: updated for version 1.17.2 python/python3-atpublic: updated for version 7.0.0 python/python3-autobahn: updated for version 25.12.2 python/python3-babel: updated for version 2.18.0 python/python3-billiard: updated for version 4.2.4 python/python3-cattrs: Last py3.9 ver. python/python3-celery: updated for version 5.6.2 python/python3-cookiecutter: Update README python/python3-dotenv: Last py3.9 ver. python/python3-flufl.i18n: updated for version 6.0.0 python/python3-flufl.lock: updated for version 9.0.0 python/python3-incremental: updated for version 24.11.0 python/python3-kombu: updated for version 5.6.2 python/python3-maturin: Updated for version 1.12.6. python/python3-nuitka: Updated for version 4.0.2 python/python3-odfdo: Updated for version 3.21.0 python/python3-parso: updated for version 0.8.6 python/python3-persistent: updated for version 6.5 python/python3-prefixed: Fixed script python/python3-prompt_toolkit: Changed deps. python/python3-pyasn1: updated for version 0.6.2 python/python3-pyjwt: updated for version 2.11.0 python/python3-pypdf: Updated for version 6.7.5 python/python3-pyproject-metadata: Updated for version 0.11.0. python/python3-regex: Update for 2026.1.15 python/python3-rich: Updated for version 14.3.3. python/python3-smart_open: Update README python/python3-txaio: updated for version 25.12.2 python/python3-typeguard: Updated for version 4.5.1. python/python3-wcwidth: updated for version 0.6.0 python/python3-xcffib: Update for 1.12.0 python/python3-zodbpickle: updated for version 4.3 python/werkzeug: Updated for version 3.1.6. ruby/ruby-build: Updated for version 20260222. system/Iosevka-aile: Updated for version 34.2.1. system/Iosevka-core: update to 34.2.1 system/Iosevka-etoile: Updated for version 34.2.1. system/Iosevka-slab: Updated for version 34.2.1 system/Iosevka: Updated for version 34.2.1 system/apparmor: Updated for version 4.1.6. system/catatonit: Fixed script system/clamav: Updated for version 1.5.2. system/dosbox-x: updated for version 2026.01.02 system/fonts-atkinson-hyperlegible: Added (Sans-serif typeface). system/incus-ui: Updated for version 20260226_944b3601 system/incus: Updated for version 6.22 system/kyotocabinet: Updated for version 1.2.80. system/limine: Updated for version 10.8.2 system/lxqt-config: Update for 2.3.1 system/mbuffer: updated for version 20260221 system/nemo-fileroller: Update for 6.6.0 system/nemo: Update for 6.6.4 system/openzfs: updated for version 2.4.1 system/passwdqc: Updated for version 2.1.0. system/pax: Update script. system/pgbadger: updated for version 13.2 system/postgresql15: Updated for version 15.17. system/postgresql16: Updated for version 16.13. system/postgresql17: Updated for version 17.9. system/postgresql18: Updated for version 18.3. system/postgresql: Updated for version 14.22. system/pv: updated for version 1.10.3 system/redis-py: updated for version 7.2.1 system/redis: updated for version 8.6.1 system/slpkg: Updated for version 6.0.0. system/ttf-charis-sil: Updated for version 7.000. system/valkey: updated for version 9.0.3 system/winetricks: updated for version 20260125 system/xfile: Updated for version 1.0.3. system/yash: Updated for version 2.61. +--------------------------+ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 870 bytes Desc: OpenPGP digital signature URL: From duncan_roe at optusnet.com.au Sun Mar 8 03:10:43 2026 From: duncan_roe at optusnet.com.au (Duncan Roe) Date: Sun, 8 Mar 2026 14:10:43 +1100 Subject: [Slackbuilds-users] FW: Please add virtiofsd as a virt-manager optional dep Message-ID: (forgot to cc: list - D) ----- Forwarded message from Duncan Roe ----- Date: Tue, 3 Mar 2026 19:59:22 +1100 From: Duncan Roe To: rworkman at slackbuilds.org Subject: Please add virtiofsd as a virt-manager optional dep Hi Robby, "Add Hardware" now offers "Filesystem" for the guest to access host filesystems. Two transports are offered: virtiofs and virtio-9p. The latter is older and slower. virtiofsd is now in SlackBuilds. I use it with hardware drives and NFS mounts so far. Also I'm the maintainer. Please consider adding virtiofsd as an optional dependency of virt-manager, Cheers ... Duncan. ----- End forwarded message ----- From 1.41421 at gmail.com Sun Mar 8 16:44:33 2026 From: 1.41421 at gmail.com (Luveh Keraph) Date: Sun, 8 Mar 2026 10:44:33 -0600 Subject: [Slackbuilds-users] mkvtoolnix problem Message-ID: I have had mkvtoolnix running for some time. All of a sudden, I am getting the following: $ mkvtoolnix-gui mkvtoolnix-gui: error while loading shared libraries: libcmark.so.0.31.1: cannot open shared object file: No such file or directory libcmark.so is part of the cmark-0.31.2 package, which I updated on 21st February. So, I removed mkvtoolnix and tried to build it again. Alas, it won't: CXX src/mkvtoolnix-gui/util/json_config_file.cpp CXX src/mkvtoolnix-gui/util/kax_analyzer.cpp CXX src/mkvtoolnix-gui/util/kax_info.cpp CXX src/mkvtoolnix-gui/util/language_combo_box.cpp CXX src/mkvtoolnix-gui/util/serial_worker_queue.cpp CXX src/mkvtoolnix-gui/util/language_dialog.cpp CXX src/mkvtoolnix-gui/util/language_display_widget.cpp CXX src/mkvtoolnix-gui/util/media_player.cpp CXX src/mkvtoolnix-gui/util/message_box.cpp src/mkvtoolnix-gui/util/media_player.cpp: In member function ?void mtx::gui::Util::MediaPlayer::handleError(QMediaPlayer::Error)?: src/mkvtoolnix-gui/util/media_player.cpp:76:9: error: invalid use of incomplete type ?class QDebug? 76 | qDebug() << "MediaPlayer::handleError" << error << p.errorReported; compilation terminated due to -Wfatal-errors. CXX src/mkvtoolnix-gui/util/model.cpp CXX src/mkvtoolnix-gui/util/modify_tracks_submenu.cpp CXX src/mkvtoolnix-gui/util/recently_used_strings.cpp CXX src/mkvtoolnix-gui/util/network_access_manager.cpp CXX src/mkvtoolnix-gui/util/option_file.cpp CXX src/mkvtoolnix-gui/util/process.cpp CXX src/mkvtoolnix-gui/util/qgs_collapsible_group_box.cpp Any pointers on how to fix this would be much appreciated. -------------- next part -------------- An HTML attachment was scrubbed... URL: From matteo.bernardini at gmail.com Sun Mar 8 16:51:27 2026 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Sun, 8 Mar 2026 17:51:27 +0100 Subject: [Slackbuilds-users] mkvtoolnix problem In-Reply-To: References: Message-ID: which version of mkvtoolnix are you trying to build? are you on stable or on current? Matteo Il giorno dom 8 mar 2026 alle ore 17:44 Luveh Keraph <1.41421 at gmail.com> ha scritto: > I have had mkvtoolnix running for some time. All of a sudden, I am getting > the following: > > $ mkvtoolnix-gui > mkvtoolnix-gui: error while loading shared libraries: libcmark.so.0.31.1: > cannot open shared object file: No such file or directory > > libcmark.so is part of the cmark-0.31.2 package, which I updated on 21st > February. So, I removed mkvtoolnix and tried to build it again. Alas, it > won't: > > CXX src/mkvtoolnix-gui/util/json_config_file.cpp > CXX src/mkvtoolnix-gui/util/kax_analyzer.cpp > CXX src/mkvtoolnix-gui/util/kax_info.cpp > CXX src/mkvtoolnix-gui/util/language_combo_box.cpp > CXX src/mkvtoolnix-gui/util/serial_worker_queue.cpp > CXX src/mkvtoolnix-gui/util/language_dialog.cpp > CXX src/mkvtoolnix-gui/util/language_display_widget.cpp > CXX src/mkvtoolnix-gui/util/media_player.cpp > CXX src/mkvtoolnix-gui/util/message_box.cpp > src/mkvtoolnix-gui/util/media_player.cpp: In member function ?void > mtx::gui::Util::MediaPlayer::handleError(QMediaPlayer::Error)?: > src/mkvtoolnix-gui/util/media_player.cpp:76:9: error: invalid use of > incomplete type ?class QDebug? > 76 | qDebug() << "MediaPlayer::handleError" << error << > p.errorReported; > compilation terminated due to -Wfatal-errors. > CXX src/mkvtoolnix-gui/util/model.cpp > CXX src/mkvtoolnix-gui/util/modify_tracks_submenu.cpp > CXX src/mkvtoolnix-gui/util/recently_used_strings.cpp > CXX src/mkvtoolnix-gui/util/network_access_manager.cpp > CXX src/mkvtoolnix-gui/util/option_file.cpp > CXX src/mkvtoolnix-gui/util/process.cpp > CXX src/mkvtoolnix-gui/util/qgs_collapsible_group_box.cpp > > Any pointers on how to fix this would be much appreciated. > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From 1.41421 at gmail.com Sun Mar 8 17:00:40 2026 From: 1.41421 at gmail.com (Luveh Keraph) Date: Sun, 8 Mar 2026 11:00:40 -0600 Subject: [Slackbuilds-users] mkvtoolnix problem In-Reply-To: References: Message-ID: This is for 15.0. I downloaded the mkvtoolnix.tar.gz and mkvtoolnix-80.0.tar.xz tarballs from the Slackbuilds page for mkvtoolnix, tried to build, and this is what I am getting. My 15.0 system is up to date on patches. On Sun, Mar 8, 2026 at 10:51?AM Matteo Bernardini < matteo.bernardini at gmail.com> wrote: > which version of mkvtoolnix are you trying to build? > are you on stable or on current? > > Matteo > > > Il giorno dom 8 mar 2026 alle ore 17:44 Luveh Keraph <1.41421 at gmail.com> > ha scritto: > >> I have had mkvtoolnix running for some time. All of a sudden, I am >> getting the following: >> >> $ mkvtoolnix-gui >> mkvtoolnix-gui: error while loading shared libraries: libcmark.so.0.31.1: >> cannot open shared object file: No such file or directory >> >> libcmark.so is part of the cmark-0.31.2 package, which I updated on 21st >> February. So, I removed mkvtoolnix and tried to build it again. Alas, it >> won't: >> >> CXX src/mkvtoolnix-gui/util/json_config_file.cpp >> CXX src/mkvtoolnix-gui/util/kax_analyzer.cpp >> CXX src/mkvtoolnix-gui/util/kax_info.cpp >> CXX src/mkvtoolnix-gui/util/language_combo_box.cpp >> CXX src/mkvtoolnix-gui/util/serial_worker_queue.cpp >> CXX src/mkvtoolnix-gui/util/language_dialog.cpp >> CXX src/mkvtoolnix-gui/util/language_display_widget.cpp >> CXX src/mkvtoolnix-gui/util/media_player.cpp >> CXX src/mkvtoolnix-gui/util/message_box.cpp >> src/mkvtoolnix-gui/util/media_player.cpp: In member function ?void >> mtx::gui::Util::MediaPlayer::handleError(QMediaPlayer::Error)?: >> src/mkvtoolnix-gui/util/media_player.cpp:76:9: error: invalid use of >> incomplete type ?class QDebug? >> 76 | qDebug() << "MediaPlayer::handleError" << error << >> p.errorReported; >> compilation terminated due to -Wfatal-errors. >> CXX src/mkvtoolnix-gui/util/model.cpp >> CXX src/mkvtoolnix-gui/util/modify_tracks_submenu.cpp >> CXX src/mkvtoolnix-gui/util/recently_used_strings.cpp >> CXX src/mkvtoolnix-gui/util/network_access_manager.cpp >> CXX src/mkvtoolnix-gui/util/option_file.cpp >> CXX src/mkvtoolnix-gui/util/process.cpp >> CXX src/mkvtoolnix-gui/util/qgs_collapsible_group_box.cpp >> >> Any pointers on how to fix this would be much appreciated. >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - https://slackbuilds.org/faq/ >> >> _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jebrhansen+SBo at gmail.com Sun Mar 8 17:12:18 2026 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Sun, 8 Mar 2026 13:12:18 -0400 Subject: [Slackbuilds-users] mkvtoolnix problem In-Reply-To: References: Message-ID: This built fine on a clean fully patched install of 15.0. Do you by chance have any of the optional dependencies listed in the mkvtoolnix README installed? I can try again with any you have installed to potentially confirm where the issue is. Below libraries are bundled with the source code and configure will use system version if they are usable: * avilib * librmff * nlohmann-json * pugixml (on SBo) * utf8-cpp * fmt (on SBo) * libebml (on SBo) * libmatroska (on SBo) Installation of the above libraries are completely optional and internal versions are well tested within the application. Jeremy On Sun, Mar 8, 2026, 12:44?PM Luveh Keraph <1.41421 at gmail.com> wrote: > I have had mkvtoolnix running for some time. All of a sudden, I am getting > the following: > > $ mkvtoolnix-gui > mkvtoolnix-gui: error while loading shared libraries: libcmark.so.0.31.1: > cannot open shared object file: No such file or directory > > libcmark.so is part of the cmark-0.31.2 package, which I updated on 21st > February. So, I removed mkvtoolnix and tried to build it again. Alas, it > won't: > > CXX src/mkvtoolnix-gui/util/json_config_file.cpp > CXX src/mkvtoolnix-gui/util/kax_analyzer.cpp > CXX src/mkvtoolnix-gui/util/kax_info.cpp > CXX src/mkvtoolnix-gui/util/language_combo_box.cpp > CXX src/mkvtoolnix-gui/util/serial_worker_queue.cpp > CXX src/mkvtoolnix-gui/util/language_dialog.cpp > CXX src/mkvtoolnix-gui/util/language_display_widget.cpp > CXX src/mkvtoolnix-gui/util/media_player.cpp > CXX src/mkvtoolnix-gui/util/message_box.cpp > src/mkvtoolnix-gui/util/media_player.cpp: In member function ?void > mtx::gui::Util::MediaPlayer::handleError(QMediaPlayer::Error)?: > src/mkvtoolnix-gui/util/media_player.cpp:76:9: error: invalid use of > incomplete type ?class QDebug? > 76 | qDebug() << "MediaPlayer::handleError" << error << > p.errorReported; > compilation terminated due to -Wfatal-errors. > CXX src/mkvtoolnix-gui/util/model.cpp > CXX src/mkvtoolnix-gui/util/modify_tracks_submenu.cpp > CXX src/mkvtoolnix-gui/util/recently_used_strings.cpp > CXX src/mkvtoolnix-gui/util/network_access_manager.cpp > CXX src/mkvtoolnix-gui/util/option_file.cpp > CXX src/mkvtoolnix-gui/util/process.cpp > CXX src/mkvtoolnix-gui/util/qgs_collapsible_group_box.cpp > > Any pointers on how to fix this would be much appreciated. > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From 1.41421 at gmail.com Sun Mar 8 18:44:55 2026 From: 1.41421 at gmail.com (Luveh Keraph) Date: Sun, 8 Mar 2026 12:44:55 -0600 Subject: [Slackbuilds-users] mkvtoolnix problem In-Reply-To: References: Message-ID: Out of those the only one that is installed in my system is pugixml. At any rate, isn't the error diagnostic suggestive of something going on with the Qt library? What follows is a list of packages that may be related to Qt that I have in my system: -rw-r--r-- 1 root root 55573 Jan 22 2025 PyQt5-5.15.2-x86_64-5 -rw-r--r-- 1 root root 5706 Jan 22 2025 QtAV-20210414_305e5404-x86_64-1 -rw-r--r-- 1 root root 5730 Jan 22 2025 bluez-qt-5.90.0-x86_64-1 -rw-r--r-- 1 root root 3796 Jan 22 2025 fcitx-qt5-1.2.7-x86_64-1 -rw-r--r-- 1 root root 1334 Jan 22 2025 kdevelop-pg-qt-2.2.1-x86_64-4 -rw-r--r-- 1 root root 1403 Jan 22 2025 kqtquickcharts-21.12.1-x86_64-1 -rw-r--r-- 1 root root 1697 Jan 22 2025 layer-shell-qt-5.23.5-x86_64-1 -rw-r--r-- 1 root root 1580 Jan 22 2025 libdbusmenu-qt-0.9.3+16.04.20160218-x86_64-3 -rw-r--r-- 1 root root 943 Nov 29 08:21 libqtpas-4.4-x86_64-1_SBo -rw-r--r-- 1 root root 3628 Jan 22 2025 modemmanager-qt-5.90.0-x86_64-1 -rw-r--r-- 1 root root 10825 Jan 22 2025 networkmanager-qt-5.90.0-x86_64-1 -rw-r--r-- 1 root root 3169 Jan 22 2025 polkit-qt-1-0.114.0-x86_64-1 -rw-r--r-- 1 root root 3385 Jan 22 2025 pulseaudio-qt-1.3-x86_64-2 -rw-r--r-- 1 root root 692964 Jan 23 2025 qt5-5.15.3_20220318_e507d3e5-x86_64-1_slack15.0 -rw-r--r-- 1 root root 7219 Jan 22 2025 qt5-webkit-5.212.0_alpha4-x86_64-7 -rw-r--r-- 1 root root 1137955 Dec 28 06:41 qt6-6.8.3-x86_64-2_SBo -rw-r--r-- 1 root root 1716 Jan 22 2025 qtkeychain-0.13.2-x86_64-1 -rw-r--r-- 1 root root 19348 Mar 10 2025 sphinxcontrib-qthelp-2.0.0-x86_64-1_ In particular, Qt6 is very recent. On Sun, Mar 8, 2026 at 11:12?AM Jeremy Hansen wrote: > This built fine on a clean fully patched install of 15.0. > > Do you by chance have any of the optional dependencies listed in the > mkvtoolnix README installed? I can try again with any you have installed to > potentially confirm where the issue is. > > Below libraries are bundled with the source code and configure will use > system version if they are usable: > * avilib > * librmff > * nlohmann-json > * pugixml (on SBo) > * utf8-cpp > * fmt (on SBo) > * libebml (on SBo) > * libmatroska (on SBo) > > Installation of the above libraries are completely optional and internal > versions are well tested within the application. > > Jeremy > > > On Sun, Mar 8, 2026, 12:44?PM Luveh Keraph <1.41421 at gmail.com> wrote: > >> I have had mkvtoolnix running for some time. All of a sudden, I am >> getting the following: >> >> $ mkvtoolnix-gui >> mkvtoolnix-gui: error while loading shared libraries: libcmark.so.0.31.1: >> cannot open shared object file: No such file or directory >> >> libcmark.so is part of the cmark-0.31.2 package, which I updated on 21st >> February. So, I removed mkvtoolnix and tried to build it again. Alas, it >> won't: >> >> CXX src/mkvtoolnix-gui/util/json_config_file.cpp >> CXX src/mkvtoolnix-gui/util/kax_analyzer.cpp >> CXX src/mkvtoolnix-gui/util/kax_info.cpp >> CXX src/mkvtoolnix-gui/util/language_combo_box.cpp >> CXX src/mkvtoolnix-gui/util/serial_worker_queue.cpp >> CXX src/mkvtoolnix-gui/util/language_dialog.cpp >> CXX src/mkvtoolnix-gui/util/language_display_widget.cpp >> CXX src/mkvtoolnix-gui/util/media_player.cpp >> CXX src/mkvtoolnix-gui/util/message_box.cpp >> src/mkvtoolnix-gui/util/media_player.cpp: In member function ?void >> mtx::gui::Util::MediaPlayer::handleError(QMediaPlayer::Error)?: >> src/mkvtoolnix-gui/util/media_player.cpp:76:9: error: invalid use of >> incomplete type ?class QDebug? >> 76 | qDebug() << "MediaPlayer::handleError" << error << >> p.errorReported; >> compilation terminated due to -Wfatal-errors. >> CXX src/mkvtoolnix-gui/util/model.cpp >> CXX src/mkvtoolnix-gui/util/modify_tracks_submenu.cpp >> CXX src/mkvtoolnix-gui/util/recently_used_strings.cpp >> CXX src/mkvtoolnix-gui/util/network_access_manager.cpp >> CXX src/mkvtoolnix-gui/util/option_file.cpp >> CXX src/mkvtoolnix-gui/util/process.cpp >> CXX src/mkvtoolnix-gui/util/qgs_collapsible_group_box.cpp >> >> Any pointers on how to fix this would be much appreciated. >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - https://slackbuilds.org/faq/ >> >> _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From 1.41421 at gmail.com Sun Mar 8 19:30:57 2026 From: 1.41421 at gmail.com (Luveh Keraph) Date: Sun, 8 Mar 2026 13:30:57 -0600 Subject: [Slackbuilds-users] mkvtoolnix problem In-Reply-To: References: Message-ID: For what it is worth, I was able to build it on a different 15.0 system. A major difference is that Qt6 is not installed in this system. On Sun, Mar 8, 2026 at 12:44?PM Luveh Keraph <1.41421 at gmail.com> wrote: > Out of those the only one that is installed in my system is pugixml. At > any rate, isn't the error diagnostic suggestive of something going on with > the Qt library? What follows is a list of packages that may be related to > Qt that I have in my system: > > -rw-r--r-- 1 root root 55573 Jan 22 2025 PyQt5-5.15.2-x86_64-5 > -rw-r--r-- 1 root root 5706 Jan 22 2025 QtAV-20210414_305e5404-x86_64-1 > -rw-r--r-- 1 root root 5730 Jan 22 2025 bluez-qt-5.90.0-x86_64-1 > -rw-r--r-- 1 root root 3796 Jan 22 2025 fcitx-qt5-1.2.7-x86_64-1 > -rw-r--r-- 1 root root 1334 Jan 22 2025 kdevelop-pg-qt-2.2.1-x86_64-4 > -rw-r--r-- 1 root root 1403 Jan 22 2025 kqtquickcharts-21.12.1-x86_64-1 > -rw-r--r-- 1 root root 1697 Jan 22 2025 layer-shell-qt-5.23.5-x86_64-1 > -rw-r--r-- 1 root root 1580 Jan 22 2025 > libdbusmenu-qt-0.9.3+16.04.20160218-x86_64-3 > -rw-r--r-- 1 root root 943 Nov 29 08:21 libqtpas-4.4-x86_64-1_SBo > -rw-r--r-- 1 root root 3628 Jan 22 2025 modemmanager-qt-5.90.0-x86_64-1 > -rw-r--r-- 1 root root 10825 Jan 22 2025 > networkmanager-qt-5.90.0-x86_64-1 > -rw-r--r-- 1 root root 3169 Jan 22 2025 polkit-qt-1-0.114.0-x86_64-1 > -rw-r--r-- 1 root root 3385 Jan 22 2025 pulseaudio-qt-1.3-x86_64-2 > -rw-r--r-- 1 root root 692964 Jan 23 2025 > qt5-5.15.3_20220318_e507d3e5-x86_64-1_slack15.0 > -rw-r--r-- 1 root root 7219 Jan 22 2025 > qt5-webkit-5.212.0_alpha4-x86_64-7 > -rw-r--r-- 1 root root 1137955 Dec 28 06:41 qt6-6.8.3-x86_64-2_SBo > -rw-r--r-- 1 root root 1716 Jan 22 2025 qtkeychain-0.13.2-x86_64-1 > -rw-r--r-- 1 root root 19348 Mar 10 2025 > sphinxcontrib-qthelp-2.0.0-x86_64-1_ > > In particular, Qt6 is very recent. > > > On Sun, Mar 8, 2026 at 11:12?AM Jeremy Hansen > wrote: > >> This built fine on a clean fully patched install of 15.0. >> >> Do you by chance have any of the optional dependencies listed in the >> mkvtoolnix README installed? I can try again with any you have installed to >> potentially confirm where the issue is. >> >> Below libraries are bundled with the source code and configure will use >> system version if they are usable: >> * avilib >> * librmff >> * nlohmann-json >> * pugixml (on SBo) >> * utf8-cpp >> * fmt (on SBo) >> * libebml (on SBo) >> * libmatroska (on SBo) >> >> Installation of the above libraries are completely optional and internal >> versions are well tested within the application. >> >> Jeremy >> >> >> On Sun, Mar 8, 2026, 12:44?PM Luveh Keraph <1.41421 at gmail.com> wrote: >> >>> I have had mkvtoolnix running for some time. All of a sudden, I am >>> getting the following: >>> >>> $ mkvtoolnix-gui >>> mkvtoolnix-gui: error while loading shared libraries: >>> libcmark.so.0.31.1: cannot open shared object file: No such file or >>> directory >>> >>> libcmark.so is part of the cmark-0.31.2 package, which I updated on 21st >>> February. So, I removed mkvtoolnix and tried to build it again. Alas, it >>> won't: >>> >>> CXX src/mkvtoolnix-gui/util/json_config_file.cpp >>> CXX src/mkvtoolnix-gui/util/kax_analyzer.cpp >>> CXX src/mkvtoolnix-gui/util/kax_info.cpp >>> CXX src/mkvtoolnix-gui/util/language_combo_box.cpp >>> CXX src/mkvtoolnix-gui/util/serial_worker_queue.cpp >>> CXX src/mkvtoolnix-gui/util/language_dialog.cpp >>> CXX src/mkvtoolnix-gui/util/language_display_widget.cpp >>> CXX src/mkvtoolnix-gui/util/media_player.cpp >>> CXX src/mkvtoolnix-gui/util/message_box.cpp >>> src/mkvtoolnix-gui/util/media_player.cpp: In member function ?void >>> mtx::gui::Util::MediaPlayer::handleError(QMediaPlayer::Error)?: >>> src/mkvtoolnix-gui/util/media_player.cpp:76:9: error: invalid use of >>> incomplete type ?class QDebug? >>> 76 | qDebug() << "MediaPlayer::handleError" << error << >>> p.errorReported; >>> compilation terminated due to -Wfatal-errors. >>> CXX src/mkvtoolnix-gui/util/model.cpp >>> CXX src/mkvtoolnix-gui/util/modify_tracks_submenu.cpp >>> CXX src/mkvtoolnix-gui/util/recently_used_strings.cpp >>> CXX src/mkvtoolnix-gui/util/network_access_manager.cpp >>> CXX src/mkvtoolnix-gui/util/option_file.cpp >>> CXX src/mkvtoolnix-gui/util/process.cpp >>> CXX src/mkvtoolnix-gui/util/qgs_collapsible_group_box.cpp >>> >>> Any pointers on how to fix this would be much appreciated. >>> _______________________________________________ >>> SlackBuilds-users mailing list >>> SlackBuilds-users at slackbuilds.org >>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >>> FAQ - https://slackbuilds.org/faq/ >>> >>> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - https://slackbuilds.org/faq/ >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From fsleg at t-rg.ws Sun Mar 8 20:32:30 2026 From: fsleg at t-rg.ws (fsLeg) Date: Sun, 8 Mar 2026 23:32:30 +0300 Subject: [Slackbuilds-users] mkvtoolnix problem In-Reply-To: References: Message-ID: <2954f902-db5f-46d9-82e2-5cbee17960ce@t-rg.ws> Can confirm, just had the same error trying to recompile mkvtoolnix on my 15.0 with qt6 installed. Looking at output, it tries to link against qt6 instead of qt5, and the output of `./configure --help` confirms that by default mkvtoolnix only uses qt5 as a fallback if qt6 is not found. You need to add `--disable-qt6` option to configure in the SlackBuild to force building against qt5. Just tried it and it compiled for me, although my system is non-standard as I have packages from testing/ installed, namely graphics-updates and binutils-gcc-glibs, so I'm not sure if it helps with a vanilla system. On 3/8/26 22:30, Luveh Keraph wrote: > For what it is worth, I was able to build it on a different 15.0 system. > A major difference is that Qt6 is not installed in this system. From fourtysixandtwo at sliderr.net Sun Mar 8 21:20:50 2026 From: fourtysixandtwo at sliderr.net (fourtysixandtwo) Date: Sun, 8 Mar 2026 15:20:50 -0600 Subject: [Slackbuilds-users] mkvtoolnix problem In-Reply-To: <2954f902-db5f-46d9-82e2-5cbee17960ce@t-rg.ws> References: <2954f902-db5f-46d9-82e2-5cbee17960ce@t-rg.ws> Message-ID: I ran into this problem a couple weeks ago. My solution was to upgrade mkvtoolnix to 97.0 locally. A note in the README is surely warranted if not fsleg's fix. On Sun, Mar 8, 2026 at 2:32?PM fsLeg via SlackBuilds-users wrote: > > Can confirm, just had the same error trying to recompile mkvtoolnix on > my 15.0 with qt6 installed. Looking at output, it tries to link against > qt6 instead of qt5, and the output of `./configure --help` confirms that > by default mkvtoolnix only uses qt5 as a fallback if qt6 is not found. > > You need to add `--disable-qt6` option to configure in the SlackBuild to > force building against qt5. Just tried it and it compiled for me, > although my system is non-standard as I have packages from testing/ > installed, namely graphics-updates and binutils-gcc-glibs, so I'm not > sure if it helps with a vanilla system. > > On 3/8/26 22:30, Luveh Keraph wrote: > > For what it is worth, I was able to build it on a different 15.0 system. > > A major difference is that Qt6 is not installed in this system. > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > From 1.41421 at gmail.com Sun Mar 8 22:19:49 2026 From: 1.41421 at gmail.com (Luveh Keraph) Date: Sun, 8 Mar 2026 16:19:49 -0600 Subject: [Slackbuilds-users] mkvtoolnix problem In-Reply-To: References: <2954f902-db5f-46d9-82e2-5cbee17960ce@t-rg.ws> Message-ID: Thanks, version 97.0 builds and runs with no problem, assuming that pugixml is also present. On Sun, Mar 8, 2026 at 3:21?PM fourtysixandtwo wrote: > I ran into this problem a couple weeks ago. My solution was to > upgrade mkvtoolnix to 97.0 locally. > > A note in the README is surely warranted if not fsleg's fix. > > On Sun, Mar 8, 2026 at 2:32?PM fsLeg via SlackBuilds-users > wrote: > > > > Can confirm, just had the same error trying to recompile mkvtoolnix on > > my 15.0 with qt6 installed. Looking at output, it tries to link against > > qt6 instead of qt5, and the output of `./configure --help` confirms that > > by default mkvtoolnix only uses qt5 as a fallback if qt6 is not found. > > > > You need to add `--disable-qt6` option to configure in the SlackBuild to > > force building against qt5. Just tried it and it compiled for me, > > although my system is non-standard as I have packages from testing/ > > installed, namely graphics-updates and binutils-gcc-glibs, so I'm not > > sure if it helps with a vanilla system. > > > > On 3/8/26 22:30, Luveh Keraph wrote: > > > For what it is worth, I was able to build it on a different 15.0 > system. > > > A major difference is that Qt6 is not installed in this system. > > _______________________________________________ > > SlackBuilds-users mailing list > > SlackBuilds-users at slackbuilds.org > > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > > FAQ - https://slackbuilds.org/faq/ > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: