pcp
[Top] [All Lists]

Re: [pcp] Another build problem - python bits on Linux Mint 12

To: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Subject: Re: [pcp] Another build problem - python bits on Linux Mint 12
From: Nathan Scott <nathans@xxxxxxxxxx>
Date: Wed, 5 Mar 2014 21:31:19 -0500 (EST)
Cc: PCP Mailing List <pcp@xxxxxxxxxxx>
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <5316DD31.2020700@xxxxxxxxxxxxxxxx>
References: <530FCCED.4000403@xxxxxxxxxxxxxxxx> <1082118100.19105328.1393667279427.JavaMail.zimbra@xxxxxxxxxx> <5316DD31.2020700@xxxxxxxxxxxxxxxx>
Reply-to: Nathan Scott <nathans@xxxxxxxxxx>
Thread-index: +Dri1ejhg0JBbK+5seagJkdiPjY4MQ==
Thread-topic: Another build problem - python bits on Linux Mint 12

----- Original Message -----
> [...]
> for V in 2.7 2.6; do \
>              export GZIP=-9q DIST_ROOT=`pwd`/debian/python-pcp;
> /usr/bin/make PYTHON=python$V -C src/python install; \
> done
> 
> I think the problem is that the first make leaves 2.7 turds behind that
> are not remade for 2.6 ... adding /usr/bin/make -C src/python clean
> after the make install seems to fix this, but I don't know if that
> leaves the tree in a bozo state, and this sort of hack cannot possibly
> work for some other builds, like for tarball packaging.

Yes, that explanation makes sense - and I think that fix will work fine.

> 
> It seems like you need to clone src/python for each version of Python
> that you want to build for, and descend into each of these in turn at
> each step in the build.
> 

Yep, or that - I think your make clean solution above will be simplest.

cheers.

--
Nathan

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