This should definitely not be necessary. As described in some earlier emails in the mailing list, you may have play some tricks with the TEXMF variable if you already have TeXLive or some other TeX installation in Windows that sets the environment variable. However, in that case it is better to just clear the variable in the startup scripts for cygwin and let the ordinary cygwin mechanisms set the variable correct.
From the log in the original mail, the line
TEXMF={/usr/share/lilypond/2.2.5,}
indicates that something is wrong related to this variable, before
the lilypond related setup file adds its setting.
The first thing I would check is if the changes you have made earlier
to /etc/profile/ still remain, or if they have been overwritten when
you rerun setup.exe./Mats
James Moore wrote:
I had a similar problem when I upgraded to 2.4 lilypond under cygwin. Turned out that there was an environment variable problem. I added this to my .bashrc file:
export TEXMF='{/usr/share/lilypond/2.4.2,/usr/share/texmf}'
and lilypond was happy.
Interestingly, lilypond worked just fine when I ran a plain bash shell
without X. I only saw the problem when I ran lilypond in a xterm.
- James
_______________________________________________ lilypond-user mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-user
-- ============================================= 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://lists.gnu.org/mailman/listinfo/lilypond-user
