On 2017/04/16 14:28, Christian Weisgerber wrote: > On 2017-04-16, Marc Espie <[email protected]> wrote: > > >> * In the clang module, also link /usr/local/bin/clang and clang++ > >> into the leading PATH directory. > > > > Should that actually be default ? it will make sure the clang from ports > > is used on clang architectures, if that's the intention. > > There was a suggestion that on CLANG_ARCHS the clang module should > point to the base compiler and not pull in devel/llvm. I couldn't > find the patch though, and there are the C++ library issues to > consider, so I went with the above for the time being.
That's how things worked with the gcc module when we had a particular compiler version in-base. FWIW here's my hit list of what I think are the most important things to fix for aarch64 from the current breakages. databases/mariadb databases/p5-DBD-SQLite devel/boost devel/gdb devel/libgtop2 devel/xdg-user-dirs lang/gcc/4.9 net/libproxy sysutils/gamin textproc/aspell/core textproc/jq
