Well, probably the installation went wrong. Depending on what it exactly was, it could be anything
1) don't run make unless configure is successful (you probably even can't run make, or at least it won't finish in this case).
2) even if you could run configure, or nevertheless ran make; if make doesn't finish successfully = without errors,
do not run make install. Actually the install step depends on the makefile, but it's pretty common. Make step creates the binaries. Make install step then copies the compiled binaries and other needed files in place in your system -- you don't want to do this if the compilation went wrong.
I'd start off by removing the compiled software. If it supports an uninstall-makerule, try doing this in the source directory:
if it doesn't work, then you'll just have to hunt the files manually. After it try to re-compile it, and this time make it right; if an error is produced, you
will want to know why it was produced, then fix it and only then go on.
On Windows you might just go ahead and ram against the wall installing anything you like, and the same goes for most binaries, but whenever you're dealing with source code, remember that it's not "usable" before it is successfully compiled; installing unusable software is pretty stupid. In my opinion you shouldn't be able to run make install unless the previous make step produced zero errors, but that's up to the developer and in some cases it's impossible or very difficult to implement.
Try to stick with binary installations if you can, and if you need to compile something, do it well. Don't hurry, it's not going to help anybody.