[Matthias Klose, 2015-02-12]
> The interpreter doesn't look up the old "module" name with the multiarch
> suffix.
> Best thing would be to rename it manually (removing the "module" substring.
> Of
> course dh_python2 could do that as well.
dh_python3 already does that for Python >= 3.2. Last ti
Thanks Matthias, removing the 'module' infix fixed the problem for me.
export PYBUILD_AFTER_INSTALL := \
mv {destdir}{install_dir}/khmer/_khmermodule.so \
{destdir}{install_dir}/khmer/_khmer.so
On Thu Feb 12 2015 at 10:55:16 AM Matthias Klose wrote:
> On 02/11/2015 04:04
On 02/11/2015 04:04 PM, Michael Crusoe wrote:
> Hello,
>
> I'm working on the packaging of the khmer project[0] with the debian-med
> team[1] and we've run into an odd problem: dh_python2 renames the Python
> extension shared library from `_khmermodule.so` to a version with a
> mutliarch triplet:
On 11 February 2015 at 14:22, Scott Kitterman wrote:
> Given the filename, shouldn't it be import khmermodule?
foomodule.so was a valid filename for a module 'foo' - though I only heard
about this when that spelling was removed in Python 3.3:
https://docs.python.org/3/whatsnew/3.3.html#building
On February 11, 2015 10:04:50 AM EST, Michael Crusoe
wrote:
>Hello,
>
>I'm working on the packaging of the khmer project[0] with the
>debian-med
>team[1] and we've run into an odd problem: dh_python2 renames the
>Python
>extension shared library from `_khmermodule.so` to a version with a
>mutliar
Hello,
I'm working on the packaging of the khmer project[0] with the debian-med
team[1] and we've run into an odd problem: dh_python2 renames the Python
extension shared library from `_khmermodule.so` to a version with a
mutliarch triplet: `_khmermodule.x86_64-linux-gnu.so`. This breaks module
loa
6 matches
Mail list logo
