I think Jan's answer is slightly misleading. The message about TEXMF being an undefined variable is perfectly fine (at least if you use csh or tcsh as your shell) and just shows that you don't set it as an environmental variable anywhere else. Normally, the variable is read from a setup file in teTeX and is not set as an environment variable, but in LilyPond we exploit the possibility to override this setting with an environment variable.
Anyway, to help us assist your debugging; what does the following sequence of commands return?
kpsexpand \$TEXMF
kpsexpand \$TEXPSHEADERS
kpsewhich tex.pro
unsetenv TEXMF # Assuming you use tcsh, otherwise use: unset TEXMF
kpsexpand \$TEXMF
kpsexpand \$TEXPSHEADERS
kpsewhich tex.pro
/Mats
Jan Nieuwenhuizen wrote:
Walter Hofmeister writes:
When I start the Terminal I now get this:
Welcome to Darwin! TEXMF: Undefined variable. <-- this did not appear before.
You should find out what goes wrong here, this is most certainly the culprit. Something broke wrt your TeX or lilypond installation.
When you log in, TEXMF should point to your TeX installation (possibly something like '!!/sw/usr/share/texmf'). The additional lilypond profile or login script adds the location of the lilypond TeX tree to this variable. Both must be present, another Mac users can probably tell you what the variable must look like.
Jan.
-- ============================================= 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: [EMAIL PROTECTED] WWW: http://www.s3.kth.se/~mabe =============================================
_______________________________________________ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
