From 4c46bc63389612732c68744fdb2bc28dc6839087 Mon Sep 17 00:00:00 2001 From: Karl Berry Date: Thu, 1 May 2014 23:05:45 +0000 Subject: compile i386-linux dvisvgm separately, with system compiler on centos5[.10] git-svn-id: svn://tug.org/texlive/trunk@33784 c570f23f-e606-0410-a88d-b1316a301751 --- Build/source/README | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) (limited to 'Build/source/README') diff --git a/Build/source/README b/Build/source/README index 134aa512d3a..decdd1f9eb3 100644 --- a/Build/source/README +++ b/Build/source/README @@ -20,8 +20,12 @@ README* files here (which are generated from that document). Build information for some of the platforms. -i386-linux: gcc 4.8.2, Linux 2.6.18-* (CentOS 5.10, tug.org) - ~karl/bin/mybuild +i386-linux: gcc 4.8.2, Linux 2.6.18-* (CentOS 5.10, tug.org:~karl/bin/mybuild) + Except for dvisvgm, where we must use the system compiler (gcc 4.1.2, + Red Hat 4.1.2-54) or libgs.so crashes trying to use gcc 4.8.2's + libstdc++. On the other hand, the system compiler has an optimization + bug that causes lcdf-typetools's tfm.test to fail, so it can't be used + for everything. Sigh. x86_64-linux: gcc 4.8.2, libc 2.3.6, Linux 2.6.28.6 -- cgit v1.2.3