Why are you running the make as root? If you ran the configure as a regular user, then changed to root to run the make, that could account for it.

I'd recommend running the ./configure and the make as your regular user account and then become root purely for the make install.

That was me. Dunno why it anonymous-ed me ...

Spooforbrains: your logic doesn't hold here.

Root only has greater PERMISSIONS than normal users; i.e. permissions over EVERYTHING.

Root would create the makefile, just as any other user. The problem seems to be that it's not there. That is NOT dependent upon the user.

I, myself, am always root when I'm compiling for all users. It makes no difference in the long run for normal programs, and the programs it makes a difference for should be fixed to behave properly.

recruit: this isn't your issue, I would look for other things.

I had followed the instructions in the README doc:

"LogJam has a pretty standard setup.
Running:
$ ./configure
$ make
$ su
# make install
should be all you need to install it."

When the make cmd have me that error, I tried following the subsequent steps just for the heck of it. That's why I entered su mode. I repeated the make cmd again and copied that text to post.

I'm about to read later comments and try some of that out. :)

this is, in fact, what's reccomended for much of Linux From Scratch's build process - though I still need to get one of those built (: Started last year about this time, too ):

Take a closer look at the output of the configure script. It probably did not actually complete successfully.

Which distribution are you using? It is very likely that there are packages of Logjam for it.

I second the comment about installing as root, seems a little odd.

But, I suspect you didn't give make a target. Try make install. That is, "make install" without the quotes. Not just make.

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:

make

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.
mkdir [whatever]

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]
or
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:
script [logfile]

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
cd [whatever]

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.

Bah. What can I say, it's well past my bedtime :-P

The other possibility is that he's not in the same directory as the makefile generated was. Actual failure to create the makefile *should* be relatively obvious.

But yeah, post the log...

Thanks, cheesetruck!

Here's the link: http://pastebin.ca/288673

From what I see, it did not configure as some requirements were not met. Now I just need to figure out how to meet or avoid the calls.

You've got it - you're missing GTK:
====
#
checking for LOGJAM... configure: error: Package requirements (gtk+-2.0 >= 2.4 glib-2.0 gobject-2.0 libxml-2.0 gthread-2.0) were not met.
====
GTK is one of the graphical toolkits that is often used to make gui-based programs for systems with Xwindows (like Linux.) There are others, but, that's not important right now.

Mandriva undoubtably has some form of system for installing packages like this - GTK is very common, and you'll use it for several other programs. So see if you can find the Mandriva install system, and install GTK.

I, myself, don't use Mandriva, so I don't know if they use a rpm (redhat package manager) type system, a apt type system (debian's package system), something like slackware's 'we just have tarballs' system, or something like pacman (arch) or portage (gentoo) - there are a LOT of these methods of installing/uninstalling/upgrading. They all fill the purpose of "keeping your system up to date AND letting you get on with things instead of needing to worry about dependencies."

dependency problems are things like "need gtk installed to install logjam" - so you can see why this is something that a lot of people prefer over 'build it yourself' methods.

But mass props for trying to build it yourself - you'll learn a LOT that way. (Hopefully what everyone said here is helping - it's all good stuff, even if some of it was not exactly right - you can be MOSTLY right with unix and still have a working system (: )

Oh, and, you won't want to AVOID the calls for gtk - as it's the graphical toolkit used, you would not have anything opening the window, managing the graphical widgets, etc...

www.gtk.org , I believe, is their webpage. You may be interested in knowing EXACTLY what it does before installing it (:

Just to make sure: did you run ./autogen.sh before ./configure?