From: Tay Ray Chuan <rctay89@gmail.com>
To: Oliver Kullmann <O.Kullmann@swansea.ac.uk>
Cc: git@vger.kernel.org, Sverre Rabbelier <srabbelier@gmail.com>
Subject: Re: error when installing 1.7.0.1: "ImportError: No module named distutils.core"
Date: Mon, 1 Mar 2010 23:15:20 +0800 [thread overview]
Message-ID: <be6fef0d1003010715l31d7b49bs36ee69685e1684e8@mail.gmail.com> (raw)
In-Reply-To: <20100301144000.GA17135@cs-wsok.swansea.ac.uk>
Hi,
On Mon, Mar 1, 2010 at 10:40 PM, Oliver Kullmann
<O.Kullmann@swansea.ac.uk> wrote:
> make[3]: Leaving directory `/home/csoliver/SAT-Algorithmen/OKplatform/ExternalSources/builds/Git/git-1.7.0.1/perl'
> make[2]: Leaving directory `/home/csoliver/SAT-Algorithmen/OKplatform/ExternalSources/builds/Git/git-1.7.0.1/perl'
> make[2]: Entering directory `/home/csoliver/SAT-Algorithmen/OKplatform/ExternalSources/builds/Git/git-1.7.0.1/git_remote_helpers'
> Traceback (most recent call last):
> File "setup.py", line 5, in ?
> from distutils.core import setup
> ImportError: No module named distutils.core
(adding Sverre to the Cc list, perhaps he has something to add)
you need to install setuptools from python, or pass NO_PYTHON to make/configure.
> I've checked the README and INSTALL file, but I don't see that there are new
> requirements? (That is not regarding doc.)
I guess we should improve on this.
--
Cheers,
Ray Chuan
next prev parent reply other threads:[~2010-03-01 15:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-01 14:40 error when installing 1.7.0.1: "ImportError: No module named distutils.core" Oliver Kullmann
2010-03-01 15:15 ` Tay Ray Chuan [this message]
2010-03-01 15:24 ` Sverre Rabbelier
2010-03-01 18:21 ` Julian Phillips
2010-03-01 18:32 ` Sverre Rabbelier
2010-03-01 16:15 ` Todd Zullinger
-- strict thread matches above, loose matches on Subject: below --
2010-03-01 17:04 Oliver Kullmann
2010-03-01 17:26 ` Sverre Rabbelier
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=be6fef0d1003010715l31d7b49bs36ee69685e1684e8@mail.gmail.com \
--to=rctay89@gmail.com \
--cc=O.Kullmann@swansea.ac.uk \
--cc=git@vger.kernel.org \
--cc=srabbelier@gmail.com \
/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 NNTP newsgroup(s).