[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

building pdf documentation of glibc-doc-reference



Can someone help me in building the pdf documentation of glibc-doc-reference
on a Debian Sid machine? This is what I did

$apt-get source --download-only glibc-doc-reference
$dpkg-source -x glibc-doc-reference_2.6.1-1.dsc
$cd glibc-doc-reference-2.6.1/; vim debian/rules

change line 14 from
        $(MAKE) -C manual info html
to
        $(MAKE) -C manual info html pdf

$fakeroot debian/rules build

The compilations stops at

This is `epsf.tex' v2.7.3 <23 July 2005>
) localization, and turning on texinfo input format.) (./dir-add.texi) [
{/var/
lib/texmf/fonts/map/pdftex/updmap/pdftex.map}] [2] [3] [4] (./top-menu.texi)
(./chapters.texi (./intro.texi Chapter 1
Cross reference values unknown; you must run TeX again. [1] [2] [3] [4]
[5] [6] (./creature.texi [7] [8] [9]) [10] [11]) (./errno.texi Chapter 2
[12] [13] [14] [15] [16] [17] [18] [19] [20] [21] [22] [23] [24] [25] [26]
./errno.texi:1497: Unbalanced parentheses in @def.
@badparencount ...{Unbalanced parentheses in @def}
                                                  @global @parencount =0
@checkparencounts ...ount =0 @else @badparencount
                                                  @fi @ifnum @brackcount
=0 ...

@printdefunline ...enalty 10002 @checkparencounts
                                                  @endgroup
l.1497 ... {void (*} error_print_progname ) (void)



If I keep pressing carriage returns whenever it stops (total 3 times), in
the end I get the following error.


Output written on libc.pdf (1028 pages, 4392548 bytes).
Transcript written on libc.log.
/usr/bin/texi2dvi: pdfetex exited with bad status, quitting.
/usr/bin/texi2dvi: see libc.log for errors.
make[1]: *** [libc.pdf] Error 1
make[1]: Leaving directory
`/home/raju/practice/glibc-doc-reference/glibc-doc-reference-2.6.1/manual'
make: *** [build-stamp] Error 2


Is this a bug in glibc-doc-reference or texi2dvi or some other package? I
can file the bug but don't know against which package I should report it.
to?

thanks
raju

-- 
Kamaraju S Kusumanchi
http://www.people.cornell.edu/pages/kk288/
http://malayamaarutham.blogspot.com/



Reply to: