LinuxQuestions.org
Visit the LQ Articles and Editorials section
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 12-26-2007, 09:33 AM   #1
johnvoisey
Member
 
Registered: Jun 2002
Location: UK
Distribution: Used many over the years, main ones now "CentOS", Slackware and Arch
Posts: 31

Rep: Reputation: 15
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 all-recursive
make[1]: Entering directory `/usr/local/src/magicolor2430DL-1.6.0'
Making all in src
make[2]: 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[2]: *** [rastertokm2430dl] Error 1
make[2]: Leaving directory `/usr/local/src/magicolor2430DL-1.6.0/src'
make[1]: *** [all-recursive] Error 1
make[1]: 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 !!
 
Old 12-26-2007, 09:56 AM   #2
H_TeXMeX_H
Guru
 
Registered: Oct 2005
Location: $RANDOM
Distribution: slackware64
Posts: 12,928
Blog Entries: 2

Rep: Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269
'.a' is the static library, so in this case, when configuring liblcms you should run './configure --enable-static'.
 
Old 12-26-2007, 03:24 PM   #3
jong357
Senior Member
 
Registered: May 2003
Location: Columbus, OH
Distribution: DIYSlackware
Posts: 1,914

Rep: Reputation: 52
Well... Slackware comes with lcms. The problem is:

Quote:
Originally Posted by lcms.SlackBuild
./configure \
--prefix=/usr \
--mandir=/usr/man \
--enable-static=no
Who's fault is it? The packager making the assumption that static libs are worthless or the individual developer insisting on linking against static libs?

I have the same problem with a couple progs with regards to freetype. Gotta rebuild Freetype to get the static lib back..

Quote:
Originally Posted by freetype.SlackBuild
# Can't imagine a lot of use for this:
rm -f $PKG/usr/lib/*.a
I can... :-)

Last edited by jong357; 12-26-2007 at 03:29 PM.
 
Old 12-26-2007, 03:43 PM   #4
gnashley
Amigo developer
 
Registered: Dec 2003
Location: Germany
Distribution: Slackware
Posts: 4,771

Rep: Reputation: 477Reputation: 477Reputation: 477Reputation: 477Reputation: 477
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.
 
Old 12-26-2007, 03:50 PM   #5
jong357
Senior Member
 
Registered: May 2003
Location: Columbus, OH
Distribution: DIYSlackware
Posts: 1,914

Rep: Reputation: 52
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

Last edited by jong357; 12-26-2007 at 03:53 PM.
 
Old 12-26-2007, 03:57 PM   #6
johnvoisey
Member
 
Registered: Jun 2002
Location: UK
Distribution: Used many over the years, main ones now "CentOS", Slackware and Arch
Posts: 31

Original Poster
Rep: Reputation: 15
SOLVED !!! Thanks people

Thanks for the explanations,

After reading up the replies I went and grabbed the source and yes a swift configure and make means I have the ".a" file and yes I have a cups printer driver working now.

I guess it shows package building for distros is a bit of a black art as you never quite know what people will want to do with the software that gets packaged for distribution.

Again thanks all. regards and seasons greetings JV
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
How to install liblcms and liblcms-devel Peter6000 Fedora 4 03-01-2007 02:49 AM
using older slackware package for newer slackware. Is it problematic? hottdogg Slackware 2 12-13-2005 04:57 AM
first slackware package Rognon Slackware 2 10-14-2004 11:15 PM
Liblcms.so Lobais Linux - Software 5 03-12-2004 02:18 PM
liblcms install problem BlckJck Debian 2 06-20-2003 03:24 AM


All times are GMT -5. The time now is 03:59 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration