Section 2.4: Download Up Chapter 2: Install Section 2.6: Connect 

2.5 Build

2.5.1 configure

After unpacking a tarball or updating an existing source application from CVS, you can change to the install directory and run the configure script.
Part of the autoconf tools suite of tools, the configure program is crucial to installing many applications and seeks out existing installed products and does what is necessary to link them to your target application. For both binary and source installations you should run autoconf to check that Aubit4GL will find all its sister libraries. Some useful command line examples:
./configure --help
./configure --prefix=/local
./configure ... > config.out
./confgure --with-pdf=/local
Whenever you run ./configure it writes to config.log. This is a very verbose (more than 7000 lines) log of all its actions and it can give you a precise indication of what it is doing to find each component.
When you redirect output to config.out, you get a 500 lines or so resume of lost and found elements. e.g.:
checking for main in -liksemel... yes
checking if we can use IksEmEl... yes
...
checking for main in -lsxml... no
checking sxml.h usability... no
checking sxml.h presence... no
checking for sxml.h... no
checking if we can use SXML... no
Use these file to determine if Aubit4GL is finding all the installed elements you expect it to find.

2.5.2 Binary

Nothing to do!
Mike has already done the hard work for you. If you are lucky and yours is the same distribution as his then the system libraries will have the same names. Otherwise, you will either have to create synonyms for them or abandon the binary and install the source instead.

2.5.3 Source

Having downloaded the source, whether from a tarball or via cvs

2.5.3.1 Missing Software

Run the configure script to see which of these you have (or don’t have) in config.log:
./configure --prefix=/local/opt/aubit4gl > config.out
Look in config.out or in config.log (for more verbosity) for what configure found and missed. Don’t be too concerned if there are many things missed. e.g. you need at most one ODBC (on Linux: unix-odbc or iodbc). Similarly you will likely not need an ESQLC application for postgreSQL or SQLite3 or MySQL.
When config.out or config.log shows that you are missing something that you want, e.g. Jabber you will see what configure is looking for (in the case of Jabber: iksemel). Use your OS packet management software to search for and install the missing application and then run ./configure again.
On Linux systems the command rpm -qa will give you a (huge) list of all software installed using rpm (RedHat Package Manager). To find any rpms related to iksemel run the the following:
rpm -qa | grep -i iksemel
iksemel-1.3-0
iksemel-devel-1.3-0
On Linux systems you can find non rpm installed software with the locate command:e.g.
locate pdf
 Section 2.4: Download Up Chapter 2: Install Section 2.6: Connect