Stop Microsoft
Operating Systems => Linux and UNIX => Topic started by: dishawjp on 15 September 2002, 20:52
-
Hi All,
I hate to keep bothering all of you with stupid questions, but I'm stuck again. I went to download.com to take a shot at installing software on my computer. The download came in as a .tgz file. No problem there, a tar -xzfv uncompressed everything just fine. There was an INSTALL text file in there. I read that, and it suggested using rpm to install. Problem is that there was no .rpm file among the files. The name of the program is icebreaker, and there was an icebreaker.c file. So I tried the "make" command on that. Lots of stuff happened, and I got a "Makefile" text file and a "Makefile.W32" file out of that. No executable files that I can find though.
I could care less about this particular program, but am just trying to learn how to do things with Linux. I've been at this for quite a while and am not making any progress, and have had to resort to imposing on all you good people yet again.
Thanks in advance for any assistance (yet again).
Jim
-
./configure
make
make install
-
Are there any advantages for using
quote:
tar -xzfv
instead of the "extract here" in konquerer? :confused:
-
Different strokes for different folks...
-
Hmmmmmm......you could try apt-get install NO,you can't, that's right, you're using Redhat; my condolences.
-
Hi All,
Thanks for the replies. I can't use Konquerer because I don't have it yet. Still just getting started here.
As for the
./configure
make
make install
are there any arguments I have to add? If so, what. Still VERY green here.
Creedon... haven't done the Debian thing yet. I burned the CD's (and a copy of Knoppix for you), but will continue to beat my head bloody against the wall with this Red Hat thing until I can make it work. :) And make it work for me from the command line. And yes, I AM that stubborn.
I had to help a buddy of mine out today, a local farmer. He has a 1983 Deutz farm tractor that was hurting. I really don't like working on farm tractors. I dislike air cooled diesels even more. And working on a damned foreign made air-cooled diesel farm tractor.. on a Sunday... well, it's enough to drive me to drink. So I guess I will :)
I'll give my Linux box another go maybe tomorrow.
Thanks all for the help; I'm off to get trashed.
Jim
-
quote:
Originally posted by DOSman:
Hi All,
Thanks for the replies. I can't use Konquerer because I don't have it yet. Still just getting started here.
As for the
./configure
make
make install
are there any arguments I have to add? If so, what. Still VERY green here.
Creedon... haven't done the Debian thing yet. I burned the CD's (and a copy of Knoppix for you), but will continue to beat my head bloody against the wall with this Red Hat thing until I can make it work. :) And make it work for me from the command line. And yes, I AM that stubborn.
I had to help a buddy of mine out today, a local farmer. He has a 1983 Deutz farm tractor that was hurting. I really don't like working on farm tractors. I dislike air cooled diesels even more. And working on a damned foreign made air-cooled diesel farm tractor.. on a Sunday... well, it's enough to drive me to drink. So I guess I will :)
I'll give my Linux box another go maybe tomorrow.
Thanks all for the help; I'm off to get trashed.
Jim
WOW!! You ARE a glutton for punishment!! A Deitz!?!?!? DAMN, that's hardcore!!
./configure
make
make install
should work.
(munbles) A Deitz-sonuvabitch!
-
Forget download.com. If it says to use the RPM then also forget the *.tgz file. Get the RPM file of the program. I suggest you go to http://www.rpmfind.net/ (http://www.rpmfind.net/) and get the RPM. Then to install just:
# rpm -Uvh filename.rpm
And did you not install KDE when you installed RedHat? If you did, you have Konqueror.
-
Don't forget, if you downloaded an RPM then you can browse to the file with Konqueror. If you click on it, the RedHat Package Manager starts up. There is an option to "test install" this will let you know if there are any missing dependences. (http://smile.gif) So far, I installed Xcdroast in RedHat without a hitch that way.
-
Hi All,
Yeah Creedon a damned Deutz. About as much fun as trying to fix a Windoze box :)
As for those asking about Konqueror, I went with the Gnome desktop. No Konqueror.
Thanks for the help and I'll give this another shot after work tonight.
Jim
-
well if you did not install kde, but did install gnome then you have galeon? i think that's the gnome file browser... also, you will likely have the gnome package manager, i think it is called grpm [edit - no it's not! it's called gnorpm] on the command line, and it is roughly equivelant to krpm which is what these guys are talking about.
regarding the quote:
./configure
make
make install
this will work fine for most things. the first command uses the configure script to make a Makefile for your machine (based on what compiler you have and so on), the second line runs make (which reads the Makefile you just created and compiles the program), thr third line must be entered as root, so su into root mode and run it. it should either install, or exit printing all the errors. these will typically tell you to install some other stuff that is required before it will allow you to install this program. [edit - is this right, by the way? some people might be able to correct me on some of this...]
personally, i would say rpms might be easier, but if you want to learn (and if you want an install that matches your personal computer/system setup) then you'd be better installing from source.
[ September 16, 2002: Message edited by: Calum ]
-
At the login prompt you should have a selection box that allows you to change which window environment you want to log in with. You have Gnome set as the default, but if you look at the pulldown list and "KDE" is there you have it installed and if you select it you will log in to KDE instead of Gnome.
Also you can run Konqueror in Gnome but it will not be listed in any menu by default. You can run it from a command line (or run box) by typing "konqueror". If you have KDE installed it will run.
-
however if he only installed GNOME and not KDE (not a bad plan, so long as your mouse and so on are supported properly in GNOME), then he will have to install konqueror specifically off the CD to use it, and will not get KDE at said login prompt. Also, he won't even see the login prompt if he chose to login as a particular user automatically when he starts up. however there are graphical rpm tools in GNOME too...
-
Mouse support is not a function of the Window manager but a function of X. If the mouse works in Gnome it will work in KDE. You can not just install "konqueror" alone, you also have to have all the KDE libs and KDE net installed. But it's certainly easy to find out if it's installed, just type "konqueror". If it's installed it will run, if it's not it won't. (http://smile.gif) I'm not trying to tell him to use one Window manager over another as that is a personal preference. I was just trying to give him some pointers on how to try out both and determine whether they both were installed or not. I also suggested that it is far better to use RPMs on an RPM based system if there are RPMs for the particular application he wants to install for several reasons. Things you get with RPM over a source install:
- Ability to check dependencies
- Ability to upgrade/freshen
- Ability to uninstall
- Ability to verify install
- Ability to query
- Checksums
- etc
Source installed software will not be registered in the RPM database on your system and thus becomes it's own little unmanaged entity. Sure there are not RPMs for everything and you will need to install a source only version now and then but if there is an RPM version of it it's to your advantage to use the RPM.
-
good points indeed.
re: mouse support, what's odd then is that whenever i personally run the gnome toolbar, no matter what desktop environment i am in, the mouse goes bloody haywire, and i cannot do a thing!
this is not an issue, i just don't run that particular app.
now back to the subject in hand, i am sorry that i implied it was a case of telling somebody which programs to use, i was really just trying to say that even if he doesn't have kde then he can still use a gui running rpm manager to do the job.
re: konqueror without kde, of course, where is my head at? then again, if one tried to install konqueror, surely they would get errors to the effect that certain libs etc would also need to be installed, and thus they could install whatever was required without needing the full desktop environment, am i right? or just blowing out my ass again? :D
-
quote:
Originally posted by Calum:
good points indeed.
re: konqueror without kde, of course, where is my head at? then again, if one tried to install konqueror, surely they would get errors to the effect that certain libs etc would also need to be installed, and thus they could install whatever was required without needing the full desktop environment, am i right? or just blowing out my ass again?
Well, there is no RPM containing just konqueror. Konqueror is a pretty big part of KDE (which itself is an "environment" and not an application). An "rpm -qif /usr/bin/konqueror" tells me that the konqueror RPM is part of the "kdebase" RPM which include many major components of KDE:
And an "rpm -qR kdebase" shows me a list of things that kdebase depends on. Now konqueror is an extreme example because it is so tightly integrated into KDE which is a very large desktop environment and in the case of konqueror it is not a standalone app that you can just install and use without KDE. But it is something that is a good illustration in the advantages of RPM.
-
Hi Everybody,
Yeah, it's me again... the hopeless newbie. Anyway, I tried the ./configure and got a "bash command not found" error message. So I thought that maybe the "configure" command wasn't on my computer or something. So I did a "find / -name 'configure' - print" and sure enough in the /usr/shared/libtools/libltdl directory there was a configure command. Then I did a "which configure" to see if it was in my path. It returned a "configure not in path" message. So I tried a "set > nnn" and then "more nnn" to check my path. Sure as hell, I didn't come close to there.
Soooo, my questions are: should I modify my path to include the /usr/shared/libtools/libltdl directory, and... please don't fall out of your chairs laughing at this question... how the hell do I modify my path in Linux. My .bash_profile file does refer to my path, as does my .bashrc but neither seems to be the proper one to modify. I would have thought that a file like configure might be in the /etc or the /bin directory, or maybe even the /sbin, all of which seem to have lots of executable files and which are in my path. Should I just "mv" or "cp" configure to one of those directories?
I'm really trying hard to get functional with Linux, and am doing what I can on my own before imposing on all you good people looking for help. I can't tell you how much I appreciate all the suggestions and support I've received here.
Jim
-
I will explain the source installing i bit.
What are you installing??
the configure command is usually include with source distrobution just to check for certain things that the program needs. But configure is usually included with the source so each configure is different. Many programs have the configure command but some dont.
the "./" part of it just means the current directory. "." is the current directory. so 'cd ./' is telling your computer to change directory to the current directory and wont really go anywhere.
Linux doesnt do relative links. which means that you have to put the exact path to a command. that means that you have to use ./whatever if it is in the current directory or ../something if it is the next level down directory or /usr/local/something if it is in /usr/local but you are in some other directory.
I hope that explains a bit (a will look for a link that i had which explains it better).
So you must be in the directory which contains configure to be able to run ./configure.
Other commands that you can run, like 'cd' are in /bin /sbin /usr/bin /usr/sbin /usr/local/bin or /usr/local/sbin because those are usually part of your path which means that if you type 'cd' it will try /bin/cd then /sbin/cd then the others until it finds where the 'cd' command is. But if it isnt in those directories it will say command not found unless you actually type in the full path (I.E. /usr/local/program)
Some programs do not have a configure program. You should make sure to read any documentation that comes with any program before you install it in case it needs any special way to install it. Usually the INSTALL or README file that comes with most programs will tell you exactly how to install it. run the program 'less' to view text files (ie. less INSTALL or less README)
-
http://home.c2i.net/dark/linux.html#compile (http://home.c2i.net/dark/linux.html#compile)
here is the link that would be a good place to look.
-
Again I ask why not just get the RPM and install it? Of course if you are just doing this for the exercise of learning how to isntall non-RPM packages then press on. Regarding your path, yes, add to the "PATH" in the ~/.bash_profile separating directories that you add with a colon ":".
Another note, if you add the "." directory to your path you will not have to use the "./" in front of the name of an executable program residing in the current directory. However, I would not suggest this and would suggest that you instead get in the habit of prepending the "./" when executing programs in the current directory. It's more secure.
-
Once again, thanks. Bob, to answer your question, the program is just a stupid little game I downloaded. It's called Icebreaker. You're supposed to save some penguins or something. I'm doing this just for practice; to help me learn Linux. If there were a way to do it by double clicking on an icon, that's not the way I would want to do it now.
I probably screwed myself by picking a bad file to play with. There was no configure file after I expanded (right word?) the .tgz file. The README just talked about how to play the game, and the INSTALL file was about 2 sentences which were no help to me at all. It mostly talked about doing a rpm install and there were no .rpm files in the package. MoR/Bob, the site you pointed me to is excellent. I'm beginning to build an excellent library of internet resources for Linux thanks to you people here. I'm updating my web page now. Originally it was a sort of pro-DOS anti-Windows page, but I'll make it more of a pro-command line, anti-Windows page. I hope to be able to incorporate these links I've been provided with into some coherent form to help me and other newbies wade through the complexities of Linux.
Thanks again for all the help. I'll probably have to give up on this particular program, and try to download and install a different one.
Void Main, after I finally successfully install this type of a package, I'll be moving on to .rpm formats. I'm doing all this just to learn. Maybe someday I'll be able to help other Linux newbies. With WinXP out there, there should be lots of Linux newbies soon :)
Jim
-
if you want to download and install a silly little game, then get xbill. it is very very good, is small and simple, there's an rpm available for it (which you can install at the command line) and i am sure it is open source, so you could get a .tgz file of it too. i also know that it comes as windows binaries in a zip file.
also, once you have this game, you need not get any other games for linux. ;)
i think red hat actually include this on their distro, so if you use red hat, you might already have it installed, which kind of spoils the fun a bit...
-
Sorry All, B
But I guess I really am an idiot. I gave up on icebreaker, downloaded dopewars as a .tar.gz file. No problem. It installed and runs and everything is great. The ./configure and make and make install all worked fine. So I decided to try a few simpler things and got some .rpm files. In particular, I got Icebreaker and xbill as .src.rpm's . I tried the "rpm -Uvh (filename)" on both of them, and no luck. Red Hat whined a bit about permissions, so I tried the "su - root" and did it again and it sort of croaked and did a lot of nothing. No unpacking or anything. Also no executable file found by "find."
I got both of these files from rpmfind.net, but neither would install. For giggles, I did type gnorpm at the command line and some sort of a GUI thing started up. I didn't know what to do with it and really don't like GUI interfaces much anyway, so I jussst shut it down.
Anyway, three of my former students took me out tonight for wings and beer. After four hours in a bar with them, maybe the problem is with me and not with Linux or the downloads.
Darned kids getting us poor old men drunk and all; have they no shame :)
Anyway, consider this a progress report. I can now download and unzip and untar programs, but now can't install a simple .src.rpm file. As braindead as this sounds, it is progress for me.
Damn! Out of beer! Need to run downstairs for another beer (or three). Thanks everyone for all your help. I'll get this Linux stuff yet... even if I have to drink all the beer in the northeast US to do it :)
Jim
-
It's all in the name. *.src.rpm is a "source" RPM. The "rpm -Uvh" command is meant for an installable binary RPM (*.i386.rpm, etc). But if you wanted to actually use the source rpm to build the binary RPMs and then automatically install the freshly build RPM you would:
# rpm --rebuild xbill.src.rpm
If you would have downloaded the binary RPM (xbill.i386.rpm for example) you would use this command:
# rpm -Uvh xbill.i386.rpm
Now in order to install the source RPM in the way I mentioned in the first example you must have the appropriate development tools installed and the rpm-build RPM must also be installed. The best way to test if you have everything necessary to manipulate *.src.rpm files is to just try the first example. If it gives you an error let me know and I can help you get the necessary things installed.
A side note, if you wanted to just unpack the source RPM and perform individual steps (prep, compile, build, install) separately you would install the RPM like so:
# rpm -i xbill.src.rpm
Which will put the source under the /usr/src/redhat/SOURCES directory and it will put a file in /usr/src/redhat/SPECS called "xbill.spec". Change into the /usr/src/redhat/SPECS directory and do a:
# rpm -bb xbill.spec
which will build the xbill.i386.rpm file and place it in /usr/src/redhat/RPMS/i386 directory after it installs it. This is all assuming you are on an i386 architecture. For more info on these build options do a "man rpm" and toward the bottom of the page search for the "BUILD OPTIONS" section.
-
Similar Problem:
I can't get SDL-perl to install.
I type:/home/Dustin/Perl/configure
It says: ""Makefile.PL": No such file or directory"
Meanwhile the file is right there in the same directory...WTF?
-
Did you read the directions that came with it? Usually there is an "INSTALL" or "README" that comes with any package with step by step instructions.
If it is a Perl module that you are compiling then usually the steps are different. Be sure to check the docs but from memory you would usually change into the directory where the module source resides and do something like:
# perl Makefile.PL
# make
# make test
# make install
If there is an executable file called "configure" in the directory that the source was extracted to then you would change into that directory and usually type:
# ./configure
# make
# make install
However, with source packages that come in a tar ball your mileage may vary. You have to follow the directions in the doc as it is all up to the programmer that created the source as to how it should be built and installed. Good programmers follow the examples above. Not all programmers are good, look at Bill Gates.