Bug#917291: libass9 issue

[Tommy Wu]

I think this is not bug in harfbuzz 2.x, it should be the libass9 issue, the 
API change after harfbuzz 2.0.0, it's not compatible with libass 0.14 now.
recompile libass9 with --disable-harfbuzz option will solve this issue.

--