all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 26136@debbugs.gnu.org
Subject: bug#26136: core-updates: python-minimal@2.7.13 fails due to missing zlib
Date: Sun, 19 Mar 2017 15:26:36 -0400	[thread overview]
Message-ID: <20170319192636.GA16604@jasmine> (raw)
In-Reply-To: <20170318211901.35ed1744@scratchpost.org>

On Sat, Mar 18, 2017 at 09:19:01PM +0100, Danny Milosavljevic wrote:
> >There is also the question about zlib and the bundled pip: why is it
> >failing now?
> 
> The above doesn't fix the pip zlib problem.  It's very strange: The
> value of the environment variable C_INCLUDE_PATH includes bzip2 but
> not zlib.  Might make python unable to find zlib.
> 
> setup.py does some strange stuff with reading the zlib.h header file
> manually - maybe that broke.  Then it tries to find the library file
> for libz.  The value of the environment variable LIBRARY_PATH doesn't
> contain zlib either.

Ideally, the minimal Python variants could use the bundled zlib found at
'Modules/zlib'. We sort of gave up on this with python-minimal@3 the
last time we had this problem, but maybe we can solve it now :)

  parent reply	other threads:[~2017-03-19 19:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-17  1:46 bug#26136: core-updates: python-minimal@2.7.13 fails due to missing zlib Leo Famulari
2017-03-17 14:08 ` Danny Milosavljevic
2017-03-18 17:26   ` Leo Famulari
2017-03-18 20:19     ` Danny Milosavljevic
2017-03-19 19:19       ` Leo Famulari
2017-03-19 19:26       ` Leo Famulari [this message]
2017-03-19 20:15         ` Leo Famulari
2017-03-19 21:40           ` Ludovic Courtès
2017-03-19 23:02             ` Ludovic Courtès
2017-03-18 20:50     ` Danny Milosavljevic

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=20170319192636.GA16604@jasmine \
    --to=leo@famulari.name \
    --cc=26136@debbugs.gnu.org \
    --cc=dannym@scratchpost.org \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

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.