libical config error Cannot find Python.h
david at vizion2000.net
Wed Aug 26 08:19:24 UTC 2009
> -----Original Message-----
> From: owner-freebsd-ports at freebsd.org
> [mailto:owner-freebsd-ports at freebsd.org] On Behalf Of Greg Larkin
> Sent: 25 August 2009 11:51
> To: david at vizion2000.net
> Cc: gnome at freebsd.org; freebsd-ports at freebsd.org
> Subject: Re: libical config error Cannot find Python.h
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> david at vizion2000.net wrote:
> > On a freebsd 7.2-RELEASE-p3 amd64 compiled August 20 12.54.34 BST
> > Python.h is in
> > /usr/local/include/python2.6/
> > devel/libical build fails during configure:
> > checking for swig... (cached) true
> > checking for python2.6/Python.h usability... no checking
> > python2.6/Python.h presence... no checking for
> > no
> > configure: error: Can't find python header files ===> Script
> > "configure" failed unexpectedly.
> > In the libical/work/libical-0.43/config.log
> > The following lines appear to be significant
> > "In file included from conftest.c:81:
> > /usr/local/include/python2.6/Python.h:168:17: error: pth.h: No such
> > file or directory
> > configure:21819: $? = 1
> > configure: failed program was:
> > | /* confdefs.h. */
> > ..
> > ..
> > configure:21842: result: no
> > configure:21846: checking python2.6/Python.h presence .
> > .
> > .
> > configure:21882: result: no
> > configure:21917: checking for python2.6/Python.h
> > configure:21924: result: no
> > configure:21931: error: Cant find python header files
> > ___________________
> > pth.h is in
> > /usr/local/include/pth/pth.h
> > Solving this is urgent for me as a number of ports I need are
> > dependent upon this one. I have just completed an upgrade
> to p3 and am
> > also upgrading all the ports.
> > Thanks in advance
> > David
> Hi David,
> It appears that you have GNU Pth enabled in your python 2.6
> build. Is that required for your site? If not, I would try
> disabling it, rebuilding python and then rebuilding libical.
> If you do need GNU Pth in your python build, you can get past
> the libical configuration phase with this patch:
> However, the compilation still fails in icalmemory.c due to
> conflicting definitions for the pthread functions. I haven't
> figured that one out, and I've cc'd the port maintainer team
> in case any of them have any ideas.
> - --
> Greg Larkin
> http://www.FreeBSD.org/ - The Power To Serve
> http://www.sourcehosting.net/ - Ready. Set. Code.
> http://twitter.com/sourcehosting/ - Follow me, follow you
Thanks Greg -- as usual your are right on the button. I have done as you
suggested and disabled the GNU Pth which I would have prefered to have but
can get round for a while.
devel/libical then built fine as did a rebuild of deskutils/alacarte which
also suffers from the same problems.
I would be interested to hear of a solution to the GNU Pth limitation .
Until that is
solved maybe the maintainer could consider dropping the option so none else
into the trap!!
Thanks again for your thoughtfulness and insight
More information about the freebsd-gnome