On Sunday 14 March 2004 11:46, Graham Trott wrote:
On Sunday 14 March 2004 07:36, IanBell wrote:
On Saturday 13 March 2004 23:32, Wayne Cornish wrote:
On Sat, Mar 13, 2004 at 10:11:17PM +0000, IanBell wrote:
- type ./make this compiles the programme and should result in an
exectuable
4 type ./make install this installs the executable and any other necessary files in predetermined directories.
I think you mean "make" and not "./make". Including the dot and slash, "./", will make the shell try to run "make" from the current working directory, and not search $PATH for it.
Wayne.
Whoops, quite right Wayne.
Ian
And re the "make install"; it's often necessary to be root, so do
su -m
first. The plain su resets environment variables but -m keeps you in the same directory and with your environment variables unchanged, only with root privileges. This is useful if you need to run programs that aren't on the system path, such as kwrite.
Most packages will complain if they needed to be installed as root.
-- GT
Whoops another booboo on my part. In my experience virtually all packages need root privilidges to iinstall because the executable is normaly placed somewehre under /usr (to which non root users cannot write). So, unless you intend to install files in your home directory, you will need to be root.
As an aside, this process is usually described in the readme or install file of the source. it is always worth reading these both before compiling just in case there are some oddities (and there often are).
Ian