pcp
[Top] [All Lists]

Re: [pcp] Python requirement

To: Martins Innus <minnus@xxxxxxxxxxx>
Subject: Re: [pcp] Python requirement
From: Nathan Scott <nathans@xxxxxxxxxx>
Date: Wed, 25 Feb 2015 18:10:27 -0500 (EST)
Cc: PCP <pcp@xxxxxxxxxxx>
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <54ECCB1B.7030705@xxxxxxxxxxx>
References: <54ECCB1B.7030705@xxxxxxxxxxx>
Reply-to: Nathan Scott <nathans@xxxxxxxxxx>
Thread-index: Mla8VPdJXJCkxnYWJ456gHT67cPxpA==
Thread-topic: Python requirement
Hi Martins,

----- Original Message -----
> [...]  So python configuration was disabled. The core of pcp
> built fine and installed, but QA failed very early on with:
> [...]
> I know that there is ongoing python work currently, but since this is a
> new VM type for me, I'm not sure if this is a new issue or not.

It's a new issue.

> I was able to work around this by doing:
> 
> env PYTHON=python2.6 Makepkgs

Oh that is interesting - there's a python 2.6 on RHEL5 after all -
we could find ways to use it instead of disabling python entirely.

> and everything seems to work out fine, python pcp pieces are built, qa
> works etc.
> 
> Is that the suggested procedure on older machines?  Does QA require
> python to work in general?

It should not be required, but accidentally is at the moment - one of
the makefiles is missing a guard, I'll push that fix in shortly.

cheers.

--
Nathan

<Prev in Thread] Current Thread [Next in Thread>