Am Montag, den 27.04.2020, 09:41 +0200 schrieb Jonas Hahnfeld: > To set some context: You're trying to release 2.21.1 from the > release/unstable branch? I'd have expected an announcement that a new > release is imminent to lilypond-devel beforehand, so others could have > stopped pushing to staging / master and complicating the release. > > Am Montag, den 27.04.2020, 07:46 +0100 schrieb Phil Holmes: > > I am currently getting this error when trying to build GUB: > > > > Tail of target/tools/log/fontforge.log >>>>>>>> > > checking Build with LibUniNamesList Unicode support?... configure: error: in > > `/home/gub/NewGub/gub/target/tools/build/fontforge-20190801': > > configure: error: You may provide option `--without-libuninameslist` to > > build without this recommended feature > > See `config.log' for more details > > Command barfed: cd > > /home/gub/NewGub/gub/target/tools/build/fontforge-20190801 && chmod +x > > /home/gub/NewGub/gub/target/tools/src/fontforge-20190801/configure && sh > > /home/gub/NewGub/gub/target/tools/src/fontforge-20190801/configure > > --prefix=/home/gub/NewGub/gub/target/tools/root/usr > > --enable-shared --enable-static --disable-silent-rules --without-cairo > > --without-x > > --enable-python-scripting=3 > > CFLAGS=-I/home/gub/NewGub/gub/target/tools/root/usr/include > > LDFLAGS='-L/home/gub/NewGub/gub/target/tools/root/usr/lib -Wl,-rpath > > -Wl,\$$ORIGIN/../lib > > -Wl,-rpath -Wl,/home/gub/NewGub/gub/target/tools/root/usr/lib ' > > > > Should I just add the "--without-libuninameslist" option to the fontforge > > command line in GUB? > > Probably Werner knows better what libuninameslist is used for. > Alternatively we could go back to using FontForge 20190413 -- according > to the release notes, 20190801 was the first version to require the > "new" dependency.
Well, that library is *so* easy to build that it certainly can't hurt to add it: https://github.com/gperciva/gub/pull/73 Please give it a try!
signature.asc
Description: This is a digitally signed message part