Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
You might want to take a few seconds and fill in your profile details, or at least tell which distribution you are using when asking a question. That way we can help you faster and more precisely.
If your distribution can handle .rpm files, basically all you've to do is to open a terminal and type:
rpm -ivh Winamp-2.a1-1.i386.rpm
Actually you don't even have to do that. If you're using any fairly advaned RPM-based distribution all you need to do is click on the file from a file manager, and a graphical package manager will guide you through the whole process and do it's best to deal with any dependency issues arising form it as well.
Actually you don't even have to do that. If you're using any fairly advaned RPM-based distribution all you need to do is click on the file from a file manager, and a graphical package manager will guide you through the whole process and do it's best to deal with any dependency issues arising form it as well.
That is true, but... as far as it goes, we not even know if his/her distro actually works with rpm, leave it alone knowing if his distro actually has an advanced package manager (it could be Slackware, which can handle rpms as well).
And I second rickh idea, since winamp for linux, as it is right now it is pretty much useless (but that is for the OP to judge). It is good to see such a popular Windows program being finally ported to Linux, however...
That is true, but... as far as it goes, we not even know if his/her distro actually works with rpm, leave it alone knowing if his distro actually has an advanced package manager (it could be Slackware, which can handle rpms as well).
I did qualify with "If you'reusing a fairly advanced RPM-based distribution".
Most desktop distributions that include RPM do also include a graphical front end. There are not many that don't, and if these are not the type of distribution a new Linux user would choose.
Since clicking on the icon from a file manager is the easiest installation method, and will probably work without any problems it is best to try that method first, and if that dosn't work then go back and try something else. Manually entering code to the command line when there is almost certainly no need for it is complicating the process unnecessarily.
Quote:
Originally Posted by Mega Man X
And I second rickh idea, since winamp for linux, as it is right now it is pretty much useless (but that is for the OP to judge). It is good to see such a popular Windows program being finally ported to Linux, however...
The question was about a problem with installing WinAmp, not about XMMS. It helps to note what the question is about before writing a reply.
Manually entering code to the command line when there is almost certainly no need for it is complicating the process unnecessarily.
I have to disagree here. In the case something goes wrong, the console will drop a much better error output than UI will. Many users in this forum, when a program crashes, do not know what happened. Usually, starting the program from the console gives some clues to what went bad.
Quote:
Originally Posted by hand of fate
The question was about a problem with installing WinAmp, not about XMMS. It helps to note what the question is about before writing a reply.
Once again, I disagree. Most users trying to install a program as Winamp (which was initially a windows program) are trying to install _everything_ they can made for win32 in Linux and changes are: They never heard of xmms before. It is always good to show/mention alternatives.
I am not trying to prove you wrong and any way you use Linux is just as right as I do. I am also not going to discuss this with you anymore because it clearly won't lead anywhere and I want to stay on topic...
Last edited by Mega Man X; 02-16-2007 at 02:47 AM.
Yes it is . Not only that but it was Redhat which came up with the rpm system. The OP profile was filled after his initial post though. Now we can see he/she is using Fedora, not when I replied first.
rpm -ivh Winamp-2.a1-1.i386.rpm
error: Failed dependencies:
libstdc++-libc6.2-2.so.3 is needed by Winamp-0.a1-1.i386
If you were using a graphical package manager it would have automatically resolved that dependedcy for you.
Quote:
Originally Posted by bhert
Go to your package manager and install libstdc++-devel It should take care of the dependencies for you. You might have to install gcc++ not sure.
Or just click on the winamp package in a file manager, and all these dependencies will be dealt with automatically.
Quote:
Originally Posted by Mega Man X
I have to disagree here. In the case something goes wrong, the console will drop a much better error output than UI will. Many users in this forum, when a program crashes, do not know what happened. Usually, starting the program from the console gives some clues to what went bad.
If there is a problem installing a package using a graphical package manager, it will produce a dialog box explaining exactly what the problam was, and generally in much clearer terms that what the comnmand line RPM interface would produce.
See above for another reason to use a ghraphical package manager (apart from the obvious fact that making a single click is far easier than manually entering commands). A package manager will atomatically resolve any dependedcies it can, wheras all the command line RPM interface will do is throw up some indeciferable error message and not install anything at all.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.