bug-lilypond
[Top][All Lists]
Advanced

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

Re: Lilypond 2.2.0: cannot produce postscript


From: Mats Bengtsson
Subject: Re: Lilypond 2.2.0: cannot produce postscript
Date: Thu, 29 Apr 2004 18:29:55 +0200
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040113

I think we have solved the problem. For some reason, the slackware
distribution of tetex-2.0.2 has reorganized the directory structure
and defined
TEXPSHEADERS as .:$TEXMF/{dvips,fonts/enc,fonts/type1}//
in `kpsewhich texmf.cnf`

By default, the texmf.cnf file in teTeX 2.0.2 contains the following
definition of the variable
TEXPSHEADERS = .;$TEXMF/{dvips,pdftex,tex,fonts/type1}//

You may want to edit the file and add the directory tex in the
list of subdirectories to be searched.

As an alternative, link the files
/usr/local/share/lilypond/2.2.0/ps/*
into the directory
/usr/local/share/lilypond/2.2.0/dvips/

It may be a good idea that we move the files from the directory
tex/ to dvips/ in the LilyPond installation structure to get a
solution that's compatible with both the default teTeX setup and
the slackware version.

   /Mats


Derrick Everett wrote:
Hi Mats,

I install tetex from the Slackware 9.1 distribution: tetex-2.0.2-i386-1.tgz

Slackware sometimes locates files in other directories, or in a different hierarchy, from other distributions. This is the case with XFree86, for example.

----------------------------------
$ cat /usr/share/texmf/updates.dat
Main version number: teTeX-2.0
Installed updates:
  update 001 for teTeX-2.0
----------------------------------


--
=============================================
        Mats Bengtsson
        Signal Processing
        Signals, Sensors and Systems
        Royal Institute of Technology
        SE-100 44  STOCKHOLM
        Sweden
        Phone: (+46) 8 790 8463                         
        Fax:   (+46) 8 790 7260
        Email: address@hidden
        WWW: http://www.s3.kth.se/~mabe
=============================================




reply via email to

[Prev in Thread] Current Thread [Next in Thread]