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.
I've some problems to complie Kino for Slackware64
If I compile one of the first requirements on a native slack64 system
some thing like this
Code:
checking for LIBRAW1394... yes
checking for LIBAVC1394... configure: error: Package requirements (libavc1394 >= 0.5.1) were not met:
No package 'libavc1394' found
Alternatively, you may set the environment variables LIBAVC1394_CFLAGS
and LIBAVC1394_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
Is the libavc1394 you installed at least version 0.5.1? Did you install it in a non-standard location like your $HOME?
I don't know the directory layout of Slackware64 or how FHS compliant it is, but 64-bit libraries belong in lib64. Thus, the metadata files end up in lib64/pkgconfig. That can mess up pkg-config when it looks for dependencies. Try setting your PKG_CONFIG_PATH to look for the metadata files for 64-bit libraries when you execute the configure script. For example
You may want to try the libavc1394 from SlackBuilds.org. It appears to have been updated for Slackware64-current, although I have not tried it on my Slackware64 system.
I had this problem when installing the dependencies for gksu in current64. Everything installed OK until I got to the gksu SlackBuild itself & it errored as above. What I found was that the libs for libgksu were installed to /usr/lib, instead of /usr/lib64. I added "/usr/lib" to PKG_CONFIG_PATH, then ran the gksu SlackBuild again & all worked. I don't know if this is the best way to do this. I should probably rewrite the SlackBuild so that the libraries for libgksu are put in the proper directory, but I don't yet know enough about lib64 vs lib, etc. to be sure of what I am doing.
Regards,
Bill
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.