[tlbuild] dvisvgm-2.1 trial build

[Richard M. Koch]

Karl,

I have no problem with this decision.

However, the statement "the sources should compile fine with gcc 4.8.1,
clang 3.3, or any later versions" suggest to me that the authors haven't
investigated clang very thoroughly, or possibly the problem isn't due to C++1
on modern systems. On the latest version of OS X,

	clang --version

gives

	Apple LLVM version 8.0.0 (clang-800.0.42.1)

Going to the clang.llvm.org <http://clang.llvm.org/> sites, in a page dated January 12, 2017,
we read

-----

Clang fully implements all published ISO C++ standards (C++98 / C++03 <https://clang.llvm.org/cxx_status.html#cxx98>, C++11 <https://clang.llvm.org/cxx_status.html#cxx11>, and C++14 <https://clang.llvm.org/cxx_status.html#cxx14>), and most of the upcoming C++1z <https://clang.llvm.org/cxx_status.html#cxx17> standard.
The Clang community is continually striving to improve C++ standards compliance between releases by submitting and tracking C++ Defect Reports <https://clang.llvm.org/cxx_dr_status.html> and implementing resolutions as they become available.

Experimental work is also under way to implement C++ Technical Specifications <https://clang.llvm.org/cxx_status.html#ts> that will help drive the future of the C++ programming language.

Clang 3.3 and later implement all of the ISO C++ 2011 standard <http://www.iso.org/iso/catalogue_detail.htm?csnumber=50372>.

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 -std=c++11 option. Clang's C++11 mode can be used with libc++ <http://libcxx.llvm.org/> or with gcc's libstdc++


------

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,
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
in TeX Live

Do you know if this can be done by disabling a small number of programs? And will dvisvgm still compile?

Dick Koch



> On Feb 1, 2017, at 2:23 PM, Karl Berry <karl at freefriends.org> wrote:
> 
> I knew C++11 would be a big barrier.  Martin (Gieseking) wrote me:
> 
>    Yes [...] As of dvisvgm 2.0, C++11 is required. The new language
>    features and the additions to the standard library allow much
>    cleaner code with less cumbersome constructions.  The sources should
>    compile fine with gcc 4.8.1, clang 3.3, or any later versions.
> 
> Since I doubt it is feasible or desirable to build the entire source
> with compilers of that vintage (even when they are available), as far as
> I can see the choices are:
> 
> 1) --disable-dvisvgm
> 2) build dvisvgm in a separate tree from everything else with different
> options.
> 
> I expect the result will be that dvisvgm is no longer included in the
> native TL on most platforms, and that's ok (since it has to be).
> 
> Best,
> Karl

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://tug.org/pipermail/tlbuild/attachments/20170201/578fb853/attachment.html>