On Fri, 23 Sep 2016 at 10:14 Werner LEMBERG wrote:
>
> > What I did was:
> >
> > $ sudo ln -s /usr/include/freetype2/freetype/config
> /usr/include/freetype2/config
> > $ sudo sed -i 's|/freetype2$|/freetype2/freetype|'
> /usr/lib/x86_64-linux-gnu/pkgconfig/freetype2.pc
> > $
> What I did was:
>
> $ sudo ln -s /usr/include/freetype2/freetype/config
> /usr/include/freetype2/config
> $ sudo sed -i 's|/freetype2$|/freetype2/freetype|'
> /usr/lib/x86_64-linux-gnu/pkgconfig/freetype2.pc
> $ ./configure
> $ make
>
> Which gives me a working lilypond 2.19.49. What I
Thanks for bringing me on track, Werner. I was able to solve the problem in a
quick and dirty manner, however it would be useful to learn how to solve it
properly.
What I did was:
$ sudo ln -s /usr/include/freetype2/freetype/config
/usr/include/freetype2/config
$ sudo sed -i
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
> When I try to "make" Lilypond on Ubuntu 16.04, the freetype headers
> are expected to be located in /usr/include/freetype2/. That's also
> where Ubuntu's package libfreetype6-dev used to put them, at least
> in Ubuntu versions 14.04 to 15.10, but in 16.04 (also 12.04,
> interestingly), it's in
When I try to "make" Lilypond on Ubuntu 16.04, the freetype headers are
expected to be located in /usr/include/freetype2/. That's also where Ubuntu's
package libfreetype6-dev used to put them, at least in Ubuntu versions 14.04 to
15.10, but in 16.04 (also 12.04, interestingly), it's in