Mtune

make install
make install-recursive
make [1]: Leaving directory `/ root / Desktop / verlihub / verlihub '
Making install in src
make [2]: Leaving directory `/ root / Desktop / verlihub / verlihub / src '
If the mode / bin / sh .. / Libtool - = compile g + +-DHAVE_CONFIG_H-I. -I. -I .. G-O2-I
/ Usr / src / include / -I/usr/include/mysql-g-pipe-Wp,-D_FORTIFY_SOURCE = 2-fexceptions
s-fstack-protector - param = SSP-buffer-size = 4-Mar-M32 = i386-mtune = generic-Fasi
nchronous-relaxation-tables-D_GNU_SOURCE-D_FILE_OFFSET_BITS = 64-D_LARGEFILE_SOURCE-f
non-strict-aliasing-fwrapv -I/usr/local/include-MT casyncsocketserver.lo-MD-MP
-MF. "Deps / casyncsocketserver.Tpo" \
Casyncsocketserver.lo-Co `test-f '| | casyncsocketserver.cpp echo'./'` casync
socketserver.cpp; \
then mv-f ". deps / casyncsocketserver.Tpo. deps / casyncsocketserver.Plo" \
else rm-f ". deps / casyncsocketserver.Tpo" exit 1; \
fi
g + +-DHAVE_CONFIG_H-I. -I. -I .. G-O2 -I/usr/src/include / -I/usr/include/mysql -
g-pipe-Wp,-D_FORTIFY_SOURCE = 2 -

What is the error message? What you pasted was only the first part of the compilation output. This is normal. What if it is not the compilation stops and gives you an error message. If you did not commit a single error msg when running the application. Unfortunately, some facilities archive includes the addition to the program interface. So you must manually add it to your menus. Not hard to do. The most likely target is dir / usr / bin or / usr / local /] appname [

This is the last lines are signficant. You'll often get pages and pages of output during compilation. The more complex the program the most complex production in general. For most people this is nothing more reassuring to the compilation is still ongoing. If you have a programming background, he can tell you much, but reading the source will tell you all this so that even the programmers are not normally pay much attention to what if something goes wrong.

possible problems dependencies. Missing libs for example. If this is the case do a Google on missing libs to see what package they come. Download the appropriate archive and / or RPM. Another easier way is to ensure first time this application is not in a yum repository or shape rpm. I compile MySQL, Apache, PHP and a few other applications from the archive because I do not like the configuration of the RPM and you want to customize a lot more with these applications. Sometimes, compiled from the archives of the applications are much more efficient. Depends on how the plan was created and how it is specific to your distribution. Everything else, if I do I do in RPM format.

If the error message is not a dependence that could not be an environment variable missing. Again, it's pretty easy to fix. It is generally documented in the README file in the src directory.

If all else fails, I usually delete the whole package and try something else that does the same thing. Most developers to respond immediately to problems compiling and there may already be a solution to your problem waiting on the site you downloaded the application from.

Again, no actual error message hard to say what was wrong if anything.