shiboken pkg-config file contains bad formatted data

Bug #1155595 reported by David Garcia Garzon on 2013-03-15
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
CLAM
In Progress
Unknown
shiboken (Ubuntu)
Undecided
Unassigned

Bug Description

$ cat /usr/lib/x86_64-linux-gnu/pkgconfig/shiboken.pc
prefix=/usr
exec_prefix=/usr
libdir=/usr/lib/x86_64-linux-gnu
includedir=/usr/include/shiboken
generator_location=/usr/bin/shiboken
python_interpreter=/usr/bin/python2.7
python_include_dir=/usr/include/python2.7;/usr/include/x86_64-linux-gnu/python2.7

Name: shiboken
Description: Support library for Python bindings created with Shiboken generator.
Version: 1.1.2
Libs: /usr/lib/x86_64-linux-gnu/libpython2.7.so -L${libdir} -lshiboken-python2.7
Cflags: -I/usr/include/python2.7;/usr/include/x86_64-linux-gnu/python2.7 -I${includedir}/

Many things in this file are wrong.
1. defining in Cflags: tag a -I flag with two directories separated with a semicolon, should be two -I options
2. Including in the Libs: the full python library path with no option, it should have -lpython2.7 instead

Maybe a Depends: clause on python-2.7, which provides also a pc file, would solve the problem better.

Related branches

This bugs affects 'raring'. Until 'quantal' worked well.

Changed in clam:
status: Unknown → In Progress
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package shiboken - 1.2.1-2

---------------
shiboken (1.2.1-2) unstable; urgency=low

  * Rewrite debian/copyright with CF-1.0 (Closes: #722504)
  * Correct the default python suffix for python3, make sure cmake's
    default is python2's

 -- Didier Raboud <email address hidden> Wed, 18 Sep 2013 20:07:19 +0200

Changed in shiboken (Ubuntu):
status: New → Fix Released

This error is still persitent in 1.1.2-4

Cflags is still defined as:

      Cflags: -I/usr/include/python2.7;/usr/include/x86_64-linux-gnu/python2.7 -I${includedir}/

Which causes problems with the semicolon in any command you use pkg-config.
Seems to be autogenerated.

Instead hardcoding the paths, a line like:
      Depends: python2.7
would do the job and ease maintenance.

prefix=/usr
exec_prefix=/usr
libdir=/usr/lib/x86_64-linux-gnu
includedir=/usr/include/shiboken
generator_location=/usr/bin/shiboken
python_interpreter=/usr/bin/python2.7
python_include_dir=/usr/include/python2.7;/usr/include/x86_64-linux-gnu/python2.7

Name: shiboken
Description: Support library for Python bindings created with Shiboken generator.
Depends: python2.7
Version: 1.1.2
Libs: -lshiboken-python2.7
Cflags: -I${includedir}/

Sorry, its 'Requires', not 'Depends', and python-2.7 not python2.7, so i meant:

prefix=/usr
exec_prefix=/usr
libdir=/usr/lib/x86_64-linux-gnu
includedir=/usr/include/shiboken
generator_location=/usr/bin/shiboken
python_interpreter=/usr/bin/python2.7
python_include_dir=/usr/include/python2.7;/usr/include/x86_64-linux-gnu/python2.7

Name: shiboken
Description: Support library for Python bindings created with Shiboken generator.
Requires: python-2.7
Version: 1.1.2
Libs: -lshiboken-python2.7
Cflags: -I${includedir}/

oops, ok i understood that the fixed version was not 1.2.1-2 but 1.1.2-2 and i was surprised that still persistent 1.1.2-4. Nevermind, ignore my previous comments. I will test it when I'll jump to Trusty.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.