mirror of
git://sourceware.org/git/newlib-cygwin.git
synced 2025-01-29 10:30:50 +08:00
a669484b81
On 11/08/2015 11:08, Andre Vieira wrote: > On 10/08/15 14:38, Jon TURNEY wrote: >> On 07/08/2015 11:13, Andre Vieira wrote: >>> Building the manuals on Ubuntu LTS 14.04 (64-bit) using pdfTeX >>> 3.1415926-2.5-1.40.14 (TeX Live 2013/Debian) is failing with the >>> following error: >>> "Transcript written on libc.log. >>> /usr/bin/texi2dvi: pdfetex exited with bad status, quitting." >>> >>> libc.log complaints about the following: >>> >>> You can't use `@unskip' in vertical mode. >>> [...] >>> >>> This code has been around for a while, so it might have to do with a >>> change in pdfTex? So it seems this problem has been around for a while, and looks like it is due to a change in texi2dvi in texinfo 5.0 or late 4.x, see [1]. I guess it's not very noticeable since it only occurs when doing 'make dvi', which doesn't happen by default. Attached is a different and perhaps cleaner workaround to the one in that thread. [1] https://sourceware.org/ml/newlib/2013/msg00057.html From 4d386b5900b6c68e022004b447faa696be5ff8c7 Mon Sep 17 00:00:00 2001 From: Jon TURNEY <jon.turney@dronecode.org.uk> Date: Tue, 11 Aug 2015 14:46:39 +0100 Subject: [PATCH] Use '@sp 1' rather than '@*' to workaround a change in texi2dvi. Since about TexInfo 5.0, using '@*' immediately after a table causes a 'You can't use `@unskip' in vertical mode' error. See https://sourceware.org/ml/newlib/2013/msg00057.html Signed-off-by: Jon TURNEY <jon.turney@dronecode.org.uk>
README for GNU development tools This directory contains various GNU compilers, assemblers, linkers, debuggers, etc., plus their support routines, definitions, and documentation. If you are receiving this as part of a GDB release, see the file gdb/README. If with a binutils release, see binutils/README; if with a libg++ release, see libg++/README, etc. That'll give you info about this package -- supported targets, how to use it, how to report bugs, etc. It is now possible to automatically configure and build a variety of tools with one command. To build all of the tools contained herein, run the ``configure'' script here, e.g.: ./configure make To install them (by default in /usr/local/bin, /usr/local/lib, etc), then do: make install (If the configure script can't determine your type of computer, give it the name as an argument, for instance ``./configure sun4''. You can use the script ``config.sub'' to test whether a name is recognized; if it is, config.sub translates it to a triplet specifying CPU, vendor, and OS.) If you have more than one compiler on your system, it is often best to explicitly set CC in the environment before running configure, and to also set CC when running make. For example (assuming sh/bash/ksh): CC=gcc ./configure make A similar example using csh: setenv CC gcc ./configure make Much of the code and documentation enclosed is copyright by the Free Software Foundation, Inc. See the file COPYING or COPYING.LIB in the various directories, for a description of the GNU General Public License terms under which you can copy the files. REPORTING BUGS: Again, see gdb/README, binutils/README, etc., for info on where and how to report problems.