![]() Rebuild your freetype recipe -without-harfbuzz to match the xquartz linker flags. pc files from your recipes first, before falling back to the xquartz ones. Instead of simulating internal Windows logic like a virtual machine or emulator, Wine translates Windows API calls into POSIX calls on-the-fly. Prepend /usr/local/lib/pkgconfig to your PKG_CONFIG_PATH. Wine (originally an acronym for 'Wine Is Not an Emulator') is a compatibility layer capable of running Windows applications on several POSIX-compliant operating systems, such as Linux, macOS, & BSD. pc file.īecause you hardcode -L/usr/local/lib when building the R package, it ends up linking to the recipe freetype, even though pkg-config has given us the flags needed to link to the xQuartz freetype. Then you have another freetype recipe which you (probably unintentionally) have built against harfbuzz. pc file: one is provided by xquartz in /opt/X11/ and that one gets picked up by pkg-config. The problem is that you have two freetypes on your server, each with their own. ![]() The systemfonts package does everything correct: it calls pkg-config -libs -static freetype to get the linker flags on your server to link to freetype. ![]() The systemfonts package has a linking error about a missing symbol from harfbuzz, however this package doesn't actually link to harfbuzz: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |