compilation tips and tricks

Owned by Paul McCullough (Unlicensed)
Last updated: Mar 08, 2011Version comment

Here are some common problems I encountered when compiling fossg C libraries.
This includes geos and proj.4.

ON centos, when I issued the make command I saw this:

../../../libtool: line 1223: g++: command not found

The googles suggested

yum install gcc-c++

which worked first time.

If the output from "make install" included the following
----------------------------------------------------------------------
Libraries have been installed in:
/usr/local/lib

If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the `-LLIBDIR'
flag during linking and do at least one of the following:

  • add LIBDIR to the `LD_LIBRARY_PATH' environment variable during execution
  • add LIBDIR to the `LD_RUN_PATH' environment variable during linking
  • use the `Wl,-rpath -Wl,LIBDIR' linker flag
  • have your system administrator add LIBDIR to `/etc/ld.so.conf'

See any operating system documentation about shared libraries for
more information, such as the ld(1) and ld.so(8) manual pages.
----------------------------------------------------------------------
you need to do this:

echo '/usr/local/lib' >> /etc/ld.so.conf.d/local-lib.conf
ldconfig

If things get ugly and the simple steps above do not work, you can use a buckshot approach.
Obviously this should be avoided.

> yum install gcc
> yum install make
> yum groupinstall "Development Libraries"
> yum install glibc-headers glibc glibc-commonglibc-devel
> yum update glibc glibc-common glibc-headers glibc-devel

Lather, rinse, repeat as needed.
You should eventually see no errors and no dependency check failures.