Thanks for your reply, Werner.  What I did is the following:

$ git pull ; LANG=C make all | tail
Already up-to-date.
make[1]: *** No rule to make target '/usr/include/freetype2/freetype.h', needed 
by 'out/vaticana-ligature.o'.  Stop.
make: *** [all] Error 2
make[2]: Entering directory '/home/tom/devel/lilypond/scripts/build'
true
make[2]: Leaving directory '/home/tom/devel/lilypond/scripts/build'
make[1]: Leaving directory '/home/tom/devel/lilypond/scripts'
make[1]: Entering directory '/home/tom/devel/lilypond/flower'
true
make[1]: Leaving directory '/home/tom/devel/lilypond/flower'
make[1]: Entering directory '/home/tom/devel/lilypond/lily'
make[1]: Leaving directory '/home/tom/devel/lilypond/lily'
/home/tom/devel/lilypond/stepmake/stepmake/generic-targets.make:6: recipe for 
target 'all' failed


Am 21.09.2016 um 08:39 schrieb Werner LEMBERG:
>
> However, if you use
> either the `freetype-config' script or the `freetype2.pc' file for
> pkg-config tool to specify the header include directory, together with
> proper header macros like FT_FREETYPE_H in the source code, nothing
> should change for compilation.


Pardon my ignorance - how would I have to use freetype-config or how would I 
have to manipulate freetype2.pc?  I tried changing the line "Cflags: 
-I${includedir}/freetype2" to "Cflags: -I${includedir}/freetype2/freetype", but 
the headers are still not found.

Thomas

_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Reply via email to