For testing outside of the build directory, it would be convenient to have $SUBJECT.
This could be used in conjunction with -dumpversion to create on-the-fly include and library directory paths for C++ includes in a sane manner, much like the following: %g++ -print-install-prefix /mnt/share/bld/H-x86-gcc %g++ -dumpversion 4.2.0 Then it'd be trivial to construct things like /mnt/share/bld/H-x86-gcc/include/c++/4.2.0 Anyway. I suppose there's a way to get at this via g++ -print-libgcc-file-name but in the meantime, I'm wondering if there is a much easier way to go about this that I'm currently overlooking. Thoughts? -benjamin