pcp
[Top] [All Lists]

Re: [pcp] rpm-based build failures .. moved to python code

To: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Subject: Re: [pcp] rpm-based build failures .. moved to python code
From: Nathan Scott <nathans@xxxxxxxxxx>
Date: Thu, 30 Oct 2014 17:01:55 -0400 (EDT)
Cc: pcp@xxxxxxxxxxx
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <545294D1.3050001@xxxxxxxxxxxxxxxx>
References: <54521217.5030709@xxxxxxxxxxxxxxxx> <545294D1.3050001@xxxxxxxxxxxxxxxx>
Reply-to: Nathan Scott <nathans@xxxxxxxxxx>
Thread-index: 2wZRvM+RdvAcF91L1zpczvb6QGZ7CQ==
Thread-topic: rpm-based build failures .. moved to python code

----- Original Message -----
> [...]
> Anyway, that seems to have passed now, but I'm seeing build failures in the
> python code now (on Fedora 19, I've not delved into the other cases yet) ...
> 
> I've tried make distclean, but Makepkgs fails the same way.
> 
> If it makes any difference, python and python3 are both installed on this
> system

(yep, it does make a difference)

> kenj@vm22:~/src/pcp$ python --version
> Python 2.7.5
> kenj@vm22:~/src/pcp$ python3 --version
> Python 3.3.2

Are both versions of python[3]-devel installed?

> -I../../src/include -I/usr/include/python3.3m -c pmapi.c -o
> build/temp.linux-x86_64-3.3/pmapi.o
> pmapi.c:27:20: fatal error: Python.h: No such file or directory
>  #include <Python.h>
>                     ^
> compilation terminated.

This looks sorta like configure has decided to go ahead with python3
but later we find no python3 devel environment.  There are checks in
configure.ac for this though, its not clear how we are circumventing
those in your case here?

cheers.

--
Nathan

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