FS#43373 - [fontforge] libspiro is not linking to fontforge

Attached to Project: Arch Linux
Opened by lief swanson (liefswanson) - Wednesday, 07 January 2015, 19:36 GMT
Last edited by Gaetan Bisson (vesath) - Sunday, 01 February 2015, 07:59 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Gaetan Bisson (vesath)
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Fontforge does not properly link to one of it's dependencies spiro. The program runs, but it cannot use libspiro to do spiro curve editing.

Additional info:
* package version(s)
fontforge x86_64 20141126-2
libspiro x86_64 1:0.2-2

* config and/or log files etc.
No special configuration I have everything installed.
May be worth noting that i think the problem is with lib spiro specifically. I tried compiling my own fontforge and it didn't end up linking to the .so files i had from libspiro in the repos.
... but they are definitely there.

pacman -Ql libspiro

libspiro /usr/
libspiro /usr/include/
libspiro /usr/include/bezctx.h
libspiro /usr/include/bezctx_intf.h
libspiro /usr/include/spiro.h
libspiro /usr/include/spiroentrypoints.h
libspiro /usr/lib/
libspiro /usr/lib/libspiro.so
libspiro /usr/lib/libspiro.so.0
libspiro /usr/lib/libspiro.so.0.0.2
libspiro /usr/lib/pkgconfig/
libspiro /usr/lib/pkgconfig/libspiro.pc



Steps to reproduce:
open fontforge, click the spiro editing tool. A window bearing an error message will show up and read as
"This version of fontforge is not linked with the spiro library, you may not use them."
This task depends upon

Closed by  Gaetan Bisson (vesath)
Sunday, 01 February 2015, 07:59 GMT
Reason for closing:  Fixed
Additional comments about closing:  20141126-3 in [extra]
Comment by Gaetan Bisson (vesath) - Friday, 09 January 2015, 19:19 GMT
Do you have any idea how this may be fixed?
Comment by Gaetan Bisson (vesath) - Sunday, 18 January 2015, 21:56 GMT
This issue is fixed with upstream git HEAD; they're in the process of cutting a new release.

Loading...