dvips error

Gregory Davis gregdavis at ieee.org
Fri Oct 22 17:14:27 PDT 2004


Gregory Davis wrote:

> Sergi Vélez wrote:
> 
>> On dl, 2004-10-11 at 09:50, Sergi Vélez wrote:
>>> Hi,
>>> 
>>> I've just installed TeX-2.0.2.
>>> 
>>> When I' try to compile a document (exactly this one
>>>
>
http://www.tug.org/tex-archive/graphics/pstricks/contrib/psgo/psgomanual.tex,
>>> but same error with others)
>>> 
>>> I get this error:
>>> 
>>> 
>>> [ris at ris-pc go 1046]$ latex psgomanual.tex && latex psgomanual.tex
>>> 
>>> (lots of text)
>>> LaTeX Font Warning: Some font shapes were not available, defaults
>>> substituted.
>>> 
>>>  )
>>> (see the transcript file for additional information)
>>> Output written on psgomanual.dvi (10 pages, 85040 bytes).
>>> Transcript written on psgomanual.log.
>>> [ris at ris-pc go 1046]$
>>> 
>>> then I run
>>> 
>>> [ris at ris-pc go 1046]$ dvips psgomanual.dvi -o
>>> 
>>> and get this
>>> 
>>> [ris at ris-pc go 1046]$ dvips psgomanual.dvi -o
>>> This is dvips(k) 5.92b Copyright 2002 Radical Eye Software
>>> (www.radicaleye.com)
>>> ' TeX output 2004.10.11:0947' -> psgomanual.ps
>>> kpathsea: Running mktexpk --mfmode ljfour --bdpi 600 --mag 1+0/600 --dpi
>>> 600 mss17
>>> mktexpk: don't know how to create bitmap font for mss17.
>>> kpathsea: Appending font creation commands to missfont.log.
>>> dvips: Font mss17 not found, characters will be left blank.
>>> dvips: Can't open font metric file mss17.tfm
>>> dvips: I will use cmr10.tfm instead, so expect bad output.
>>> dvips: Checksum mismatch in mss17
>>> dvips: Design size mismatch in mss17.tfm
>>> kpathsea: Running mktexpk --mfmode ljfour --bdpi 600 --mag 1+0/600 --dpi
>>> 600 mr10
>>> mktexpk: don't know how to create bitmap font for mr10.
>>> dvips: Font mr10 not found, characters will be left blank.
>>> dvips: Can't open font metric file mr10.tfm
>>> dvips: I will use cmr10.tfm instead, so expect bad output.
>>> kpathsea: Running mktexpk --mfmode ljfour --bdpi 600 --mag 1+0/600 --dpi
>>> 600 mss10
>>> mktexpk: don't know how to create bitmap font for mss10.
>>> dvips: Font mss10 not found, characters will be left blank.
>>> dvips: Can't open font metric file mss10.tfm
>>> dvips: I will use cmr10.tfm instead, so expect bad output.
>>> dvips: Checksum mismatch in mss10
>>> 
>>> ...
>>> 
>>> kpathsea: Running mktexpk --mfmode ljfour --bdpi 600 --mag 1+0/600 --dpi
>>> 600 msy9
>>> mktexpk: don't know how to create bitmap font for msy9.
>>> dvips: Font msy9 not found, characters will be left blank.
>>> dvips: Can't open font metric file msy9.tfm
>>> dvips: I will use cmr10.tfm instead, so expect bad output.
>>> dvips: Checksum mismatch in msy9
>>> dvips: Design size mismatch in msy9.tfm
>>>
>
<texc.pro><pstricks.pro><pst-dots.pro><pst-node.pro><special.pro><color.pro>
>>> . [1] [2] [3] [4] [5] [6] [7] [8] [9] [10]
>>> [ris at ris-pc go 1047]$
>>> 
>>> The ps generated contains no words
>>> 
>>> Any idea?
>>> 
>>> 
>>> Thanks
>>> 
>>> --
>>> Sergi.
>> 
>> I've solved the problem. It seems that there's a problem with CFLAGS. I
>> compile it without any optimizations and works fine.
>> 
> 
> Do you recall what flags you used?  I have the same problem and optimized
> like a madman, but don't remember compile time errors or warnings.  We
> should find out what is the bad flag and have it noted in the book.
> 
> Greg

I love responding to myself, that must be breaking some unbroken law.  Here
is what didn't work:
CFLAGS="-march=athlon-tbird -O3 -pipe -fforce-addr -fomit-frame-pointer \
  -funroll-loops -falign-functions=4 -maccumulate-outgoing-args"
CXXFLAGS=$CFLAGS
and just now, this did:
CFLAGS="-march=athlon-tbird -O3 -pipe -fomit-frame-pointer"
CXXFLAGS=$CFLAGS

so using one or more of these broke the build:
-fforce-addr
-funroll-loops
-falign-functions=4
-maccumulate-outgoing args

Greg



More information about the blfs-support mailing list