[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: More on Kpackage



> Just to explain a bit more about the Kpackage bug in SuSE 6.4 that
> both myself and Craig Andrews have come across.

Doesn't look like a Kpackage bug to me, I'm afraid!! Looks like you have a
rpm problem, either a bug in the software (unlikely), or a database problem
(possible), or a system inconsistency (likely).

> This might suggest that it's just Kpackage ?  But, when I try to
> install a GRASS 4.21 rpm (for Red Hat 6.0) I find that I get
> "libjpeg.so.6 is needed by by GRASS-4.2.1.i586.rpm".  libjpeg.so.6 is
> definitely on my hard disk.  I can see it at.....
>
> /usr/lib/libjpeg.so.6
> /usr/lib/libjpeg.so.62
>
> Both Craig and myself have had a look at this and we can't figure it
> out.  Even tied all of the RPM options for installation.

What's happening (obviously ;) is that it can't see libjpeg. Admission
first: I hate libraries. I compile all my software statically. I think
libraries are the spawn of the devil himself [1], and I refuse to use them,
have no knowledge of how they work, nor do I care about that !!

But.. I believe you have to have some sort of map or something so the system
can see stuff? 'ldconfig' or something? Sounds like you need to run that to
update the system to tell it everything is there? Odd, though, because
libjpeg is fairly common, and should be installed properly. Another
possibility is that libjpeg isn't in rpm's database (is it 'rpm -qa | grep
libjpeg' or something? that should find things....), in which case it
doesn't think it's installed. Try installing the libjpeg rpm again?

Whether or not GRASS needs libjpeg, I don't know. I should think so, being
an image data tool in some respects, so maybe you've just picked two rpms
that have the same problem? Try installing a console program that doesn't do
anything graphical (a console CD-player, for example, there's plenty of
them!!). If that fails the dependency, you have a serious problem.

Other things you might want to check out - where $LD_LIBRARY_PATH points,
and other such variables. I can't remember what they do, I don't much care
(see above! ;), but they might be implicated also!

Other than that, dunno really.

Cheers,

Alex.

[1] - I like the idea of libraries. Just, in practice, they're crap.
Especially dll's. Awful. IMHO, anything with any version dependency problems
should install to a CVS tree by default, and whenever you need a specific
version of a library, you just check it out. But then, I have /home/alex
installed to a CVS tree, so perhaps I'm just a VS-nut...

---------------------------------------------------------------------
Sheffield Linux User's Group - http://www.sheflug.co.uk
To unsubscribe from this list send mail to
- <sheflug-request [at] vuw.ac.nz> - with the word 
 "unsubscribe" in the body of the message. 

  GNU the choice of a complete generation.