Alex Turbov

> clang fails on plaudis.scm on undefined references to a few different wrapper iterators. and is it successfully compiled `paludis-9999` from portage? and about an error, I've asked about compile...

The warning is not important (though could be easy fixed by patch). Linking errors actually caused by improper use of [Dual ABI](https://gcc.gnu.org/onlinedocs/libstdc++/manual/using_dual_abi.html): it looks like some parts of your system...

FYI, to resolve `cave fix-linkage` bug, [here](https://github.com/zaufi/paludis-autopatches/blob/master/ebuild_unpack_post/sys-apps/paludis-scm/ios-base-failure-gcc-bug.patch) is a patch I use to apply by [auto-patch hook](http://zaufi.github.io/my-paludis-hooks-and-addons.html).

please show me the env file mentioned... I'll try to reproduce.

I'm not sure that setting `T` is a good idea (allowed at all) -- please read PMS about it (and a footnote about its consistency). Maybe you can try to...

Probably we can use Python bindings for that (need to check API), but the limitation of this solution: `paludis` must be build w/ USE=python... the other idea is to use...

:-) unfortunately portage is unavoidable nowadays as official docs claim… then we ought to build `paludis` w/ `USE+=python`… (as for me I build it w/ that flag cuz Python bindings...

I'll try :) what exactly Ubuntu do you have? 16.04 (xenial) or 16.10 (yakkety) ? I'll use the corresponding docker container to check it on my spare time... On Fri,...

Thanks for the report, I've been able to reproduce it...

Thanks for the report, I've been able to reproduce it... That is not really a bug, but a lack of feature. (and little bit messy in the `README` %)