$Id$ Copyright 2004, 2006, 2007 TeX Users Group. You may freely use, modify and/or distribute this file. (Originally written in 2004 by Karl Berry.) To build the source tree, run ./Build. To build (mostly) without optimization, try CFLAGS=-g Build. - Bison and Flex are needed for web2c. - libfontconfig (development) must be present for XeTeX to build, except on MacOSX. - A terminal (development) library such as libncurses must be present for Texinfo to build. The binaries will be left in ./inst/bin/. Don't worry about the other files and directories in inst. The new binaries are not directly usable from that location. Instead, you have to copy them to texmf/bin/ (in the repository, that's under the Master tree). If your C++ needs to find the standard library in, say, /usr/local/lib, (i.e., configure fails saying the compiler doesn't work), try: env LD_OPTIONS=-R/usr/local/lib Build That should be it for normal builds. Email tex-live@tug.org if problems. Running ./reautoconf here reruns autoconf, both old (the hacked 2.13 we have here) and new (assumed to be in /usr/bin/autoconf). Automadness: should be oldest > newest in this order (often used alternate names in parentheses): Makefile.am > configure.ac (configure.in) Makefile.in > config.h.in (config.hin) > configure To rerun dvipdfmx: until integration, insert our configure.in, data/Makefile.am, src/Makefile.am changes, copy compile script. aclocal; autoheader; automake; autoconf touch config.h.in; sleep 1; touch Makefile.in # shouldn't be needed, but ... Build information: i386-darwin: i686-apple-darwin8.1.0 built by Gerben Wierda, from http://bloch.ling.yale.edu/i-packages/experimental/tex.ii2/tex.30.tar.bz2 powerpc-darwin: powerpc-apple-darwin6.8 built by Gerben Wierda, from http://bloch.ling.yale.edu/i-packages/experimental/tex.ii2/tex.26.tar.bz2 x86_64-linux: built by Tigran Aivazian, from http://www.bibles.org.uk/x86_64 # uname -a Linux elpis 2.6.8.1 #18 SMP Fri Mar 25 19:46:16 GMT 2005 x86_64 x86_64 x86_64 G$ # gcc -v Reading specs from /usr/lib/gcc-lib/x86_64-redhat-linux/3.3.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --disable-libunwind-exceptions --with-system-zlib --enable-__cxa_atexit --host=x86_64-redhat-linux Thread model: posix gcc version 3.3.3 20040412 (Red Hat Linux 3.3.3-7) These three built and checked in by Vladimir Volovich: 1) sparc-solaris OS: Sun Solaris 8 compiler: Sun Studio 11 bison (GNU Bison) 2.3 flex version 2.5.4 GNU m4 1.4.5 GNU Make 3.81 xe(la)tex and xdvipdfmx depend on fontconfig. Because Solaris 8 does not include fontconfig, we used fontconfig package (version 2.3.2) from http://www.blastwave.org/ (together with it's dependencies) 2) sparc-linux OS: Debian GNU/Linux 3.1 (Sarge), kernel 2.4.27-2-sparc64 gcc (GCC) 3.3.5 (Debian 1:3.3.5-13) bison (GNU Bison) 1.875d flex 2.5.31 GNU m4 1.4.2 GNU Make 3.80 3) powerpc-aix OS: AIX 4.3 compiler: IBM C for AIX Compiler, Version 5 (xlc) bison (GNU Bison) 1.34 flex version 2.5.4 GNU m4 1.4 GNU Make 3.79.1 xe(la)tex and xdvipdfmx depend on fontconfig. You can download fontconfig for AIX from http://www-03.ibm.com/servers/aix/products/aixos/linux/download.html ftp://ftp.software.ibm.com/aix/freeSoftware/aixtoolbox/RPMS/ppc/fontconfig/ xdvi 22.84.10 - ok 28nov06 http://xdvi.sourceforge.net/ - TeX Live includes many programs, which depend on many libraries, notably the TeX file-searching library kpathsea. - TL has thousands of users, and they almost all install binaries, rather than compile from source. - Of course kpathsea is itself part of TeX Live, and we need to use the version that is included here, not whatever is randomly installed on the build system or the end-user's system. - So a program that TL includes, such as lcdf-typetools (http://www.lcdf.org/type/), has a configure option --enable-tetex-build, which sets up CPPFLAGS and LDFLAGS to use the local kpathsea in the build tree, like this: if test "x$enable_tetex_build" = xyes; then ... CPPFLAGS="$CPPFLAGS -I\$(top_builddir)/../../texk -I\$(top_srcdir)/../../texk" LDFLAGS="$LDFLAGS -L\$(top_builddir)/../../texk/kpathsea/.libs" - The exact paths there aren't important reflect the structure of our source hierarchy, relative to top_builddir/srcddir. - The quoting there makes the values in the Makefile use Make variables: CPPFLAGS = -I$(top_builddir)/../../texk -I$(top_srcdir)/../../texk - However, since "$(top_builddir)" is used as a literal string, of course that's not going to be found in the -I list, so any further configure tests that need those values are going to fail. For example: AC_CHECK_DECLS(kpse_opentype_format, :, :, [#include ]) - To get around this, we've simply been hardwiring the test results of when --enable-tetex-build is given. So the test above becomes: if test "x$enable_tetex_build" = xyes; then AC_DEFINE(HAVE_DECL_KPSE_OPENTYPE_FORMAT) else AC_CHECK_DECLS(kpse_opentype_format, :, :, [#include ]) fi - None of this is actually specific to kpathsea, there are tons of other libraries involved. It's just easier to discuss a specific example. So I asked autoconf@gnu.org: I am wondering if there's a reasonable way to use the top_builddir and top_srcdir values at configure time. As in: CPPFLAGS="$CPPFLAGS -I$top_builddir/whatever" When simply used as above, the value is not defined. It seems that the value for these variables only gets defined at the end, for output (or for recursive --help's). I guess I could simply duplicate the code which computes them, but of course that is not very appealing. Is there a better way? Andreas Schwab replied: At configure time $top_builddir == "." and $top_srcdir == $srcdir. They are only different in sub-makefiles. So maybe it would not be so hard. Bob Frisenhahn mentioned: # Get full paths to source and build directories srcdirfull=`cd $srcdir && pwd` builddir=`pwd`