SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Distribution: Used many over the years, main ones now "CentOS", Slackware and Arch
liblcms.a not in slackware 12 lcms package ?
OK I don't know where best to put this request for help / ideas but here goes.
I've just built a slackware 12 system. I'd like to get the CUPS stuff working for my Konica Minolta MC2430DL. In previous versions of slackware this has been FAIRLY straightforward (for slackware!!) it's been a matter of downloading the driver source from linuxprinting.org, then grab marcus kuhn's jbigkit (which the linuxprinting driver needs), ./configure and make jbigkit, copy the .h file to /usr/local/include, copy the .a file to /usr/local/lib and then the "magicolour2430DL" driver can be built using its ./configure and make. Well that worked for slackware 10 / 11 anyway.
Got a bit of a snag here with slackware 12 though.
The "magicolour" ./configure worked just fine, it packs up the "jbigkit" dependency and says all is fine. But then make fails like this :-
make: Entering directory `/usr/local/src/magicolor2430DL-1.6.0'
Making all in src
make: Entering directory `/usr/local/src/magicolor2430DL-1.6.0/src'
gcc -g -O2 -o rastertokm2430dl rastertokmlf.o bmp.o /usr/local/lib/liblcms.a /usr/local/lib/libjbig.a -lcupsimage -lcups
gcc: /usr/local/lib/liblcms.a: No such file or directory
make: *** [rastertokm2430dl] Error 1
make: Leaving directory `/usr/local/src/magicolor2430DL-1.6.0/src'
make: *** [all-recursive] Error 1
make: Leaving directory `/usr/local/src/magicolor2430DL-1.6.0'
make: *** [all] Error 2
OK it can't find a file liblcms.a
That's not too surprising given that the MANIFEST.bz2 file shows a liblcms.so.1.0.16 being put in /usr/lib, and a liblcms.la going in /usr/lib, but no liblcms.a at all.
Can someone explain what this .a file is and how I get one / make one ?
Last edited by johnvoisey; 12-26-2007 at 03:54 PM.
Reason: SOLVED !!
This is fairly common in Slackware packages. I have run across this several times in different versions and with different libs. Just recompile lcms using "--enable-static=yes" and all should be okay. I'll guess that Patrick leaves the static libs out when he knows that none of the packages included in the standard distribution need them. Anyway,sometimes mistakes creep in -I remember one version when basic GTK2 apps wouldn't compile beacuse the gtk-2.0.pc file wasn't installed with the package.
Yea.. We all know static libs are about as useless as tits on a bull but until people quit linking against them it's not such a hot idea to remove them. Fedora and others are going crazy with that philosophy and they can get away with it because their package base is enormous. You can't say the same for Slackware. Slackers compile software and we need the tools to do it... Best to leave that stuff alone IMO...
With things like Splashy, it makes sense to be compiled statically, and indeed it's not gonna work trying to link against a shared library.. No avoiding it there, so if you want to use Splashy, you need libfreetype.a