find libraries
Klaus-Peter Schrage
kpschrage
Sun Oct 31 12:06:31 PST 2004
Collins Richey wrote:
> On Sun, 31 Oct 2004 16:40:04 +0100, Klaus-Peter Schrage
> <kpschrage at gmx.de> wrote:
>
>>Rick Sivernell wrote:
>>
>>>All
>>>
>>> I have moved my desktop machine from genttoo, unable to get things just to run
>>>propely, to Suse 9.0. I am trying to build some programs, Eterm and scite and
>>>others, b ut ./configure is not finding some of the required libs, yes I went and
>>>got them, built them and most go in /usr/lib, some are in /usr/local/lib. the
>>>ld.so.conf has these directories in them and the ldconfg -v | grep lbast* finds
>>>the lib in /usr/local/lib. What eles do i need to done to get other programs to
>>>see my new libs. I am trying to build all code insttead of rpm. On getting xfce4
>>>I have the tarballs but is their an easy way to build the many tarballs?
>>
>>A thing often forgotten (by me): When you compile a program from source,
>>say xxx.tar.gz, which needs libyyy, it's usually not sufficient to have
>>the package libyyy.rpm installed, but also libyyy-devel.rpm which many
>>distros don't install by default.
>>So I have made it my habit to install the -devel counterpart to any new
>>lib, even if it's not needed at first sight.
>
>
> I'm not really a heavy with RPM based distros like SUSE, but I would
> think the thing to do with source based products is to get (or make)
> an SRPM. The output of this is then a binary that you install with
> normal RPM facilities and, thus, there SHOULD be few complaints about
> missing libraries.
>
Agreed, as far as getting and using a prefabricated SRPM is concerned.
But MAKING it from a plain tarball is a thing I never tackled - perhaps
others on this list are more daring.
What I did instead to keep my self compiled applications in line with
the rpm package system was using checkinstall, but alas, I found that no
version of it would play with my Fedara 2.
Klaus
More information about the Linux-users
mailing list