All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 7971] python-flask, python-werkzeug. No module named zlib
Date: Mon, 20 Apr 2015 22:00:16 +0000 (UTC)	[thread overview]
Message-ID: <20150420220016.22065819CE@busybox.osuosl.org> (raw)
In-Reply-To: <bug-7971-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=7971

--- Comment #3 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> 2015-04-20 22:00:15 UTC ---
I am using a fr_FR.UTF-8 system. I've built the following defconfig:

BR2_arm=y
BR2_TOOLCHAIN_EXTERNAL=y
BR2_TOOLCHAIN_EXTERNAL_CUSTOM=y
BR2_TOOLCHAIN_EXTERNAL_DOWNLOAD=y
BR2_TOOLCHAIN_EXTERNAL_URL="http://autobuild.buildroot.org/toolchains/tarballs/br-arm-full-2015.02.tar.bz2"
BR2_TOOLCHAIN_EXTERNAL_HEADERS_3_18=y
BR2_TOOLCHAIN_EXTERNAL_INET_IPV6=y
BR2_TOOLCHAIN_EXTERNAL_LOCALE=y
# BR2_TOOLCHAIN_EXTERNAL_HAS_THREADS_DEBUG is not set
BR2_TOOLCHAIN_EXTERNAL_INET_RPC=y
BR2_TOOLCHAIN_EXTERNAL_CXX=y
BR2_PACKAGE_PYTHON=y
BR2_PACKAGE_PYTHON_FLASK=y

And Flask can be imported just fine:

Welcome to Buildroot
buildroot login: root
# python
>>> from flask import Flask
>>> 

So I cannot reproduce the bug reported by Nikita.

-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

  parent reply	other threads:[~2015-04-20 22:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-24 20:43 [Buildroot] [Bug 7971] New: python-flask, python-flask. No module named zlib bugzilla at busybox.net
2015-03-24 20:47 ` [Buildroot] [Bug 7971] " bugzilla at busybox.net
2015-03-24 20:48 ` [Buildroot] [Bug 7971] python-flask, python-werkzeug. " bugzilla at busybox.net
2015-04-10 21:16 ` bugzilla at busybox.net
2015-04-19 12:53 ` bugzilla at busybox.net
2015-04-19 12:54 ` bugzilla at busybox.net
2015-04-20 22:00 ` bugzilla at busybox.net [this message]
2015-06-03  1:09 ` bugzilla at busybox.net

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=20150420220016.22065819CE@busybox.osuosl.org \
    --to=bugzilla@busybox.net \
    --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.