unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Wade Zhang <dochang@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Issue about building python on a foreign distro
Date: Mon, 23 Aug 2021 18:41:04 +0200	[thread overview]
Message-ID: <CAJ3okZ3uMjAeWEBV6Zo+zHiOK43WpUtZiqjsWEG6JSQAg28kZg@mail.gmail.com> (raw)
In-Reply-To: <CANBNykuUganjSKkvaofcicxhO=itzUtAbLZXLQcpyWO0B4MF=A@mail.gmail.com>

Hi,

Welcome! :-)

On Sun, 22 Aug 2021 at 23:39, Wade Zhang <dochang@gmail.com> wrote:

> Recently I installed Guix on a Debian buster host.  I want to install all build
> dependencies by Guix.  Since I use pyenv to manage Python versions, I have to
> install Python outside Guix.  Now I get stuck during the Python installation.

[...]

> It seems all dependencies installed by Guix are not found.

Well, do you do

  source ~/.guix-profile/etc/profile

after installing all the dependencies (gcc-toolchain, bzip2, etc.)

> Could you please tell me the reason of these errors and how to fix them?

I do not use 'pyenv' and I had bad experience when mixing "package
manager".  To have other Python versions than the default ones, I
would create variant by using package transformation

  guix build python
--with-source=python=https://www.python.org/ftp/python/3.8.11/Python-3.8.11.tar.xz

but there is no guarantee it works for all the versions. Well, I would
start by a package transformation at the command-line and if it fails
then compile --without-tests or create a package variant and use
--load-path.


Hope that helps,
simon


  reply	other threads:[~2021-08-23 16:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-22 11:27 Issue about building python on a foreign distro Wade Zhang
2021-08-23 16:41 ` zimoun [this message]
2021-08-23 19:30   ` Wade Zhang
2021-08-25 13:08     ` zimoun
2021-08-29 22:29       ` Wade Zhang
2021-09-16 11:24 ` Hartmut Goebel

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAJ3okZ3uMjAeWEBV6Zo+zHiOK43WpUtZiqjsWEG6JSQAg28kZg@mail.gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=dochang@gmail.com \
    --cc=help-guix@gnu.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).