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.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,126
Original Poster
Rep:
Quote:
+--------------------------+
Sat Oct 14 08:49:55 UTC 2023
chromium: updated 64bit to 118.0.5993.70 (Slackware 15.0 & onwards).
chromium-ungoogled: updated 64bit to 118.0.5993.70 (Slackware 15.0 & onwards)
Anyone else having trouble with cmake for his ffmpeg build? Specifically ffmpeg 5.1.3 and building the game music emulator lib? I've never really used cmake before, but I think the problem lies in the version I'm using? Could someone confirm whether it's demanding I use an older/newer version of cmake for this?
A relevant extract from the CMakeLists.txt found in the build env for gme leads me to believe I need a version under 2.7:
Code:
# 2.6+ always assumes FATAL_ERROR, but 2.4 and below don't.
# Of course, 2.4 might work, in which case you're welcome to drop
# down the requirement, but I can't test that.
cmake_minimum_required(VERSION 2.6 FATAL_ERROR)
but then when I try running the cmake command in the build env itself, I get this warning:
Code:
CMake Deprecation Warning at CMakeLists.txt:12 (cmake_minimum_required):
Compatibility with CMake < 2.8.12 will be removed from a future version of
CMake.
Update the VERSION argument <min> value or use a ...<max> suffix to tell
CMake that the project does not need compatibility with older versions.
CMake Error at CMakeLists.txt:72 (if):
if given arguments:
"(" "VERSION_GREATER" "4.1" ")" "OR" "(" "VERSION_EQUAL" "4.1" ")"
Unknown arguments specified
Which, in the larger context of its original stanza:
Code:
# gcc <4.1 had poor support for symbol visibility
if ((${_gcc_version} VERSION_GREATER "4.1") OR (${_gcc_version} VERSION_EQUAL "4.1"))
set (CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -fvisibility=hidden")
set (ENABLE_VISIBILITY ON)
add_definitions (-DLIBGME_VISIBILITY)
# GCC >= 4.2 also correctly supports making inline members have hidden
# visibility by default.
if ((${_gcc_version} VERSION_GREATER "4.2") OR (${_gcc_version} VERSION_EQUAL "4.2"))
set (CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -fvisibility-inlines-hidden")
endif()
endif()
endif() # test visibility
leads me to believe that versions greater than 2.6 should work.
I'm currently using cmake 3.21.4 and just updated and upgraded my system yesterday. I'm on 15.0 stable. Was this package built with slackware -current in mind maybe?
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,126
Original Poster
Rep:
Alienbob has been kind enough to update his VLC package.
Quote:
Tue Oct 17 12:15:40 UTC 2023
vlc: updated to 3.0.19 for Slackware 15.0 and -current.
Removed the package for Slackware 14.2.
Added 4K HDR tone-mapping support via libplacebo.
Added soxr as audio resampling engine.
Updated internal libs: dav1d, ffmpeg, libva, shout, upnp, vpx.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.