@ian see http://blog.sourcefrog.net/2009/09/setting-up-ubuntu-chroot-
for.html for what I used to reproduce this.
I can still confirm it's happening in current Karmic. However, since it
can be reproduced in other packages I'm going to downgrade it in bzr. I
do think the Karmic python maintainers should take it more seriously...
** Changed in: bzr
Importance: Critical => High
** Changed in: bzr
Status: Triaged => Confirmed
** Description changed:
+ In Karmic, it seems that distutils build_ext puts compiled extensions
+ into eg 'bzrlib/bzrlib/foo.so' when it should be just 'bzrlib/foo.so',
+ so the extension is not used. This was discovered in Bazaar but
+ reproduced in other places, so seems independent of the program. This
+ is a new regression compared to Jaunty.
+
+ ----
+
C extensions are placed in bzrlib/bzrlib and thus are not used.
- $make
+ $make
setup.py build_ext -i
running build_ext
building 'bzrlib._bencode_pyx' extension
creating .../iter-changes-partial-parents/bzrlib/bzrlib
gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions
build/temp.linux-x86_64-2.6/bzrlib/_bencode_pyx.o -o
.../iter-changes-partial-parents/bzrlib/bzrlib/_bencode_pyx.so
building 'bzrlib._btree_serializer_pyx' extension
gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions
build/temp.linux-x86_64-2.6/bzrlib/_btree_serializer_pyx.o -o
.../iter-changes-partial-parents/bzrlib/bzrlib/_btree_serializer_pyx.so
...
--
C extensions placed in wrong directory on karmic
https://bugs.launchpad.net/bugs/392355
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
