Bug#1087436: med-fichier FTBFS with Python 3.13 as supported version
Adrian Bunk
bunk at debian.org
Wed Nov 13 15:15:12 GMT 2024
Source: med-fichier
Version: 4.1.0+repack-6
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/logs.php?pkg=med-fichier&ver=4.1.0%2Brepack-6%2Bb1
...
libtool: compile: g++ -DHAVE_CONFIG_H -I. -I../../python -I../include -I/usr/include/python3.13 -I/usr/include/python3.13 -I../../include -I../include -DH5_USE_16_API -I/usr/lib/x86_64-linux-gnu/hdf5/openmpi/include -DSWIG_TYPE_TABLE=medtable -DSWIGWORDSIZE64 -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/lib/x86_64-linux-gnu/openmpi/include -I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi -DOMPI_SKIP_MPICXX=1 -DMPICH_SKIP_MPICXX=1 -DH5_USE_110_API -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c medmesh_int_wrap.cc -fPIC -DPIC -o .libs/_medmesh_la-medmesh_int_wrap.o
/usr/share/swig/4.2.1/std/std_alloc.i:98: Warning 404: Duplicate template instantiation of 'vector< char >' with name 'MEDCHAR' ignored,
/usr/share/swig/4.2.1/std/std_alloc.i:97: Warning 404: previous instantiation of 'vector< char >' with name 'MEDCHAR'.
/usr/share/swig/4.2.1/std/std_alloc.i:99: Warning 404: Duplicate template instantiation of 'vector< char >' with name 'MEDCHAR' ignored,
/usr/share/swig/4.2.1/std/std_alloc.i:97: Warning 404: previous instantiation of 'vector< char >' with name 'MEDCHAR'.
/usr/share/swig/4.2.1/std/std_alloc.i:98: Warning 404: Duplicate template instantiation of 'vector< char >' with name 'MEDCHAR' ignored,
/usr/share/swig/4.2.1/std/std_alloc.i:97: Warning 404: previous instantiation of 'vector< char >' with name 'MEDCHAR'.
/usr/share/swig/4.2.1/std/std_alloc.i:99: Warning 404: Duplicate template instantiation of 'vector< char >' with name 'MEDCHAR' ignored,
/usr/share/swig/4.2.1/std/std_alloc.i:97: Warning 404: previous instantiation of 'vector< char >' with name 'MEDCHAR'.
medmesh_int_wrap.cc: In function 'PyObject* _wrap_MEDmeshInfoByName(PyObject*, PyObject*, PyObject*)':
medmesh_int_wrap.cc:23634:14: error: 'PyEval_CallObject' was not declared in this scope; did you mean 'PyObject_CallObject'?
23634 | pinst = PyEval_CallObject(pclass, pargs);
| ^~~~~~~~~~~~~~~~~
| PyObject_CallObject
medmesh_int_wrap.cc:23655:14: error: 'PyEval_CallObject' was not declared in this scope; did you mean 'PyObject_CallObject'?
23655 | pinst = PyEval_CallObject(pclass, pargs);
| ^~~~~~~~~~~~~~~~~
| PyObject_CallObject
medmesh_int_wrap.cc:23678:14: error: 'PyEval_CallObject' was not declared in this scope; did you mean 'PyObject_CallObject'?
23678 | pinst = PyEval_CallObject(pclass, pargs);
| ^~~~~~~~~~~~~~~~~
| PyObject_CallObject
medmesh_int_wrap.cc: In function 'PyObject* _wrap_MEDmeshInfo(PyObject*, PyObject*, PyObject*)':
medmesh_int_wrap.cc:23825:14: error: 'PyEval_CallObject' was not declared in this scope; did you mean 'PyObject_CallObject'?
23825 | pinst = PyEval_CallObject(pclass, pargs);
| ^~~~~~~~~~~~~~~~~
| PyObject_CallObject
medmesh_int_wrap.cc:23846:14: error: 'PyEval_CallObject' was not declared in this scope; did you mean 'PyObject_CallObject'?
23846 | pinst = PyEval_CallObject(pclass, pargs);
| ^~~~~~~~~~~~~~~~~
| PyObject_CallObject
medmesh_int_wrap.cc:23869:14: error: 'PyEval_CallObject' was not declared in this scope; did you mean 'PyObject_CallObject'?
23869 | pinst = PyEval_CallObject(pclass, pargs);
| ^~~~~~~~~~~~~~~~~
| PyObject_CallObject
medmesh_int_wrap.cc: In function 'PyObject* _wrap_MEDmeshGridTypeRd(PyObject*, PyObject*, PyObject*)':
medmesh_int_wrap.cc:24164:14: error: 'PyEval_CallObject' was not declared in this scope; did you mean 'PyObject_CallObject'?
24164 | pinst = PyEval_CallObject(pclass, pargs);
| ^~~~~~~~~~~~~~~~~
| PyObject_CallObject
...
More information about the debian-science-maintainers
mailing list