Merge lp:~jtaylor/ubuntu/precise/python-numpy/multiarch-fix-818867 into lp:ubuntu/precise/python-numpy
Status: | Merged |
---|---|
Merge reported by: | Julian Taylor |
Merged at revision: | not available |
Proposed branch: | lp:~jtaylor/ubuntu/precise/python-numpy/multiarch-fix-818867 |
Merge into: | lp:ubuntu/precise/python-numpy |
Diff against target: |
49 lines (+29/-0) 3 files modified
debian/changelog (+7/-0) debian/patches/search-multiarch-paths.patch (+21/-0) debian/patches/series (+1/-0) |
To merge this branch: | bzr merge lp:~jtaylor/ubuntu/precise/python-numpy/multiarch-fix-818867 |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Serge Hallyn | Approve | ||
Ubuntu branches | Pending | ||
Review via email: mp+87165@code.launchpad.net |
Description of the change
make numpy's distutils multiarch aware.
See bug 818867 and its duplicate.
the method is very ugly due to the lack of a proper way to get the triplet in python.
Ideally numpy's distutil should not need to know the paths at all and leave that to the compiler but that is a major change better left to upstream once multiarch has settled a bit.
one can test the patch with natty's python-enable package (oneiric's has been patched to work around the issue).
without numpy's patch you get this result:
ldd -r ./usr/lib/
linux-vdso.so.1 => (0x00007fff82a1
libstdc++.so.6 => /usr/lib/
libgcc_s.so.1 => /lib/x86_
libpthread.so.0 => /lib/x86_
libc.so.6 => /lib/x86_
libm.so.6 => /lib/x86_
/lib64/
undefined symbol: XCreateImage (./usr/
undefined symbol: XOpenDisplay (./usr/
undefined symbol: XCloseDisplay (./usr/
undefined symbol: XFreeGC (./usr/
undefined symbol: XCreateGC (./usr/
undefined symbol: XPutImage (./usr/
with the patch it correcly links with X11
Thanks very much for taking the time to submit this fix.
The debdiff looks good. I've tested the fix, and it worked for me.