On Thursday 05 October 2006 09:31, Ralph Stoker wrote: > On Wed, 04 Oct 2006 22:03, Nick Rout wrote: > > This is a common question for people new to compiling. The short answer > > is that if it finishes the program should run. of course they way to test > > that is simply to run it (which can usually be done prior to "make > > install" by simply running it from the directory where "make" has left > > it. > > The executable file is created in the src folder. > > On clicking the .exe file nothing happens. > > When I try the run command an error returns #unknown host saballistics > > trying the make install returns the following > > [EMAIL PROTECTED]:~/Desktop/saballistics-1.3.2/saballistics-1.3.2> make > install > Making install in src > make[1]: Entering directory > `/home/ralph/Desktop/saballistics-1.3.2/saballistics-1.3.2/src' > make[2]: Entering directory > `/home/ralph/Desktop/saballistics-1.3.2/saballistics-1.3.2/src' > /bin/sh ../config/mkinstalldirs /usr/local/saballistics-1.3.2/bin > /usr/bin/install -c > saballistics /usr/local/saballistics-1.3.2/bin/saballistics > /usr/bin/install: cannot remove > `/usr/local/saballistics-1.3.2/bin/saballistics': Permission denied > make[2]: *** [install-binPROGRAMS] Error 1 > make[2]: Leaving directory > `/home/ralph/Desktop/saballistics-1.3.2/saballistics-1.3.2/src' > make[1]: *** [install-am] Error 2 > make[1]: Leaving directory > `/home/ralph/Desktop/saballistics-1.3.2/saballistics-1.3.2/src' > make: *** [install-recursive] Error 1 > [EMAIL PROTECTED]:~/Desktop/saballistics-1.3.2/saballistics-1.3.2> su > Password: > ralph:/home/ralph/Desktop/saballistics-1.3.2/saballistics-1.3.2 # make > install Making install in src > make[1]: Entering directory > `/home/ralph/Desktop/saballistics-1.3.2/saballistics-1.3.2/src' > make[2]: Entering directory > `/home/ralph/Desktop/saballistics-1.3.2/saballistics-1.3.2/src' > /bin/sh ../config/mkinstalldirs /usr/local/saballistics-1.3.2/bin > /usr/bin/install -c > saballistics /usr/local/saballistics-1.3.2/bin/saballistics This is the executable file. It's created a family of subdirectories in /usr/local into which it has to put all the components of the package.
> /bin/sh ../config/mkinstalldirs /usr/local/saballistics-1.3.2/share > /usr/bin/install -c -m 644 > bullet.dat /usr/local/saballistics-1.3.2/share/bullet.dat > /bin/sh ../config/mkinstalldirs /usr/local/saballistics-1.3.2/share > /usr/bin/install -c -m 644 > bullet.dat /usr/local/saballistics-1.3.2/share/bullet.dat > make[2]: Leaving directory > `/home/ralph/Desktop/saballistics-1.3.2/saballistics-1.3.2/src' > make[1]: Leaving directory > `/home/ralph/Desktop/saballistics-1.3.2/saballistics-1.3.2/src' > make[1]: Entering directory > `/home/ralph/Desktop/saballistics-1.3.2/saballistics-1.3.2' > make[2]: Entering directory > `/home/ralph/Desktop/saballistics-1.3.2/saballistics-1.3.2' > make[2]: Nothing to be done for `install-exec-am'. > make[2]: Nothing to be done for `install-data-am'. > make[2]: Leaving directory > `/home/ralph/Desktop/saballistics-1.3.2/saballistics-1.3.2' > make[1]: Leaving directory > `/home/ralph/Desktop/saballistics-1.3.2/saballistics-1.3.2' > ralph:/home/ralph/Desktop/saballistics-1.3.2/saballistics-1.3.2 # > > bad program, operator error or missing link?? missing link. You _might_ get it to go by making a link from a directory in your $PATH to the executable. ln -s /usr/local/saballistics-1.3.2/bin/saballistics /usr/local/bin > As an aside to this problem...when I down a .tar.gz file application file > where should I extract it to?... It doesn't matter, as long as you have permission to use that part of the file system as yourself. > I generally download files to my desktop... > and in this case I extracted it to my desktop too. That's fine as long as you don't mind the 'litter' of your working directories appearing on your desktop. > ...or does it not really matter to where it is extracted... Correct. > the program on compiling selects the appropriate directories? Correct again, but the correctness of the selection made by the program's author varies considerably. If the package is configured by the GNU Automake system you can discover this by running the ./configure script with the --help option. Usually you can change the installation directory with the PREFIX configure flag. In your case you might like to have PREFIX=/usr/local as an option to the ./configure script. -- CS
