inconsistent python2.7 include multiarch paths

Bug #1088988 reported by Dimitri John Ledkov
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
python2.7 (Ubuntu)
Fix Released
High
Unassigned

Bug Description

$ python-config --includes
-I/usr/include/python2.7 -I/usr/include/x86_64-linux-gnu/python2.7

$ pkg-config --cflags-only-I python-2.7
-I/usr/include/python2.7 -I/usr/include/x86_64-linux-gnu/python2.7m

$ dpkg -S /usr/include/x86_64-linux-gnu/python2.*
libpython2.7-dev:amd64: /usr/include/x86_64-linux-gnu/python2.7
libpython2.7-dbg:amd64: /usr/include/x86_64-linux-gnu/python2.7_d

It seems like there is inconsistency in the multiarch include paths above.

Changed in python2.7 (Ubuntu):
importance: Undecided → High
status: New → Confirmed
Revision history for this message
Matthias Klose (doko) wrote :

yes, the m is a typo

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package python2.7 - 2.7.3-12ubuntu1

---------------
python2.7 (2.7.3-12ubuntu1) raring; urgency=low

  * Merge with Debian; remaining changes:
    - Regenerate the control file.

python2.7 (2.7.3-12) experimental; urgency=low

  * Fix typo in pkgconfig file. Closes: #695671, LP: #1088988.
 -- Matthias Klose <email address hidden> Tue, 11 Dec 2012 23:38:03 +0100

Changed in python2.7 (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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