It looks like fontforge switched over to cmake / ninja for its build system I've cobbled together an ebuild here: https://github.com/FireBurn/Overlay/blob/master/media-gfx/fontforge/fontforge-20200314.ebuild This seemed easier than trying to add python 3.8 to the current build in portage It also requires this fix from upstream https://github.com/fontforge/fontforge/commit/43e6087ec9bdbb23b8bb61c07efe6490fab23d73 which is also at https://github.com/FireBurn/Overlay/blob/master/media-gfx/fontforge/files/20200314-tilepath.patch Reproducible: Always
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f1024636277d2d1ab20b126f590a30a3457cd992 commit f1024636277d2d1ab20b126f590a30a3457cd992 Author: Mike Gilbert <floppym@gentoo.org> AuthorDate: 2020-03-29 18:03:11 +0000 Commit: Mike Gilbert <floppym@gentoo.org> CommitDate: 2020-03-29 18:08:58 +0000 media-gfx/fontforge: bump to 20200314 Thanks to Mike Lothian for the cmake port. Closes: https://bugs.gentoo.org/714612 Package-Manager: Portage-2.3.96_p4, Repoman-2.3.22_p1 Signed-off-by: Mike Gilbert <floppym@gentoo.org> media-gfx/fontforge/Manifest | 1 + media-gfx/fontforge/files/20200314-tilepath.patch | 31 ++++++ media-gfx/fontforge/fontforge-20200314.ebuild | 111 ++++++++++++++++++++++ media-gfx/fontforge/metadata.xml | 1 + 4 files changed, 144 insertions(+)
All or a lot of packages depending on fontforge fail with SyntaxError. libreoffice, liberation-fonts, dejavu tested
D'oh native scripting isn't enabled in the build diff --git a/media-gfx/fontforge/fontforge-20200314.ebuild b/media-gfx/fontforge/fontforge-20200314.ebuild index a0197c7..a3445ab 100644 --- a/media-gfx/fontforge/fontforge-20200314.ebuild +++ b/media-gfx/fontforge/fontforge-20200314.ebuild @@ -89,7 +89,7 @@ src_configure() { -DENABLE_LIBTIFF=$(usex tiff) -DENABLE_LIBUNINAMESLIST=$(usex unicode) -DENABLE_MAINTAINER_TOOLS=0 - -DENABLE_NATIVE_SCRIPTING=0 + -DENABLE_NATIVE_SCRIPTING=1 -DENABLE_PYTHON_EXTENSION=$(usex python) -DENABLE_PYTHON_SCRIPTING=$(usex python) -DENABLE_SANITIZER=none Should fix the issues
I modified the ebuild to remove -DENABLE_NATIVE_SCRIPTING=0 before I pushed it to gentoo. The option defaults to enabled if not specified.
(In reply to Mike Lothian from comment #3) > D'oh native scripting isn't enabled in the build > > diff --git a/media-gfx/fontforge/fontforge-20200314.ebuild > b/media-gfx/fontforge/fontforge-20200314.ebuild > index a0197c7..a3445ab 100644 > --- a/media-gfx/fontforge/fontforge-20200314.ebuild > +++ b/media-gfx/fontforge/fontforge-20200314.ebuild > @@ -89,7 +89,7 @@ src_configure() { > -DENABLE_LIBTIFF=$(usex tiff) > -DENABLE_LIBUNINAMESLIST=$(usex unicode) > -DENABLE_MAINTAINER_TOOLS=0 > - -DENABLE_NATIVE_SCRIPTING=0 > + -DENABLE_NATIVE_SCRIPTING=1 > -DENABLE_PYTHON_EXTENSION=$(usex python) > -DENABLE_PYTHON_SCRIPTING=$(usex python) > -DENABLE_SANITIZER=none > > Should fix the issues Sorry for the noise. The ebuild from your overlay was installed on my system. Didn't see that when I wrote here before. Thank you 2 for your work.
