Fix autotools's harfbuzz.cc build How this works? gen-harfbuzzcc.py operates at its own source path (see its 7th line) and that is reliable when used both on meson and autotools. Just like 19ecabed, weirdly this didn't come up sooner, guess it has something to do with timestamps. Fortunately whole harfbuzz.cc just doesn't matter for packagers but we can tag a release only for this if needed.