Bug 1015094 - Unable to build inkscape from src.rpm
Summary: Unable to build inkscape from src.rpm
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: inkscape
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: beta
: 7.0
Assignee: Jan Horak
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-03 12:49 UTC by Martin Simon
Modified: 2016-09-20 02:15 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-12-17 14:26:35 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Martin Simon 2013-10-03 12:49:44 UTC
Description of problem:
I'm unable to build inkscape using source data from src.rpm. We use it to execute upstream testsets (via `make check`).

There is an extra comma "," at the end of one line. In upstream I can see the extra character is removed correctly.

Version-Release number of selected component (if applicable):
inkscape-0.48.4-7.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1. get src.rpm, extract sources and after configuring execute `make`

Actual results:
...
In file included from desktop.cpp:91:0:
widgets/desktop-widget.h:242:32: error: stray ‘,’ at end of member declaration
     GtkWidget *commands_toolbox,;
                                ^
...

Expected results:
inkscape should be built correctly

Additional info:

Comment 1 Jan Horak 2013-12-17 14:26:35 UTC
You should run tests on patched sources by doing 'rhpkg prep' or 'rpmbuild -bp' with srpm. Otherwise you're testing original sources and not sources which was actually used to build the package.

The wrong widgets/desktop-widget.h is in upstream tarball, see 
http://downloads.sourceforge.net/inkscape/inkscape-0.48.4.tar.gz if interested. However it is fixed in latest trunk, so . We have inkscape-0.48.4-spuriouscomma.h patch to fix this problem.


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