somewhere I remember reading a request to list portage packages that fail to build with DragonEgg. This is a list of packages that fail to build with CFLAGS="${CFLAGS} -fplugin=/usr/lib64/llvm/dragonegg.so", but succeeds when it is commented out: kde-base/nepomuk dev-lang/ocaml dev-lang/ruby-1.8.7_p357 dev-lang/ruby-enterprise-1.8.7.2010.02-r1 app-office/libreoffice-3.5.2.2 media-libs/xine-lib-1.2.1-r1 x11-libs/pixman-0.24.0 kde-base/kdelibs-4.8.1-r2 dev-libs/glib-2.32.3 -- 'asm goto' not supported dev-lang/ruby (1.9.3_p125 to 1.9.3_p194_r1) Looking into the problem more I'm wondering if this does not screem for a use flag that is implemented in parallel with multilib in the toolchain-funcs.eclass. That would likely give a suitable location to inherit a new dragonegg.eclass which can appropriately deal with locating and adding dragonegg.so to CFLAGS/CXXFLAGS and specificially setting USE="-dragonegg" to turn it off on a per package basis. If I can break away some time I may try to hack a test, but I am not an expert at setting up eclasses... Just a thought. Hope this helps.
Thanks for the report! Let's fill this tracker bug with the existing ones
Last rites for sys-devel/dragonegg in progress, bug #543644
