Hmm, loads of confusion here on how make works (:
From the make manual:
To prepare to use make, you must write a file called the makefile that
describes the relationships among files in your program, and the states
the commands for updating each file. In a program, typically the exe-
cutable file is updated from object files, which are in turn made by
compiling source files.
Once a suitable makefile exists, each time you change some source
files, this simple shell command:
suffices to perform all necessary recompilations. The make program
uses the makefile data base and the last-modification times of the
files to decide which of the files need to be updated. For each of
those files, it issues the commands recorded in the data base.
make executes commands in the makefile to update one or more target
names, where name is typically a program. If no -f option is present,
make will look for the makefiles GNUmakefile, makefile, and Makefile,
in that order.
In short, he's missing the makefile, the one that configure SHOULD have produced. He doesn't need a target - yet.
He does need a makefile... configure SHOULD have made one... so I agree with broonie that the configure probably didn't compile successfully.
Recruit: How about doing this -
1. know where the tarball (the .tar.bz2 or .tar.gz file you're building the source from.) - full path. If you're not sure what the full path is, do:
a. change to the directory where the 'tarball' is.
b. type 'pwd'
your full path is the result of the 'pwd' command plus the filename.
'pwd'- stands for 'print working directory' - 'working' in this case meaning 'the directory you're in, where you're doing work'
2. change to a temporary spot - I prefer /var/tmp - and make your own temp dir.
where whatever is any name you wish. Because I do this quite often I tend to use 'q' as the dirname, as it's easy to type. You will, more than likely, NOT be untarring 80 tarballs an hour, so you can name it 'logjam-temp' if you like.)
- and untar the file:
tar -xjvf [logjamtarball.tar.bz2]
tar -xzvf [logjamtarball.tar.gz]
Replace [logjamtarball.blah.whatever] with the full path to the file.
tar -x = extract, -z = use zlib compression, -j = use bzip2 compression, -v = verbose (or view more detail if you like) -f "use the following phrase as the tarball filename"
you'll see the files unpack, and they SHOULD unpack into their own directory.
4. Tell linux that you want to make a log of everything you do for this install:
Anything you type, or that a program sends to the screen (stdout, stderr) gets captured. This is going to help everyone who's interested in fixing the problem.
5. change to the temp directory you made before
6. repeat the process you went through before - configure, make ...
7. After this is done, hit control-d. (hold down control and type d.) That ends the 'script' recording session.
8. go to http://pastebin.ca/upload.php
and upload the log file. Follow the instructions there, get the resulting url, and post it for us to review.
Then we'll all be able to see the full log of everything, and do less guesswork. Because everyone
here is giving good suggestions according to their general knowledge and familiarity - but without the full log, it's not that easy to determine what went wrong.