<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Karl,<div class=""><br class=""></div><div class="">I have no problem with this decision.</div><div class=""><br class=""></div><div class="">However, the statement "the sources should compile fine with gcc 4.8.1,</div><div class="">clang 3.3, or any later versions" suggest to me that the authors haven't</div><div class="">investigated clang very thoroughly, or possibly the problem isn't due to C++1</div><div class="">on modern systems. On the latest version of OS X,</div><div class=""><br class=""></div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>clang --version</div><div class=""><br class=""></div><div class="">gives</div><div class=""><br class=""></div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span><span style="font-family: Menlo; font-size: 11px; background-color: rgb(255, 255, 255);" class="">Apple LLVM version 8.0.0 (clang-800.0.42.1)</span><div style="margin: 0px; font-size: 11px; line-height: normal; font-family: Menlo; background-color: rgb(255, 255, 255);" class=""><br class=""></div><div style="margin: 0px; font-size: 11px; line-height: normal; font-family: Menlo; background-color: rgb(255, 255, 255);" class="">Going to the <a href="http://clang.llvm.org" class="">clang.llvm.org</a> sites, in a page dated January 12, 2017,</div><div style="margin: 0px; font-size: 11px; line-height: normal; font-family: Menlo; background-color: rgb(255, 255, 255);" class="">we read</div><div style="margin: 0px; font-size: 11px; line-height: normal; font-family: Menlo; background-color: rgb(255, 255, 255);" class=""><br class=""></div><div style="margin: 0px; font-size: 11px; line-height: normal; font-family: Menlo; background-color: rgb(255, 255, 255);" class="">-----</div><div style="margin: 0px; font-size: 11px; line-height: normal; font-family: Menlo; background-color: rgb(255, 255, 255);" class=""><br class=""></div><div style="margin: 0px; font-size: 11px; line-height: normal; font-family: Menlo; background-color: rgb(255, 255, 255);" class=""><span style="color: rgb(34, 34, 34); font-family: 'Lucida Grande', 'Lucida Sans Unicode', Arial, Verdana, Helvetica, sans-serif;" class="">Clang fully implements all published ISO C++ standards (</span><a href="https://clang.llvm.org/cxx_status.html#cxx98" style="font-family: 'Lucida Grande', 'Lucida Sans Unicode', Arial, Verdana, Helvetica, sans-serif;" class="">C++98 / C++03</a><span style="color: rgb(34, 34, 34); font-family: 'Lucida Grande', 'Lucida Sans Unicode', Arial, Verdana, Helvetica, sans-serif;" class="">,</span><span style="color: rgb(34, 34, 34); font-family: 'Lucida Grande', 'Lucida Sans Unicode', Arial, Verdana, Helvetica, sans-serif;" class=""> </span><a href="https://clang.llvm.org/cxx_status.html#cxx11" style="font-family: 'Lucida Grande', 'Lucida Sans Unicode', Arial, Verdana, Helvetica, sans-serif;" class="">C++11</a><span style="color: rgb(34, 34, 34); font-family: 'Lucida Grande', 'Lucida Sans Unicode', Arial, Verdana, Helvetica, sans-serif;" class="">, and</span><span style="color: rgb(34, 34, 34); font-family: 'Lucida Grande', 'Lucida Sans Unicode', Arial, Verdana, Helvetica, sans-serif;" class=""> </span><a href="https://clang.llvm.org/cxx_status.html#cxx14" style="font-family: 'Lucida Grande', 'Lucida Sans Unicode', Arial, Verdana, Helvetica, sans-serif;" class="">C++14</a><span style="color: rgb(34, 34, 34); font-family: 'Lucida Grande', 'Lucida Sans Unicode', Arial, Verdana, Helvetica, sans-serif;" class="">), and most of the upcoming</span><span style="color: rgb(34, 34, 34); font-family: 'Lucida Grande', 'Lucida Sans Unicode', Arial, Verdana, Helvetica, sans-serif;" class=""> </span><a href="https://clang.llvm.org/cxx_status.html#cxx17" style="font-family: 'Lucida Grande', 'Lucida Sans Unicode', Arial, Verdana, Helvetica, sans-serif;" class="">C++1z</a><span style="color: rgb(34, 34, 34); font-family: 'Lucida Grande', 'Lucida Sans Unicode', Arial, Verdana, Helvetica, sans-serif;" class=""> </span><span style="color: rgb(34, 34, 34); font-family: 'Lucida Grande', 'Lucida Sans Unicode', Arial, Verdana, Helvetica, sans-serif;" class="">standard.</span></div><p style="color: rgb(34, 34, 34); font-family: 'Lucida Grande', 'Lucida Sans Unicode', Arial, Verdana, Helvetica, sans-serif;" class="">The Clang community is continually striving to improve C++ standards compliance between releases by submitting and tracking <a href="https://clang.llvm.org/cxx_dr_status.html" class="">C++ Defect Reports</a> and implementing resolutions as they become available.</p><p style="color: rgb(34, 34, 34); font-family: 'Lucida Grande', 'Lucida Sans Unicode', Arial, Verdana, Helvetica, sans-serif;" class="">Experimental work is also under way to implement <a href="https://clang.llvm.org/cxx_status.html#ts" class="">C++ Technical Specifications</a> that will help drive the future of the C++ programming language.</p><div class=""><p style="color: rgb(34, 34, 34); font-family: 'Lucida Grande', 'Lucida Sans Unicode', Arial, Verdana, Helvetica, sans-serif;" class="">Clang 3.3 and later implement all of the <a href="http://www.iso.org/iso/catalogue_detail.htm?csnumber=50372" class="">ISO C++ 2011 standard</a>.</p><p style="color: rgb(34, 34, 34); font-family: 'Lucida Grande', 'Lucida Sans Unicode', Arial, Verdana, Helvetica, sans-serif;" class="">By default, Clang builds C++ code according to the C++98 standard, with many C++11 features accepted as extensions. You can use Clang in C++11 mode with the <code class="">-std=c++11</code> option. Clang's C++11 mode can be used with <a href="http://libcxx.llvm.org/" class="">libc++</a> or with gcc's libstdc++</p><div class=""><br class=""></div><div class="">------</div><div class=""><br class=""></div><div class="">Being an amateur in these matters, I probably don't understand details. But since one error on OS X mentions locale-r, and since I definitely found this defined in OS X headers, and since a blog site says the error is related to a conflict between X11 headers and OS X headers on the Mac,</div><div class="">and since Apple no longer supplies X11 or its headers (which now come from open source), it would be fun to see what happens if X11 is turned off</div><div class="">in TeX Live</div><div class=""><br class=""></div><div class="">Do you know if this can be done by disabling a small number of programs? And will dvisvgm still compile?</div><div class=""><br class=""></div><div class="">Dick Koch</div><div class=""><br class=""></div></div><div class=""><br class=""></div><div style="margin: 0px; font-size: 11px; line-height: normal; font-family: Menlo; background-color: rgb(255, 255, 255);" class=""><br class=""></div><div><blockquote type="cite" class=""><div class="">On Feb 1, 2017, at 2:23 PM, Karl Berry <<a href="mailto:karl@freefriends.org" class="">karl@freefriends.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">I knew C++11 would be a big barrier. Martin (Gieseking) wrote me:<br class=""><br class=""> Yes [...] As of dvisvgm 2.0, C++11 is required. The new language<br class=""> features and the additions to the standard library allow much<br class=""> cleaner code with less cumbersome constructions. The sources should<br class=""> compile fine with gcc 4.8.1, clang 3.3, or any later versions.<br class=""><br class="">Since I doubt it is feasible or desirable to build the entire source<br class="">with compilers of that vintage (even when they are available), as far as<br class="">I can see the choices are:<br class=""><br class="">1) --disable-dvisvgm<br class="">2) build dvisvgm in a separate tree from everything else with different<br class="">options.<br class=""><br class="">I expect the result will be that dvisvgm is no longer included in the<br class="">native TL on most platforms, and that's ok (since it has to be).<br class=""><br class="">Best,<br class="">Karl<br class=""></div></div></blockquote></div><br class=""></div></body></html>