I meant to add too that this perhaps raises an even larger question in
pkgsrc of how buildlink2 might be leveraged to provide support for
generally using an arbitrary C (or C++) compiler (eg. lang/gcc-ssp, or
perhaps some commercial compiler) without having to modify things too
much.

I suspect one could do this now with at least lang/gcc by defining
USE_PKGSRC_GCC and including lang/gcc/buildlink2.mk in /etc/mk.conf,
though (I've not tested this idea yet).  That seems pretty hackish
though and even though it would allow for gcc variants like gcc-ssp if
the issues in my initial post are addressed, it doesn't allow for
arbitrary compilers to be controlled with the same framework.

-- 
								Greg A. Woods

+1 416 218-0098;            <g.a.woods@ieee.org>;           <woods@robohack.ca>
Planix, Inc. <woods@planix.com>; VE3TCP; Secrets of the Weird <woods@weird.com>