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.
Gugur, what Didier Spaier was suggesting is manually compiling it by hands using slackbuild scripts (a good thing to know how to do). Since you're using sbopkg, you need to do a variation of what Didier Spaier is suggesting in order to get LAME working in sbopkg. Go back to sbopkg, find ffmpeg in there, and enter its detail page. Go down to Options, enter in "LAME=yes" in there and then you can rebuild ffmpeg with that option activated in sbopkg. As Darth Vader pointed out, LAME need to be installed first before this can work.
No apology needed, I should have read the first post more carefully.
On the other hand Gugur, my advice is to first build packages from stuff available @ SBo manually, waiting until you be acquainted with the building process to use tools that automate it. Then you will more easily handle issues like this one.
Gugur, what Didier Spaier was suggesting is manually compiling it by hands using slackbuild scripts (a good thing to know how to do). Since you're using sbopkg, you need to do a variation of what Didier Spaier is suggesting in order to get LAME working in sbopkg. Go back to sbopkg, find ffmpeg in there, and enter its detail page. Go down to Options, enter in "LAME=yes" in there and then you can rebuild ffmpeg with that option activated in sbopkg. As Darth Vader pointed out, LAME need to be installed first before this can work.
Some may also not be aware that you can put these options into your queue files. When I last built ffmpeg for 14.1 using sbopkg, I had the following queue file. The @ symbol means it will follow any queue files I have for those packages. Then, on the program you want options passed against, you just use the pipe symbol "|" and then add all the options you need.
So, for the programs listed here, you'd need a simple queue file like the following. Note, since winff requires ffmpeg, that would be the last item on the queue. As SW64 mentioned, since you're wanting to convert from opus to mp3, you will probably need the opus codec installed too.
Code:
opus
lame
ffmpeg | LAME=yes OPUS=yes
winff
Save the file as winff.sqf under /var/lib/sbopkg/queues/ and then run sbopkg -i winff and when it prompts you if you want to build just the package or the queue file, select q for the queue file and let it work its magic.
=====================================
To get a little more advanced with queue files (feel free to disregard this if your struggling with this already). You may want to add things down the road to ffmpeg, but it might be hard to remember that you had all your ffmpeg options stored in winff. Because of this, you may want to create a separate queue file for winff and ffmpeg. This is when that @ symbol becomes handy. The @ symbol means it will process a queue file that exists with that name before continuing down the list. You could create a ffmpeg.sqf file that contains:
Code:
opus
lame
ffmpeg | LAME=yes OPUS=yes
Then, if you need to add future capabilities (like maybe x264 encoding), you just modify it to add the x264 library and add the X264=yes option.
Then, for winff, you simply put the @ in front of the ffmpeg option and it will then process the whole ffmpeg queue file before it builds winff.
That's excellent, bassmadrigal. I've been on a look out for tips on taming the slackbuilds with large amount of manual options that 'sqg -p [package]' alone will not resolve, such as ffmpeg where I wish to compile it with all options activated. I'll definitely will make use of this. Thanks!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.