Comment 10 for bug 392355

This problem only affects in-place builds (i.e. "python setup.py build_ext
-i"), which is something that developers will stumble over while doing
development. Distribution builds don't seem to be affected.

On Thu, Aug 27, 2009 at 12:31 PM, James Westby
<<email address hidden><jw%<email address hidden>>
> wrote:

> On Wed Aug 26 22:44:40 UTC 2009 Martin Pool wrote:
> > 2009/8/26 James Westby <<email address hidden><jw%<email address hidden>>
> >:
> > > Martin,
> > >
> > > Why did you add a "bzr (Ubuntu)" task to this bug, I don't see this
> > > happening with the bzr package in Ubuntu.
> >
> > Because I thought it might be a problem there. If not, I'll mark it
> > invalid and apologize for the noise.
>
> No problem, I just wondered if you knew something I didn't.
>
> I made sure to check the contents of the .deb before uploading, and
> they were definitely in bzrlib/*.so as they should be.
>
> Thanks,
>
> James
>
> --
> C extensions placed in wrong directory
> https://bugs.launchpad.net/bugs/392355
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Bazaar Version Control System: Triaged
> Status in “bzr” package in Ubuntu: Invalid
> Status in “python-defaults” package in Ubuntu: New
>
> Bug description:
> C extensions are placed in bzrlib/bzrlib and thus are not used.
>
> $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
> ...
>

--
Aldo Cortesi
www.nullcube.com
+64 210 718 900