[Python-modules-team] Bug#640345: python-jpype: FTBFS: src/native/common/include/jpype.h:45:17: fatal error: jni.h: No such file or directory

Mònica Ramírez Arceda monica at probeta.net
Sun Sep 4 12:34:01 UTC 2011


Source: python-jpype
Version: 0.5.4.2-1
Severity: serious
Tags: wheezy sid
User: debian-qa at lists.debian.org
Usertags: qa-ftbfs-2011-09-02 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -g -O2 -fPIC -I/usr/lib/jvm/java-6-openjdk/include -I/usr/lib/jvm/java-6-openjdk/include/linux -Isrc/native/common/include -Isrc/native/python/include -I/usr/include/python2.7 -c src/native/common/jp_primitivetypes_autogen.cpp -o build/temp.linux-x86_64-2.7/src/native/common/jp_primitivetypes_autogen.o
> cc1plus: warning: command line option '-Wstrict-prototypes' is valid for Ada/C/ObjC but not for C++ [enabled by default]
> In file included from src/native/common/jp_primitivetypes_autogen.cpp:21:0:
> src/native/common/include/jpype.h:45:17: fatal error: jni.h: No such file or directory
> compilation terminated.
> error: command 'gcc' failed with exit status 1
> dh_auto_build: python2.7 setup.py build --force returned exit code 1
> make: *** [build] Error 1

The full build log is available from:
   http://people.debian.org/~lucas/logs/2011-09-02/python-jpype_0.5.4.2-1_lsid64.buildlog

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot.  Internet was not
accessible from the build systems.





More information about the Python-modules-team mailing list