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.
If you examine the Slackware-current changelog you'll not that not every piece of software gets recompiled when glibc is upgraded. This indicates that it should be possible to upgrade in place and not break things. But of course, anything you compile afterwards will not be compatible with a stock Slackware-14.2 installation.
There is no need to upgrade glibc (nor glib2 as stated in the previous thread). You will not get different answers asking again the same questions in a new thread.
This being said, feel to break your system. Just don't count on us to repair it.
My guess is that he installed some package meant for Slackware-current (which is compiled against the glibc in -current). Now on Slackware 14.2 that will generate all sorts of runtime linker errors about GLIBC_2.23 symbols not being found.
Because I found a file on YouTube that requires the use of subtitles.
We can't read your mind. Are you seeing error messages that lead to this conclusion? Then show them to us! If you're getting frustrated that you're not receiving the help you'd like, it's because you're not providing enough information for us to help you.
Instead of speculating, like Alien Bob did in the previous post, we could potentially tell you exactly what is wrong and how to fix it.
Going along with Alien Bob's speculation, please note that in the vast majority of cases (actually probably ALL cases) you cannot install a -current Slackware package in 14.2. They have diverged too much. If you want an upgraded package from -current you'll have to download the sources and run the SlackBuild yourself on 14.2 to compile the package - I actually do this with vim.
Because I found a file on YouTube that requires the use of subtitles.
This is a pointless answer. We don't know what you mean.
If you mean you're trying to watch a YouTube video online, the online player doesn't use avidemux and displays captions via the HTML5 player.
If you're trying to download a YouTube video with captions, then again, you don't need avidemux, as you can use a downloader (like youtube-dl) to download the video and subtitles and then you can use any player that supports subtitles to play it (I use smplayer).
If you were watching a YouTube video on how to use avidemux to use subtitles, and they said you need a newer glib, glib2, or glibc, then that might be OS specific. Needs more details for us to properly guide you.
If you were watching a YouTube video on using avidemux and you ran into a problem with building or running the program, show us the error.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.