Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 224285 - dev-python/pycairo-1.4.0: places pycairo.pc in /usr/lib/pkgconfig instead of /usr/lib64/pkgconfig on amd64
Summary: dev-python/pycairo-1.4.0: places pycairo.pc in /usr/lib/pkgconfig instead of ...
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: AMD64 Linux
: High normal
Assignee: Python Gentoo Team
URL:
Whiteboard:
Keywords:
Depends on: 232327
Blocks:
  Show dependency tree
 
Reported: 2008-05-31 01:32 UTC by Tony S
Modified: 2008-10-02 02:06 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Tony S 2008-05-31 01:32:39 UTC 
pycairo puts pycairo.pc in /usr/lib/pkgconfig.  On amd64 architecture, all other pkgconfig files are found in /usr/lib64/pkgconfig.  Because of this, pkg-config is unable to report the proper version or other information for pycairo.  This causes pygtk (and possibly other apps) to fail during compile.

Reproducible: Always

Steps to Reproduce:
1. Install pycairo on amd64.
2. Look at the location of pycairo.pc.
3. Use pkg-config --modversion pycairo and observe that it fails.

Actual Results:  
pkg-config cannot find pycairo.  pygtk fails to compile because it needs the version information on pycairo to setup function calls properly.

Expected Results:  
The ebuild for pycairo should install pycairo.pc in /usr/lib64/pkgconfig on amd64.

symlinking /usr/lib/pkgconfig/pycairo.pc to /usr/lib64/pkgconfig is a reasonable temporary workaround.
Comment 1 Olivier Crete (RETIRED) gentoo-dev 2008-07-19 13:30:14 UTC 
actually, it only installs a .h file, no .so, so its maybe reasonable to have it in /usr/lib. Btw, pycairo-1.4.12 that was just stabilized still installs it in /usr/lib
Comment 2 Tony S 2008-07-25 00:11:19 UTC 
Here is the pkg manifest for pycairo-1.4.0:

/usr/share/doc/pycairo-1.4.0/README.bz2
/usr/share/doc/pycairo-1.4.0/ChangeLog.bz2
/usr/share/doc/pycairo-1.4.0/NEWS.bz2
/usr/share/doc/pycairo-1.4.0/NOTES.bz2
/usr/share/doc/pycairo-1.4.0/AUTHORS.bz2
/usr/lib64/python2.5/site-packages/cairo/_cairo.so
/usr/lib64/python2.5/site-packages/cairo/__init__.py
/usr/lib64/python2.5/site-packages/pycairo-1.4.0-py2.5.egg-info
/usr/include/pycairo/pycairo.h
/usr/lib/pkgconfig/pycairo.pc

pycairo places its pkg-config definition file in /usr/lib/pkgconfig instead of /usr/lib64/pkgconfig, which is where all other pkgconfig files go on the amd64 platform.  The default pkg-config path on the amd64 platform is /usr/lib64/pkgconfig:/usr/share/pkgconfig.
Comment 3 Santiago M. Mola (RETIRED) gentoo-dev 2008-09-17 10:23:43 UTC 
This is fixed for me with pycairo-1.4.12:
/usr/lib64/pkgconfig/pycairo.pc

Is this still a problem? is your /usr/lib symlinked to /usr/lib64?
Comment 4 Jeremy Olexa (darkside) (RETIRED) archtester gentoo-dev Security 2008-10-02 02:06:33 UTC 
(In reply to comment #3)
> This is fixed for me with pycairo-1.4.12:
> /usr/lib64/pkgconfig/pycairo.pc
> 
> Is this still a problem? is your /usr/lib symlinked to /usr/lib64?
> 

Since 1.4.12 is stabilized now, we can resolve this bug. Please reopen or file a new bug if there are any issues.