Source Code

dvong3 · 07-13-2003, 02:33 AM

How do we know file are source code or pre-compiled package? IF source code, what steps do I need to compile ? I am trying to install ssh.

whansard · 07-13-2003, 03:35 AM

the place you download the file from has to tell you.
the instructions for compiling often vary, but the instructions
are almost always contained in the README or INSTALL
contained within the tarball.

s_nic · 07-13-2003, 01:17 PM

Compilling from source almost always involves opening up a terminal (GNOMEterm, Konsole, rxvt, etc) and:

Code:

$ cd source directory (what was extracted from the tarball)
$ ./configure
$ make
$ su
enter root pass
# make install

The configure script checks your environment, checks for a compiler, and for other dependencies. It also generates the makefiles needed to compile the source. make compiles, and them make install shifts everything to a nifty place. Usually files for the program to run eg sounds, images, and configuration files to /usr/local/share, and then the executables to /usr/local/bin. You can change the prefix of the install manually though.

However, ALWAYS, ALWAYS read the README and INSTALL files. Most tarballs contain generic INSTALL files. You can tell by the "These are generic installation instructions" line

README's are never the same, and you should ALWAYS read them.

Either of these documents can contain possible parameters for configuration/compilation. So read them or it's your fault :P

MasterC · 07-13-2003, 01:20 PM

Ocassionally the precompiled binaries will also use this similar process though. Sometimes a name will give it away:
great-application-5.1beta-i386.tar.gz is most likely a precompiled binary (not source) where:
great-application-5.1beta.tar.gz is more likely source. Also, if when you open up the tarball if there is a file that you can:
./filename
to run the program, this is a precompiled binary. If you open up your tarball and just see a bunch of .h and .c files, this is more likely source.

COol