Honestly.. If your code compiled cleanly, but you aren't passing make test, I would complete the compilation (make install), and then write a quick script to access a DB and pull a line from a table. If that doesnt work, then I would roll back and try again.

I've been doing sysadmin work for a few years now, and find that some (make test)s, don't acurately poll the system, or do not have as robust a "test" suite as I would like. As long as during configuration/compilation I do not see errors, for the software itself or components I need, I attempt a make test. If after clean compilation, make tests moan, I generally install and then right my own tests.. Sometimes quick ones, other times I've spent alot more time that I should testing.. It all depends on the module/software in question.

Try a make install, make sure you can use the methods you need to get your job done now, get that done, then decide if you really need make test to finish clean.. If so happy hacking, if not happy hacking :)

/* And the Creator, against his better judgement, wrote man.c */