Will Oram writes:
That's why I asked; `/defs.ly' is a full path...
Bad news: No difference in errors.
Errors are not bad news per se. LilyPond prints error messages to
help you if something is wrong.
Just take a look at the error message
mvmt1/mvmt1.ly:15:18: error: can't find file: `defs.ly'
(search path:
/sw/share/lilypond/2.2.3/ps:/sw/share/lilypond/2.2.3/tfm:/sw/share/
lilypond/2.2.3/scm:/sw/share/lilypond/2.2.3/mf/out:/sw/share/lilypond/
2.2.3/afm:/sw/share/lilypond/2.2.3/ly:/sw/share/lilypond/ps:/sw/share/
lilypond/tfm:/sw/share/lilypond/scm:/sw/share/lilypond/mf/out:/sw/
share/lilypond/afm:/sw/share/lilypond/ly::include-mvmt1:/Users/
spamguy/
tchai_op35')
:
\include "defs.ly"
Is it valid, ie, is defs.ly in the search path that is printed, or
not?
If it valid, there is little need to mail this list; you need simply
to resolve it. If it is not valid, you found a bug. In that case,
you're invited to supply a simple test case that shows the bug, so
that we can fix it.