Bug 822413 - inkscape doesn't build with poppler-0.20.0
Summary: inkscape doesn't build with poppler-0.20.0
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: inkscape
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Lubomir Rintel
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-05-17 09:53 UTC by Marek Kašík
Modified: 2012-06-23 19:37 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-23 19:37:29 UTC


Attachments (Terms of Use)
Patch (26.86 KB, patch)
2012-05-27 00:44 UTC, Sandro Mani
no flags Details | Diff

Description Marek Kašík 2012-05-17 09:53:49 UTC
Description of problem:
inkscape fails when built with new poppler-0.20.0.


Version-Release number of selected component (if applicable):
inkscape-0.48.2-5


Additional info:
This patch should fix the problem:
https://projects.archlinux.org/svntogit/packages.git/tree/trunk/poppler20.patch?h=packages/inkscape

Comment 1 Sandro Mani 2012-05-27 00:44:42 UTC
Created attachment 587053 [details]
Patch

Patch modified to apply cleanly on top of existing fedora package patches.

Comment 2 Alex Valavanis 2012-06-08 10:51:29 UTC
See upstream Inkscape bug: https://launchpad.net/bugs/1005565

Comment 3 Rex Dieter 2012-06-23 15:41:00 UTC
0.48.2-8

- fix icon/desktop-file scriptlets (#739375)
- drop .desktop vendor (f18+)
- inkscape doesn't build with poppler-0.20.0 (#822413)


http://koji.fedoraproject.org/koji/taskinfo?taskID=4190484

Comment 4 Rex Dieter 2012-06-23 15:59:48 UTC
boo, patch doesn't seem to work as advertised, looking closer now.

Comment 5 Rex Dieter 2012-06-23 16:39:36 UTC
Hrm, seems to build ok locally on my f17 x86_64 box with poppler-0.20.0-1 installed.  Something odd going on. (f18 gcc/glibc differences?, missing builddep?)

Comment 6 Kevin Kofler 2012-06-23 18:03:11 UTC
From the build failure, it looks like the first argument to the function "error" is being eaten somewhere, maybe something defining "error" as a macro?

Comment 7 Rex Dieter 2012-06-23 19:37:29 UTC
OK, the version of the patch from https://launchpad.net/bugs/1005565 works, build succeeds now.


Note You need to log in before you can comment on or make changes to this bug.