4.2. Some common pilot-link errors

Depending on your system, and the requirements it may have, you may receive one or more errors, below are examples of some common errors you might receive, and solutions to solving them.

If you should get an error that looks like the error below, you are missing the development headers for the 'readline' package.

checking for add_history in -lncurses... no checking for add_history in -lcurses... no checking for add_history in -ltermcap... no checking for add_history in -lterminfo... no checking for add_history in -ltermlib... no checking for readline... not found configure: error: Development headers for readline were not found. Please correct.

On Debian, the proper package is called libreadline4-dev. You can find out what the proper package is by doing the following:

hacker@druid:~/build/pilot-link-0.11.8$ apt-cache search libreadline | grep dev libreadline4-dev - GNU readline and history libraries, development files;

So on a Debian system, you would install the 'libreadline4-dev' package as follows:

# apt-get install libreadline4-dev

On a Red Hat system, this package is called 'readline-devel', and you would install it using whatever facilities your distribution provides for installing this package (rpm, apt-get, urpmi, rc, or others).

After installing the missing headers and library packages, re-run configure again. It should complete cleanly. If it doesn't, see if you can find what it is missing, and install it.

checking for add_history in -lncurses... yes checking for readline... found checking for basic readline functions... yes checking for extra readline functions... yes

If configure completes cleanly, you should see the following output:

Options detected/selected -------------------------. pilot-link version...... : 0.11.8 libpisock version....... : 8.0.5 libpisync version....... : 0.0.1 Build for host.......... : i686-pc-linux-gnu Extra Warnings.......... : no Direct USB support...... : yes, Linux ElectricFence checks.... : no CFLAGS.................. : -g -O2 CXXFLAGS................ : -g -O2 -Wno-deprecated Internal Language Support -------------------------. C++ support............. : yes Iconv support........... : yes PNG support............. : no Readline support........ : full External Language Support -------------------------. TCL support............. : no Java support............ : no Python support.......... : no Perl support............ : no

There are a couple of things there that you might want to look into. The first is that PNG support was not detected. A couple of the pilot-link conduits use PNG to output image files of that type. If you want the best-quality images, it is advisable to get the PNG support working. You can get that with the proper libpng-dev package for your distribution, if it doesn't already have it installed. Below is how it would be installed on a Debian system:

# apt-get install libpng3-dev

Re-run configure again, and see if it finds the PNG support this time. If you installed the right package, it should find it:

PNG support............. : yes

Now you can type 'make' to build pilot-link. It should building cleanly, given that all of the dependancies have been found and are tested to function properly.