as a matter of fact, lately, the ardour.org binaries are built statically to a (lib)freetype2 version (for TrueType font rendering) that is NOT compatible with modern system distros, so that's why you get the precise error/issue above.
means that, for the time being, you'll need to forcely instate BOTH options above (a. AND b.; not either).
as an after-effect, all the vee-ones will need to embed some font in their guts and not resort to system fontconfig/freetype2, whatever it makes them a little bit more self-contained...
WIP.
cheers
ps. again all this should only pertain to the ardour.org supplied binaries ;)
UPDATE: hopefully this coming v1.4.0 release will nail it quid pro quo ;) check it out!
as a matter of fact, lately, the ardour.org binaries are built statically to a (lib)freetype2 version (for TrueType font rendering) that is NOT compatible with modern system distros, so that's why you get the precise error/issue above.
means that, for the time being, you'll need to forcely instate BOTH options above (a. AND b.; not either).
as an after-effect, all the vee-ones will need to embed some font in their guts and not resort to system fontconfig/freetype2, whatever it makes them a little bit more self-contained...
WIP.
cheers
ps. again all this should only pertain to the ardour.org supplied binaries ;)
UPDATE: hopefully this coming v1.4.0 release will nail it quid pro quo ;) check it out!