Summary: | py2cairo, mac os x 10.6.7 xcode 4.0.2 python 2.7 py2cairo cannot build | ||
---|---|---|---|
Product: | pycairo | Reporter: | Rinat <rinat.enikeev> |
Component: | general | Assignee: | Steve Chaplin <d74n5pohf9> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | medium | ||
Version: | unspecified | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Rinat
2011-05-20 10:03:25 UTC
It looks like it is compiling for x86_64 when it should be compiling for i386. The 'arch' options are conflicting with each other - the end of your message has '-arch', 'i386', '-arch', 'x86_64', repeated many times. I suggest trying to discover where these 'arch' options are being set or picked up from. It should be i386 or x86_64, but not both. (I think the last one mentioned wins) I can confirm this problem. I tried building pycairo 1.10.0 on OS X 10.6.8, Python 2.6.1, gcc 4.2.1. It seems waf is over-zealous in what archs it attempts to build for. For me it wanted to build for all of i386, ppc and x86_64. The cairo build system built cairo for only x86_64, and so pycairo failed to link to it. I managed to work around the problem by manually editing build_directory/c4che/_cache.py to remove the -arch arguments. Since 1.11 pycairo uses distutils for building. There is a good chance that this bug no longer occurs with the new system. If there are still problems please file a bug: https://github.com/pygobject/pycairo/issues |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.