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 13.37 and -current, Dragonfly BSD
Posts: 1,810
Rep:
Quote:
Didn't realize slacky.eu had build scripts for their packages. Thanks, that'll come in handy for when I can't find something on Slackbuilds.org
Just check the "src/" directory - they host the SlackBuild and the source. A very useful resource to add to your armoury
I would still recommend looking at README's, INSTALL's, slack-required's etc as well as the *.SlackBuild before running to make sure all requisites are followed and no oddness is scripted in.
Thanks. I learned long ago that the worst proofreader, editor, and reviewer of any written piece is the original author. Feedback and additional writing effort is almost always needed. So thanks to everybody who responded.
In regard of DavidHindman's compilation or package creation problems, I noticed that many applications and components, which depend on ffmpeg components (like libavcodec or libavformat), look for the header files and libraries in the wrong places.
They mostly expect a ffmpeg subdirectory wherever they search for them, or you indicate where they are supposed to be and they still look for an ffmpeg subdirectory.
This even happens with the slackbuilds.org built package of ffmpeg.
One way for me to overcome this, was to create ffmpeg directories in /usr/lib and /usr/include and create symbolic links to the files in question. ie:
Check the configure.log file to see which headers or libraries are not found.
I experienced this when satisfying the dependencies for mediatomb and ushare.
I could not make k3b recognize the presence of libmusicbrains installation.
Here is some output of k3b's configure script:
Code:
checking musicbrainz/mb_c.h usability... no
checking musicbrainz/mb_c.h presence... no
checking for musicbrainz/mb_c.h... no
K3b - Tag guessing using MusicBrainz no
K3b - You are missing the musicbrainz headers and libraries.
K3b - K3b will be compiled without support for tag guessing.
I have installed libmusicbrainz-3.0.2. The library header that k3b-1.0.5 does not find is present in:
So - not just a simple include directory name difference, but
a complete library change too.
Looks to me as if k3b is set to use an older version of musicbrainz.
So - you either persuade k3b to use the new library (unlikely i'd guess),
or you install an older version of musicbrainz (maybe ver 2 or 1 ?) and
try again. Maybe there's a newer version of k3b (in subversion/development)
that is using the new musicbrainz.
But this is the fun part. And when you solve it, you will be the stronger
for it.
Note: there is a small bug with building ffmpeg. The bug is being remedied in the slackbuild script but is not yet uploaded. The ffmpeg configure file is hard-coded to look for a TEMPDIR variable. If you use /tmp as your temporary working directory then run the build script like this: TEMPDIR=/tmp sh ffmpeg.SlackBuild.
Of course, then try again to build transcode.
Thanks for solving 24 hours of frustration for me when attempting to build the new version of transcode! I note the FFmpeg script on slackbuilds.org has not received this small but vital change, was it rejected for some reason?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.