On Sat, 12 Jun 1999, David Krings wrote:
> Hi !
>
> Tosday I tried to install an mp3-player (i loaded x11amp [as
rpm],
> kjukebox and mp3-studio). Again I ran into tremendous problems like I
> always do when I try to install something. I'm using RedHat 5.2, kernel
> 2.0.36 and KDE 1.1.1 (if more information about my linux is needed,
please
> tell me).
>
> The x11rpm asks for some files in order of unsolved
dependencies. I never
> have a clue where to get those files, because only the file names and
not
> the name of a required package is reported (would be very comfortable
if
> the producers of rpms would add a source where to get those files).
Pardon the autoplagiarism:
I make an rpmlist by cd'ing to the RPMS dir on a RH cd and doing
rpm -qilp * >~/rpmlist
That gives me a file with the package descriptions and file list that's
very useful for finding my way around RedHat.
Just find the file you need with less, and then back up till you get to
the package header, and you know what package you need.
> I think of installing more programs to my system in future and
I guess I
> will always have the same problem. I don't think it is senseful to bug
ppl
> on this list everytime I want to install something, so that I'm
interested
> in a basic explanation on hwo to install software with less or even no
> problems. Especially this point is imho the biggest disadvantage of
Linux.
>
>
> How can I figure out, what package includes the requested files
?
> Where can I find packages (besides rufus) ?
> What do I have to do if the file is probably already on my
puter, but has
> a different name ? (I had once probs with a libstdc++.so.2.9 that was
named
> on my puter libstdc++.2.9 !)
> Why is it always such a (unnecessary) problem to figure that
out ?
Just try developing a package to run on any conceivable system and see
how easy it is. :-)
I think rpm only knows about files it has installed.
I use rpm -i --nodeps
but I don't expect rpm to keep track of things. This is a SlackHat
system. :-)
>
> The other progs were available as tar.gz files, so I unpacked
them and
> wanted to go the typical way with ./configure, make, make install. This
is
> pretty easy. But everytime ./configure aborts telling me that c++ / g++
are
> not able to produce executables.
> What can I do to make the compiler (is it the compiler ?) to
create
> executables ?
> Is there anything missing ?
>
Yes. Something is missing. To create c++ executables, you need at
least:
gcc or egcs.
glibc-devel*.rpm
libg++-devel*.rpm
binutils-*.rpm
the -devel package for any other library the program relies on, for
instance XFree86-devel.
Lawson
>< Microsoft free environment
This mail client runs on Wine. Your mileage may vary.
___________________________________________________________________
Get the Internet just the way you want it.
Free software, free e-mail, and free Internet access for a month!
Try Juno Web: http://dl.www.juno.com/dynoget/tagj.
