Re: 2.99.1: new beta / almost release candidate
Reinhard Kotucha <[email protected]>
| Newsgroups | gmane.comp.tex.tetex.beta |
|---|---|
| Message-ID | <[email protected]> |
Hi Thomas,
my first attempt to compile this version was not successful. I got:
In file included from dvipng.h:81,
from dvipng.c:44:
/usr/lib/gcc-lib/i386-slackware-linux/egcs-2.91.66/include/stdbool.h:9: parse error before `0'
make[2]: *** [dvipng.o] Error 1
make[2]: Leaving directory `/ext/dtp-build/tetex/tetex-src-beta-2.99.1.20041026/texk/dvipng'
The file stdbool.{c,h} is obviously part of gcc and I was successful
when I used gcc 3.1.1 instead of egcs-2.91.66, maybe configure can
detect this problem.
Then I got the message:
WARNING: You must install texinfo.tex and txi-??.tex manually,
perhaps in TEXMF/tex/texinfo/,
where TEXMF is a root of your TeX tree.
See doc/README for some considerations.
You can run make TEXMF=/your/texmf install-tex to do this.
You may also need to install epsf.tex and (if you
use pdftex) pdfcolor.tex in TEXMF/tex/generic/dvips
and TEXMF/pdftex/plain/misc/pdfcolor.tex respectively,
if your TeX installation did not include them.
This message is misleading because the files mentioned in the message
had been installed properly.
Maybe they are not in the tetex-texmf archive but are installed from
the tetex-source tree. In this case the makefile probably should ask
later or install them earlier. But the warning doesn't cause any
problem, it's just misleading.
When "make world" generated the format files, I got the following
error messages:
fmtutil: attempting to create localized format using pool=tex-pl and tcx=il2-pl.
running `pdfetex -ini -translate-file=il2-pl -jobname=platex-pl -progname=platex-pl *platex.ini' ...
! pdfetex.pool doesn't match; tangle me again (or fix the path).
Error: `pdfetex -ini -translate-file=il2-pl -jobname=platex-pl -progname=platex-pl *platex.ini' failed
fmtutil: attempting to create localized format using pool=tex-pl and tcx=il2-pl.
running `pdfetex -ini -translate-file=il2-pl -jobname=mex-pl -progname=mex-pl *mex.ini' ...
! pdfetex.pool doesn't match; tangle me again (or fix the path).
Error: `pdfetex -ini -translate-file=il2-pl -jobname=mex-pl
-progname=mex-pl *mex.ini' failed
fmtutil: attempting to create localized format using pool=pdftex-pl and tcx=il2-pl.
running `pdfetex -ini -translate-file=il2-pl -jobname=pdfmex-pl -progname=pdfmex-pl *pdfmex.ini' ...
! pdfetex.pool doesn't match; tangle me again (or fix the path).
Error: `pdfetex -ini -translate-file=il2-pl -jobname=pdfmex-pl -progname=pdfmex-pl *pdfmex.ini' failed
[...]
###############################################################################
fmtutil: Error! Not all formats have been built successfully.
Visit the log files in directory
/usr/local/dtp/share/texmf/web2c
for details.
###############################################################################
This is a summary of all `failed' messages and warnings:
`pdfetex -ini -translate-file=il2-pl -jobname=platex-pl -progname=platex-pl *platex.ini' failed
`pdfetex -ini -translate-file=il2-pl -jobname=mex-pl -progname=mex-pl *mex.ini' failed
`pdfetex -ini -translate-file=il2-pl -jobname=pdfmex-pl -progname=pdfmex-pl *pdfmex.ini' failed
make: *** [install] Error 1
The nasty thing is that some symlinks had not been created. For
instance, pdflatex (the symlink) was missing though pdflatex.fmt had
been created successfully.
There was no problem with these formats when running "texconfig init"
manually. This created all missing symlinks.
Then I thought that I have a TeX system that works, but when I
compiled a document, many fonts had not been found. I then launched
updmap manually (without any option) and now it seems that everything
works.
Regards,
Reinhard
--
----------------------------------------------------------------------------
Reinhard Kotucha Phone: +49-511-4592165
Marschnerstr. 25
D-30167 Hannover mailto:[email protected]
----------------------------------------------------------------------------
Microsoft isn't the answer. Microsoft is the question, and the answer is NO.
----------------------------------------------------------------------------