Trace The Variables
Most of the problems with installs come when variables don't behave the way you'd expect. The usual problem for GAR is the installation directory variables. Many packages simply set things manually never expecting anyone to need to override them.
So often you have to trace through the build process looking to see where the variable gets its info. The typical path (and possible problem points) is as follows:
- configure script
- Try reading the configure.in to see if the author put in any raw shell code (instead of using standard AC_ macros). If that doesn't give you the info you need, try Configure With Verbose Shell.
- Makefile
- grep through for variable assignments. Note that things set up for substitution in the configure script will substitute @atsignvars@ with their values from the Makefile.in, so keep an eye on that. Often you need to Install Override Dirs in order to change one of these vars at install-time (as opposed to build-time). Be on the lookout for dir variables used in Makefile.in install-foo steps that don't have DESTDIR!
Remember the path goes from CONFIGURE_ARGS -> configure -> Makefile.in -> Makefile
Most often, the way to proceed once you've found the variables you want is to override make variables