5.3. Testing and installing gnome-pilot

On most systems, gnome-pilot will already be installed, and may be functional, so this build will overwrite the existing copy with a new copy (possibly a newer version, but it MUST go in the same $PREFIX as GNOME itself)

When the 'make' completes, it should return successfully with the following last few lines of the 'make' command:

creating gpilotdcm-client make[2]: Leaving directory `/home/hacker/build/gnome-pilot-2.0.10/utils' make[2]: Entering directory `/home/hacker/build/gnome-pilot-2.0.10' make[2]: Leaving directory `/home/hacker/build/gnome-pilot-2.0.10' make[1]: Leaving directory `/home/hacker/build/gnome-pilot-2.0.10'

As before with pilot-link, su to the root user using 'su - root' and cd back into the gnome-pilot-2.0.10 directory and install gnome-pilot.

hacker@druid:~/build/gnome-pilot-2.0.10$ su - # switch to the root user druid:~# cd /home/hacker/build/gnome-pilot-2.0.10 hacker@druid:~/build/gnome-pilot-2.0.10# make install

Install for gnome-pilot should terminate successfully with the following last few lines:

/bin/sh ./mkinstalldirs /usr/lib /usr/bin/install -c -m 644 ./gpilotConf.sh /usr/lib/gpilotConf.sh make[2]: Nothing to be done for `install-data-am'. make[2]: Leaving directory `/home/hacker/build/gnome-pilot-2.0.10' make[1]: Leaving directory `/home/hacker/build/gnome-pilot-2.0.10' hacker:~/build/gnome-pilot-2.0.10$

Now let's check to make sure that the version we just built was successfully installed in the right location, and is functional:

hacker@druid:~/build/gnome-pilot-2.0.10$ ./gpilotd/gpilotd --version gpilotd-Message: gnome-pilot 2.0.10 starting... gpilotd-Message: compiled for pilot-link version 0.11.8 gpilotd-Message: compiled with [VFS] [USB] [IrDA] [Network] Gnome gnome-pilot 2.0.10

So far, so good. We see version 2.0.10 and that it was built against 0.11.8 of pilot-link. On to the next step!