Re: dvipng compilation error for teTeX 2.99.3 on OSF1
Svend Tollak Munkejord <[email protected]> Wed, 10 Nov 2004 19:20:45 +0100
| Newsgroups | gmane.comp.tex.tetex.beta |
|---|---|
| Organization | The Royal Society for Putting Things on Top of Other Things |
| Message-ID | <[email protected]> |
On 2004-11-10, Stefan Ulrich <[email protected]> wrote: > Svend Tollak Munkejord <[email protected]> wrote : > >> make[2]: Entering directory >> `/home/vsl175/a/svendm/hentet/tetex-src-2.99.3.20041109-beta/texk/dvipng' > [...] >> cc: Error: dvipng.c, line 67: Invalid statement. (badstmt) >> // setbuf(stderr, NULL); >> --^ >> make[2]: *** [dvipng.o] Error 1 > > that C compiler obviously doesn't like C++ comments; try to remove > that line and see if that works ... In fact, I had to remove similar lines from several files in that directory: draw.c dvipng.c enc.c font.c pk.c special.c t1.c After that, all of teTeX compiled using the native cc and cxx. But alas, the resulting xdvi displayed the same errors as before. >> I also tried compiling with gcc (i.e. without setting CC and CXX), >> and that worked. However, xdvi turned up with a fancy interface, >> and died after a second: >> >> svendm@vsl175 > xdvi test Warning: Cannot convert string >> "-*-Menu-Medium-R-Normal--*-120-*-*-P-*-ISO8859-1" to type >> FontStruct xdvi-motif.bin 22.84.6 (Motif toolkit): events.c:4175: >> Shouldn't happen: Segmentation fault - trying to clean up and >> aborting ... IOT/Abort trap (core dumped) > > Did you make sure there were no files compiled with the other > compiler still lying around? (Try `make distclean', then again > configure && make ...) Oh yes, I had even removed the source directory and unpacked the tetex-src*.tar.gz file again. >> Another thing: in mt-yy.map, the lines >> mtex MTEX >> mtsy MTSY >> rmtmi RMTMI >> >> cause warnings about duplicate map entries to be issued by pdflatex >> and xdvi. > > In that case these entries must have occured in another .map file > before; could you try a grep on these to check? (The output of > `xdvi -debug open file.dvi' should show the candidates.) Yes. Thomas Esser pointed out that I ought to disable mt-belleek.map when using Mathtime. Best regards, Svend Tollak Munkejord