Does anyone (maybe people pushing for the llvm update :-) know how we should handle this yet?
On 2016/03/15 13:43, Stuart Henderson wrote: > On 2016/03/14 22:04, Antoine Jacoutot wrote: > > I haven't followed ports too closely these past few days but > > textproc/vislcg3 failed in my last bulk. > > Building icu4c with gcc 4.9 or with clang fixes vislcg3, but then breaks > other things unless they are also built with gcc 4.9 or clang, and will > result in a whole bunch of things pulling in conflicting libraries, both > stdc++ (often via Mesa's libGLU) and estdc++. (i.e. taking us back to > approximately the place we were before gcc 4.2 was imported to base > - which we were able to sidestep for a while with the older version of > clang that was able to compile newer programs than 4.2.1 while still > using base's libstdc++ - which we can no longer do following the change > in the clang port to using libestdc++). > > The most "correct" fixes that I can see would either be to use > libc++/clang in base, or build all c++ (including that in xenocara) > with ports compilers and linked with estdc++. > > Untested but I wonder if removing --std=c++0x from CXXFLAGS in icu4c's > pkg-config files might help as a dirty workaround for now... >
