SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Thunderbird 115 Now Available & It Looks Fantastic
Code:
As a devoted Thunderbird mail client user for the past nearly twenty years
since its first release, I'm elated today by the release of Thunderbird 115.
Thunderbird 115 Now Available & It Looks Fantastic
Code:
As a devoted Thunderbird mail client user for the past nearly twenty years
since its first release, I'm elated today by the release of Thunderbird 115.
For some reason, this isn't compiling here. I've tried using the bootstrap, setting rpath = true, kludging the stage2 library path in LD_LIBRARY_PATH (but the build overwrites that variable), setting the stage2 path in /etc/ld.so.conf.d/rust-kludge.conf and running ldconfig (but the build still overrides this somehow).
Basically, at some point in the stage2 build, I get a ton of errors like this:
Code:
warning: the code example in lint `forbidden_lint_groups` in /tmp/rustc-1.71.0-src/compiler/rustc_lint_defs/src/builtin.rs failed to generate the expected output: did not find lint `forbidden_lint_groups` in output of example, got:
/tmp/rustc-1.71.0-src/build/x86_64-unknown-linux-gnu/stage2/bin/rustc: error while loading shared libraries: librustc_driver-732696a5e5992975.so: cannot open shared object file: No such file or directory
Any clues appreciated. Meanwhile at least we should be good with 1.70.0 for now. Technically FF/TB 115 want rust 1.69.0 (and usually I don't push it with that) but seeing other distributions and BSDs using rust 1.70.0 and not needing to patch anything I figured I'd try it, and it seems to be fine here anyway.
For some reason, this isn't compiling here. I've tried using the bootstrap, setting rpath = true, kludging the stage2 library path in LD_LIBRARY_PATH (but the build overwrites that variable), setting the stage2 path in /etc/ld.so.conf.d/rust-kludge.conf and running ldconfig (but the build still overrides this somehow).
Basically, at some point in the stage2 build, I get a ton of errors like this:
Code:
warning: the code example in lint `forbidden_lint_groups` in /tmp/rustc-1.71.0-src/compiler/rustc_lint_defs/src/builtin.rs failed to generate the expected output: did not find lint `forbidden_lint_groups` in output of example, got:
/tmp/rustc-1.71.0-src/build/x86_64-unknown-linux-gnu/stage2/bin/rustc: error while loading shared libraries: librustc_driver-732696a5e5992975.so: cannot open shared object file: No such file or directory
Any clues appreciated. Meanwhile at least we should be good with 1.70.0 for now. Technically FF/TB 115 want rust 1.69.0 (and usually I don't push it with that) but seeing other distributions and BSDs using rust 1.70.0 and not needing to patch anything I figured I'd try it, and it seems to be fine here anyway.
Thanks! The patches didn't fix the problem, but looking at their PKGBUILD I noticed this in the [build] section of config.toml:
Code:
# Generating docs fails with the wasm32-* targets
docs = false
It was while attempting to generate docs that the problem occurred, so I added this and got a successful build and package. But not wanting to use "docs = false" I poked through the recent commits to rust master and found this:
Thanks! The patches didn't fix the problem, but looking at their PKGBUILD I noticed this in the [build] section of config.toml:
Code:
# Generating docs fails with the wasm32-* targets
docs = false
It was while attempting to generate docs that the problem occurred, so I added this and got a successful build and package. But not wanting to use "docs = false" I poked through the recent commits to rust master and found this:
I can confirm , build vmaf here without extra deps mentioned on slackbuilds , all fine.
Quote:
[1/2] /usr/bin/meson test --no-rebuild --print-errorlogs
1/13 test_picture OK 0.08s
2/13 test_feature_collector OK 0.08s
3/13 test_thread_pool OK 0.07s
4/13 test_model OK 0.07s
5/13 test_predict OK 0.06s
6/13 test_feature_extractor OK 0.06s
7/13 test_dict OK 0.05s
8/13 test_cpu OK 0.05s
9/13 test_ref OK 0.04s
10/13 test_feature OK 0.03s
11/13 test_ciede OK 0.03s
12/13 test_cambi OK 0.02s
13/13 test_luminance_tools OK 0.01s
Last edited by USUARIONUEVO; 07-15-2023 at 04:56 PM.
The point I was making is that ffmpeg will not work with --enable-libvmaf unless vmaf is also included in the slackware tree.
But the patch suggested by Eeel does not use --enable-libvmaf unless an environment variable VMAF has been set to something else than "no" ("yes" would be a good choice) before the SlackBuild script is run.
So to get VMAF support in ffmpeg with that suggested patch you would need to:
Install vmaf
set the environment variable VMAF to something like "yes"
rebuild the ffmpeg package using the patched ffmpeg.SlackBuild script
So the patch would only be useful for those who rebuild their ffmpeg from source. The original ffmpeg.SlackBuild script already supports other libraries not included in Slackware in a similar way.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.