I recently did: mkdir build mv lilypond build
after that building failed, but removing share/ directory helped. By this manner, I found that there is a mixture of relative and absolute paths in share/: $ ls -lg share/lilypond total 12 lrwxrwxrwx 1 hjunes 12 May 4 15:12 afm -> ../../mf/out lrwxrwxrwx 1 hjunes 12 May 4 15:12 dvips -> ../../mf/out drwxr-xr-x 2 hjunes 4096 May 4 15:12 elisp drwxr-xr-x 2 hjunes 4096 May 4 15:12 fonts lrwxrwxrwx 1 hjunes 30 May 4 15:12 ly -> /home/hjunes/build/lilypond/ly lrwxrwxrwx 1 hjunes 30 May 4 15:12 mf -> /home/hjunes/build/lilypond/mf lrwxrwxrwx 1 hjunes 30 May 4 15:12 ps -> /home/hjunes/build/lilypond/ps lrwxrwxrwx 1 hjunes 16 May 4 15:12 python -> ../../python/out lrwxrwxrwx 1 hjunes 31 May 4 15:12 scm -> /home/hjunes/build/lilypond/scm drwxr-xr-x 2 hjunes 4096 May 4 15:12 tex lrwxrwxrwx 1 hjunes 12 May 4 15:12 tfm -> ../../mf/out My question is that should there be some coherent solution: all paths in share/ are either (a) relative, or (b) absolute? -- Heikki Junes _______________________________________________ lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
