Bug 1191583 - swig 3.0.3 and later breaks libgpod build
Summary: swig 3.0.3 and later breaks libgpod build
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: libgpod
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Bastien Nocera
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-02-11 14:34 UTC by Peter Robinson
Modified: 2015-02-12 13:12 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-02-12 13:12:55 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Update comment in gpod.i.in (607 bytes, patch)
2015-02-12 08:13 UTC, Jitka Plesnikova
no flags Details | Diff

Description Peter Robinson 2015-02-11 14:34:52 UTC
Similar to this build any swig higher than 3.0.2 breaks the libgpod build

https://bugs.funtoo.org/browse/FL-1937

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

Comment 1 Jitka Plesnikova 2015-02-12 08:12:01 UTC
I am not swig expert, but it seems the problem is with using comment in gpod.i.in.

The comment below should be either remove or change to C comment. Otherwise it is handled by preprocessor as a macro, because it is not part of %pythoncode block.

# be nicer to decode these utf8 strings into Unicode objects in the C
# layer. Here we are leaving it to the Python side, and just giving
# them utf8 encoded Strings.

I created small patch and it fixed the build issue for me.

Comment 2 Jitka Plesnikova 2015-02-12 08:13:14 UTC
Created attachment 990794 [details]
Update comment in gpod.i.in

Comment 3 Jitka Plesnikova 2015-02-12 08:24:53 UTC
The issue was previously ignored, but now it is reported as error.

So, change the lines which start with # but which aren't preprocessor statements to not start with # - SWIG allows C++-style comments, so you can use // instead on those lines.

Comment 4 Peter Robinson 2015-02-12 13:12:55 UTC
Thanks for the help, pushed


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