From: Yegor Yefremov <yegor_sub1@visionsystems.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] New package: python-dpkt
Date: Wed, 14 Dec 2011 12:37:55 +0100 [thread overview]
Message-ID: <4EE88A93.3090409@visionsystems.de> (raw)
In-Reply-To: <20111214114650.539556ba@skate>
Am 14.12.2011 11:46, schrieb Thomas Petazzoni:
> Le Wed, 14 Dec 2011 11:39:05 +0100,
> Yegor Yefremov <yegor_sub1@visionsystems.de> a ?crit :
>
>> I have following problem building this package:
>>
>> Traceback (most recent call last):
>> File "setup.py", line 4, in <module>
>> import dpkt
>> File
>> "/home/YegorYefremov/projects/versioned/tests/br-queue-python/output/build/python-dpkt-1.7/dpkt/__init__.py",
>> line 26, in <module> import gzip File
>> "/home/YegorYefremov/projects/versioned/tests/br-queue-python/output/build/python-dpkt-1.7/dpkt/gzip.py",
>> line 5, in <module> import struct, zlib ImportError: No module named
>> zlib
> At build time, the host-python is used. And the fact that you enabled
> "zlib" for the target python has no impact on the configuration of the
> host python. Why does it require zlib support in Python at build time?
> Or, said otherwise, why does it tries to import the dpkt Python module
> you're building, at build time?
This is a good question to maintainer of dpkt. I copied version, author and other stuff from dpkt/_init_.py to setup.py, commented import dpkt and could successfully install this package. Still haven't tested it. Because I need netifaces and this package needs setuptools :-(
Yegor
prev parent reply other threads:[~2011-12-14 11:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-14 10:35 [Buildroot] [PATCH] New package: python-dpkt yegorslists at googlemail.com
2011-12-14 10:39 ` Yegor Yefremov
2011-12-14 10:46 ` Thomas Petazzoni
2011-12-14 11:37 ` Yegor Yefremov [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4EE88A93.3090409@visionsystems.de \
--to=yegor_sub1@visionsystems.de \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.