I've implemented a "make install" target in the Makefile, based on what was in the rpm specfile. This is slightly complicated by the fact we now have the gcc-c-api layer. This builds as gcc-c-api/libgcccapi.so which the plugin links against. So when running the plugin from a working copy, use LD_LIBARY_PATH=gcc-c-api so that the plugin can find its libgccapi.so there. This is already done by the Makefile targets that run the plugin, via INVOCATION_ENV_VARS := LD_LIBRARY_PATH=gcc-c-api When installing, both the plugin and libgccapi.so will be installed to GCC's plugins directory (e.g /usr/libexec/gcc/x86_64-redhat-linux/4.7.2/plugin/ on this machine) so we give the plugin an RPATH that points at that directory so that it finds the libgcccapi.so there (to support the case of having multiple GCCs installed). Ultimately I hope to move gcc-c-api out from the plugin's source tree and into its own project once it's proven itself, but the above approach seems to me to be a good way forward in the meantime. I'm working on getting the plugin to work fully with GCC 4.8 (or at least the build from SVN I have on my machine) and hope to do a new release soon, so please let me know if I broke anyone's builds of the plugin in the above! Cheers Dave