From: Andreas Enge <andreas@enge.fr>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix-devel <guix-devel@gnu.org>, Federico Beffa <beffa@ieee.org>
Subject: Re: Changing python-wrapper to handle lib/ etc.
Date: Sun, 2 Nov 2014 22:32:57 +0100 [thread overview]
Message-ID: <20141102213257.GA11661@debian> (raw)
In-Reply-To: <20141102174450.GC6865@debian>
The first problem occurs. Swig does not compile any more:
http://hydra.gnu.org/build/134889/log/raw
There are lots of error messages of the form:
checking testcase namespace_nested under python
namespace_enum_wrap.cxx:154:21: fatal error: Python.h: No such file or directory
# include <Python.h>
If one compares with the version in master:
http://hydra.gnu.org/build/131472/log/raw
one realises that there python was simply not found, so the tests were
probably not executed:
checking for Python header files...
checking for Python library... Not found
checking for python3... no
With the new python wrapper, something is found:
checking for python3-config... python3-config
checking for Python 3.x prefix... /gnu/store/r6614z0w2inxn78wzaa7ic5sai8s7l9f-python-3.3.5
checking for Python 3.x exec-prefix... /gnu/store/r6614z0w2inxn78wzaa7ic5sai8s7l9f-python-3.3.5
checking for Python 3.x version... python3.3
checking for Python 3.x lib dir... lib
checking for Python 3.x header files... -I/gnu/store/r6614z0w2inxn78wzaa7ic5sai8s7l9f-python-3.3.5/include/python3.3m -I/gnu/store/r6614z0w2inxn78wzaa7ic5sai8s7l9f-python-3.3.5/include/python3.3m
checking for Python 3.x library... Not found
Whatever this means! The header files are correctly located in the python3.3m
subdirectory of the include directory. However, the CPATH includes only
the include/ directory itself (logic!). And apparently the tests do not
use the correct include path.
Could maybe a swig specialist have a look?
Andreas
next prev parent reply other threads:[~2014-11-02 21:33 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-26 13:09 [PATCH 1/2] gnu: Add numpy Federico Beffa
2014-10-26 18:56 ` Ludovic Courtès
2014-10-27 20:26 ` Federico Beffa
2014-10-28 9:34 ` Ludovic Courtès
2014-10-28 17:49 ` Federico Beffa
2014-10-29 21:28 ` Ludovic Courtès
2014-10-28 23:34 ` Ludovic Courtès
2014-10-29 22:23 ` Andreas Enge
2014-10-30 13:12 ` Changing python-wrapper to handle lib/ etc Ludovic Courtès
2014-11-02 17:44 ` Andreas Enge
2014-11-02 21:32 ` Andreas Enge [this message]
2014-11-03 10:11 ` Federico Beffa
2014-11-03 10:13 ` Andreas Enge
2014-11-03 20:19 ` Andreas Enge
2014-11-03 20:49 ` Andreas Enge
2014-11-03 22:06 ` Andreas Enge
2014-11-04 9:44 ` Ludovic Courtès
2014-11-04 13:07 ` Andreas Enge
2014-11-04 16:48 ` Ludovic Courtès
2014-11-04 17:08 ` Andreas Enge
2014-11-04 18:26 ` Andreas Enge
2014-11-04 21:40 ` Ludovic Courtès
2014-11-04 22:29 ` Andreas Enge
2014-11-03 9:04 ` Ludovic Courtès
2014-10-29 22:20 ` [PATCH 1/2] gnu: Add numpy Andreas Enge
2014-10-30 16:56 ` Federico Beffa
2014-10-30 17:03 ` Andreas Enge
2014-10-30 17:05 ` Federico Beffa
2014-11-02 18:21 ` Ludovic Courtès
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20141102213257.GA11661@debian \
--to=andreas@enge.fr \
--cc=beffa@ieee.org \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).