Use your favorite web browser and google up a copy of 'Newbies Linux Manual' to get you started on the adventure of a lifetime.
Path: there's a file (/etc/ld.so.conf) which lists the directories bash should search to find executable files, libraries, etc. Use the which command to find gcc, the c compiler (open a terminal and enter the command 'which gcc'). When you have the path to gcc, edit the file named above to add that, then give the command PATH=/usr/bin/gcc, or whatever the path is, then follow that with the command 'export $PATH'.
Exporting the PATH is a temporary solution which lasts only as long as you are logged in. Editing the /etd/ld.so.conf file is permanent. It will be there every time you log in.
Now, with regard to ./configure, make, and make install. When you unpack a tarball, it creates a folder which contains the files it will install or use to make binary files. You must do one of the following for it to work: cd to the folder, or, from the folder you 're in, give the full path to the folder. Same for make and make install.
example: let's say you're in your home directory ~, but the tarball is in /usr/local. Either you cd to /usr/local and give the command ./configure, or you stay in your home directory and give the command /usr/local/.configure. That tells bash where the configure script is (the ./ tells bash that the script is in the current working directory. If you are not in the directory where the configure script is located, then bash gets confused unless you give it the full path to the file).
The same applies to the make and make install commands. Tell bash where they are, and they'll run.
By the way: SuSE is rpm based. To install rpm, use the rpm -i command. The ./configure,make,make install only applies to tarballs (files that end in the file extension .tar.gz or .tgz).
Last edited by bigrigdriver; 09-15-2004 at 04:01 AM.