Building of sage 9.2 stopped with sagelib compilation - taking now system packages of Opensuse

93 views
Skip to first unread message

Tobias Weiss

unread,
Nov 28, 2020, 3:25:24 PM11/28/20
to sage-support
Hello Everybody,

now the second post to the problem. I try to make sage 9.2 on Opensuse Tumbleweed. The compilation stopped with last step of sagelib. If I don't take system packages, the error don't occurs.
(see thread https://groups.google.com/g/sage-support/c/AJRosgRDrsE)

Pari was take from tarball this times. The output of make ends with:
[sagelib-9.2] [296/297] creating build/temp.linux-x86_64-3.8/build/cythonized/sage/tests
[sagelib-9.2] gcc -Wno-unused-result -Wsign-compare -DNDEBUG -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -Werror=return-type -g -DOPENSSL_LOAD_
CONF -fwrapv -fno-semantic-interposition -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -Werror=return-type -g -O2 -Wall -D_FORTIFY_SOURCE=2 -fsta
ck-protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -Werror=return-type -g -fPIC -I/home/tobias/bin/sage-9.2/build/pkgs/sagelib/src -I/home/tobias/bin/sage-9.2/build/pkgs/sagelib/src/sag
e/ext -I/usr/include/python3.8 -I/home/tobias/bin/sage-9.2/local/lib64/python3.8/site-packages/numpy/core/include -Ibuild/cythonized -I/home/tobias/bin/sage-9.2/local/include -I/usr/include/python3.8 -c build/cythonized/sage
/tests/cython.c -o build/temp.linux-x86_64-3.8/build/cythonized/sage/tests/cython.o -fno-strict-aliasing -DCYTHON_CLINE_IN_TRACEBACK=1 -std=c99
[sagelib-9.2] gcc -pthread -shared -Wl,-rpath-link,/home/tobias/bin/sage-9.2/local/lib -L/home/tobias/bin/sage-9.2/local/lib -Wl,-rpath,/home/tobias/bin/sage-9.2/local/lib build/temp.linux-x86_64-3.8/build/cythonized/sage/te
sts/cython.o -L/usr/lib64 -o build/lib.linux-x86_64-3.8/sage/tests/cython.cpython-38-x86_64-linux-gnu.so
[sagelib-9.2] [297/297] gcc -Wno-unused-result -Wsign-compare -DNDEBUG -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -Werror=return-type -g -DOPE
NSSL_LOAD_CONF -fwrapv -fno-semantic-interposition -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -Werror=return-type -g -O2 -Wall -D_FORTIFY_SOUR
CE=2 -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -Werror=return-type -g -fPIC -I/home/tobias/bin/sage-9.2/local/lib64/python3.8/site-packages/cysignals -I./sage/cpython -Isa
ge/cpython -I/home/tobias/bin/sage-9.2/build/pkgs/sagelib/src -I/home/tobias/bin/sage-9.2/build/pkgs/sagelib/src/sage/ext -I/usr/include/python3.8 -I/home/tobias/bin/sage-9.2/local/lib64/python3.8/site-packages/numpy/core/in
clude -Ibuild/cythonized -I/home/tobias/bin/sage-9.2/local/include -I/usr/include/python3.8 -c build/cythonized/sage/tests/stl_vector.cpp -o build/temp.linux-x86_64-3.8/build/cythonized/sage/tests/stl_vector.o -fno-strict-al
iasing -DCYTHON_CLINE_IN_TRACEBACK=1 -std=c++11
[sagelib-9.2] build/cythonized/sage/tests/stl_vector.cpp: In function ‘PyObject* __pyx_pf_4sage_5tests_10stl_vector_14stl_int_vector_4__getitem__(__pyx_obj_4sage_5tests_10stl_vector_stl_int_vector*, int)’:
[sagelib-9.2] build/cythonized/sage/tests/stl_vector.cpp:2940:30: warning: comparison of integer expressions of different signedness: ‘int’ and ‘std::vector<int>::size_type’ {aka ‘long unsigned int’} [-Wsign-compare]
[sagelib-9.2]  2940 |       __pyx_t_1 = (__pyx_v_i < __pyx_v_self->data->size());
[sagelib-9.2]       |                    ~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~
[sagelib-9.2] build/cythonized/sage/tests/stl_vector.cpp: At global scope:
[sagelib-9.2] build/cythonized/sage/tests/stl_vector.cpp:5744:18: warning: ‘PyObject* __pyx_pw_4sage_7cpython_6string_3str_to_bytes(PyObject*, PyObject*, PyObject*)’ defined but not used [-Wunused-function]
[sagelib-9.2]  5744 | static PyObject *__pyx_pw_4sage_7cpython_6string_3str_to_bytes(PyObject *__pyx_self, PyObject *__pyx_args, PyObject *__pyx_kwds) {
[sagelib-9.2]       |                  ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[sagelib-9.2] build/cythonized/sage/tests/stl_vector.cpp:5743:13: warning: ‘__pyx_doc_4sage_7cpython_6string_2str_to_bytes’ defined but not used [-Wunused-variable]
[sagelib-9.2]  5743 | static char __pyx_doc_4sage_7cpython_6string_2str_to_bytes[] = "str_to_bytes(s, encoding=None, errors=None) -> bytes\nFile: sage/cpython/string.pxd (starting at line 55)\n\n    Convert ``str`` or ``unic
ode`` to ``bytes``.\n\n    It encodes the given ``str`` to a Python 3 ``bytes``\n    using the specified encoding.  It is a no-op on ``bytes`` input.\n\n    EXAMPLES::\n\n        sage: from sage.cpython.string import str_to_
bytes\n        sage: bs = [str_to_bytes(u'\317\200')]\n        sage: all(b == b'\\xcf\\x80' for b in bs)\n        True\n        sage: str_to_bytes([])\n        Traceback (most recent call last):\n        ...\n        TypeErr
or: expected str... list found\n    ";
[sagelib-9.2]       |             ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[sagelib-9.2] build/cythonized/sage/tests/stl_vector.cpp:5539:18: warning: ‘PyObject* __pyx_pw_4sage_7cpython_6string_1bytes_to_str(PyObject*, PyObject*, PyObject*)’ defined but not used [-Wunused-function]
[sagelib-9.2]  5539 | static PyObject *__pyx_pw_4sage_7cpython_6string_1bytes_to_str(PyObject *__pyx_self, PyObject *__pyx_args, PyObject *__pyx_kwds) {
[sagelib-9.2]       |                  ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[sagelib-9.2] build/cythonized/sage/tests/stl_vector.cpp:5538:13: warning: ‘__pyx_doc_4sage_7cpython_6string_bytes_to_str’ defined but not used [-Wunused-variable]
[sagelib-9.2]  5538 | static char __pyx_doc_4sage_7cpython_6string_bytes_to_str[] = "bytes_to_str(b, encoding=None, errors=None) -> str\nFile: sage/cpython/string.pxd (starting at line 29)\n\n    Convert ``bytes`` to ``str``
.\n\n    This decodes the given ``bytes`` to a Python 3 unicode ``str`` using\n    the specified encoding.  It is a no-op on ``str`` input.\n\n    EXAMPLES::\n\n        sage: from sage.cpython.string import bytes_to_str\n   
    sage: s = bytes_to_str(b'\\xcf\\x80')\n        sage: s == u'\317\200'\n        True\n        sage: bytes_to_str([])\n        Traceback (most recent call last):\n        ...\n        TypeError: expected bytes, list found
\n    ";
[sagelib-9.2]       |             ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[sagelib-9.2] build/cythonized/sage/tests/stl_vector.cpp:5259:18: warning: ‘PyObject* __pyx_pw_4sage_9structure_7richcmp_9revop(PyObject*, PyObject*)’ defined but not used [-Wunused-function]
[sagelib-9.2]  5259 | static PyObject *__pyx_pw_4sage_9structure_7richcmp_9revop(PyObject *__pyx_self, PyObject *__pyx_arg_op) {
[sagelib-9.2]       |                  ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[sagelib-9.2] build/cythonized/sage/tests/stl_vector.cpp:5258:13: warning: ‘__pyx_doc_4sage_9structure_7richcmp_8revop’ defined but not used [-Wunused-variable]
[sagelib-9.2]  5258 | static char __pyx_doc_4sage_9structure_7richcmp_8revop[] = "revop(int op) -> int\nFile: sage/structure/richcmp.pxd (starting at line 199)\n\n    Return the reverse operation of ``op``.\n\n    For exampl
e, <= becomes >=, etc.\n\n    EXAMPLES::\n\n        sage: from sage.structure.richcmp import revop\n        sage: [revop(i) for i in range(6)]\n        [4, 5, 2, 3, 0, 1]\n    ";
[sagelib-9.2]       |             ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[sagelib-9.2] build/cythonized/sage/tests/stl_vector.cpp:5132:18: warning: ‘PyObject* __pyx_pw_4sage_9structure_7richcmp_7rich_to_bool_sgn(PyObject*, PyObject*, PyObject*)’ defined but not used [-Wunused-function]
[sagelib-9.2]  5132 | static PyObject *__pyx_pw_4sage_9structure_7richcmp_7rich_to_bool_sgn(PyObject *__pyx_self, PyObject *__pyx_args, PyObject *__pyx_kwds) {
[sagelib-9.2]       |                  ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[sagelib-9.2] build/cythonized/sage/tests/stl_vector.cpp:5131:13: warning: ‘__pyx_doc_4sage_9structure_7richcmp_6rich_to_bool_sgn’ defined but not used [-Wunused-variable]
[sagelib-9.2]  5131 | static char __pyx_doc_4sage_9structure_7richcmp_6rich_to_bool_sgn[] = "rich_to_bool_sgn(int op, Py_ssize_t c) -> bool\nFile: sage/structure/richcmp.pxd (starting at line 187)\n\n    Same as ``rich_to_bo
ol``, but allow any `c < 0` and `c > 0`\n    instead of only `-1` and `1`.\n\n    .. NOTE::\n\n        This is in particular needed for ``mpz_cmp()``.\n    ";
[sagelib-9.2]       |             ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[sagelib-9.2] build/cythonized/sage/tests/stl_vector.cpp:5003:18: warning: ‘PyObject* __pyx_pw_4sage_9structure_7richcmp_5rich_to_bool(PyObject*, PyObject*, PyObject*)’ defined but not used [-Wunused-function]
[sagelib-9.2]  5003 | static PyObject *__pyx_pw_4sage_9structure_7richcmp_5rich_to_bool(PyObject *__pyx_self, PyObject *__pyx_args, PyObject *__pyx_kwds) {
[sagelib-9.2]       |                  ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[sagelib-9.2] build/cythonized/sage/tests/stl_vector.cpp:5002:13: warning: ‘__pyx_doc_4sage_9structure_7richcmp_4rich_to_bool’ defined but not used [-Wunused-variable]
[sagelib-9.2]  5002 | static char __pyx_doc_4sage_9structure_7richcmp_4rich_to_bool[] = "rich_to_bool(int op, int c) -> bool\nFile: sage/structure/richcmp.pxd (starting at line 120)\n\n    Return the corresponding ``True`` o
r ``False`` value for a rich\n    comparison, given the result of an old-style comparison.\n\n    INPUT:\n\n    - ``op`` -- a rich comparison operation (e.g. ``Py_EQ``)\n\n    - ``c`` -- the result of an old-style comparison
: -1, 0 or 1.\n\n    OUTPUT: 1 or 0 (corresponding to ``True`` and ``False``)\n\n    .. SEEALSO::\n\n        :func:`rich_to_bool_sgn` if ``c`` could be outside the\n        [-1, 0, 1] range.\n\n    EXAMPLES::\n\n        sage
: from sage.structure.richcmp import (rich_to_bool,\n        ....:    op_EQ, op_NE, op_LT, op_LE, op_GT, op_GE)\n        sage: for op in (op_LT, op_LE, op_EQ, op_NE, op_GT, op_GE):\n        ....:     for c in (-1,0,1):\n    
   ....:         print(rich_to_bool(op, c))\n        True False False\n        True True False\n        False True False\n        True False True\n        False False True\n        False True True\n\n    Indirect tests usin
g integers::\n\n        sage: 0 < 5, 5 < 5, 5 < -8\n        (True, False, False)\n        sage: 0 <= 5, 5 <= 5, 5 <= -8\n        (True, True, False)\n        sage: 0 >= 5, 5 >= 5, 5 >= -8\n        (False, True, True)\n      
 sage: 0 > 5, 5 > 5, 5 > -8\n        (False, False, True)\n        sage: 0 == 5, 5 == 5, 5 == -8\n        (False, True, False)\n        sage: 0 != 5, 5 != 5, 5 != -8\n        (True, False, True)\n    ";
[sagelib-9.2]       |             ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[sagelib-9.2] build/cythonized/sage/tests/stl_vector.cpp:4813:18: warning: ‘PyObject* __pyx_pw_4sage_9structure_7richcmp_3richcmp_not_equal(PyObject*, PyObject*, PyObject*)’ defined but not used [-Wunused-function]
[sagelib-9.2]  4813 | static PyObject *__pyx_pw_4sage_9structure_7richcmp_3richcmp_not_equal(PyObject *__pyx_self, PyObject *__pyx_args, PyObject *__pyx_kwds) {
[sagelib-9.2]       |                  ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[sagelib-9.2] build/cythonized/sage/tests/stl_vector.cpp:4812:13: warning: ‘__pyx_doc_4sage_9structure_7richcmp_2richcmp_not_equal’ defined but not used [-Wunused-variable]
[sagelib-9.2]  4812 | static char __pyx_doc_4sage_9structure_7richcmp_2richcmp_not_equal[] = "richcmp_not_equal(x, y, int op)\nFile: sage/structure/richcmp.pxd (starting at line 56)\n\n    Like ``richcmp(x, y, op)`` but assu
ming that `x` is not equal to `y`.\n\n    INPUT:\n\n    - ``op`` -- a rich comparison operation (e.g. ``Py_EQ``)\n\n    OUTPUT:\n\n    If ``op`` is not ``op_EQ`` or ``op_NE``, the result of\n    ``richcmp(x, y, op)``. If ``o
p`` is ``op_EQ``, return\n    ``False``. If ``op`` is ``op_NE``, return ``True``.\n\n    This is useful to compare lazily two objects A and B according to 2\n    (or more) different parameters, say width and height for examp
le.\n    One could use::\n\n        return richcmp((A.width(), A.height()), (B.width(), B.height()), op)\n\n    but this will compute both width and height in all cases, even if\n    A.width() and B.width() are enough to dec
ide the comparison.\n\n    Instead one can do::\n\n        wA = A.width()\n        wB = B.width()\n        if wA != wB:\n            return richcmp_not_equal(wA, wB, op)\n        return richcmp(A.height(), B.height(), op)\n\
n    The difference with ``richcmp`` is that ``richcmp_not_equal``\n    assumes that its arguments are not equal, which is excluding the case\n    where the comparison cannot be decided so far, without\n    knowing the rest
of the parameters.\n\n    EXAMPLES::\n\n        sage: from sage.structure.richcmp import (richcmp_not_equal,\n        ....:    op_EQ, op_NE, op_LT, op_LE, op_GT, op_GE)\n        sage: for op in (op_LT, op_LE, op_EQ, op_NE, o
p_GT, op_GE):\n        ....:     print(richcmp_not_equal(3, 4, op))\n        True\n        True\n        False\n        True\n        False\n        False\n        sage: for op in (op_LT, op_LE, op_EQ, op_NE, op_GT, op_GE):\
n        ....:     print(richcmp_not_equal(5, 4, op))\n        False\n        False\n        False\n        True\n        True\n        True\n    ";
[sagelib-9.2]       |             ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[sagelib-9.2] build/cythonized/sage/tests/stl_vector.cpp:4597:18: warning: ‘PyObject* __pyx_pw_4sage_9structure_7richcmp_1richcmp(PyObject*, PyObject*, PyObject*)’ defined but not used [-Wunused-function]
[sagelib-9.2]  4597 | static PyObject *__pyx_pw_4sage_9structure_7richcmp_1richcmp(PyObject *__pyx_self, PyObject *__pyx_args, PyObject *__pyx_kwds) {
[sagelib-9.2]       |                  ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[sagelib-9.2] build/cythonized/sage/tests/stl_vector.cpp:4596:13: warning: ‘__pyx_doc_4sage_9structure_7richcmp_richcmp’ defined but not used [-Wunused-variable]
[sagelib-9.2]  4596 | static char __pyx_doc_4sage_9structure_7richcmp_richcmp[] = "richcmp(x, y, int op)\nFile: sage/structure/richcmp.pxd (starting at line 6)\n\n    Return the result of the rich comparison of ``x`` and ``y
`` with\n    operator ``op``.\n\n    INPUT:\n\n    - ``x``, ``y`` -- arbitrary Python objects\n\n    - ``op`` -- comparison operator (one of ``op_LT`, ``op_LE``,\n      ``op_EQ``, ``op_NE``, ``op_GT``, ``op_GE``).\n\n    EXA
MPLES::\n\n        sage: from sage.structure.richcmp import *\n        sage: richcmp(3, 4, op_LT)\n        True\n        sage: richcmp(x, x^2, op_EQ)\n        x == x^2\n\n    The two examples above are completely equivalent
to ``3 < 4``\n    and ``x == x^2``. For this reason, it only makes sense in practice\n    to call ``richcmp`` with a non-constant value for ``op``.\n\n    We can write a custom ``Element`` class which shows a more\n    reali
stic example of how to use this::\n\n        sage: from sage.structure.element import Element\n        sage: class MyElement(Element):\n        ....:     def __init__(self, parent, value):\n        ....:         Element.__in
it__(self, parent)\n        ....:         self.v = value\n        ....:     def _richcmp_(self, other, op):\n        ....:         return richcmp(self.v, other.v, op)\n        sage: P = Parent()\n        sage: x = MyElement(
P, 3)\n        sage: y = MyElement(P, 3)\n        sage: x < y\n        False\n        sage: x == y\n        True\n        sage: x > y\n        False\n    ";
[sagelib-9.2]       |             ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[sagelib-9.2] build/cythonized/sage/tests/stl_vector.cpp:4383:18: warning: ‘PyObject* __pyx_pw_4sage_9structure_7element_3have_same_parent(PyObject*, PyObject*, PyObject*)’ defined but not used [-Wunused-function]
[sagelib-9.2]  4383 | static PyObject *__pyx_pw_4sage_9structure_7element_3have_same_parent(PyObject *__pyx_self, PyObject *__pyx_args, PyObject *__pyx_kwds) {
[sagelib-9.2]       |                  ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[sagelib-9.2] build/cythonized/sage/tests/stl_vector.cpp:4382:13: warning: ‘__pyx_doc_4sage_9structure_7element_2have_same_parent’ defined but not used [-Wunused-variable]
[sagelib-9.2]  4382 | static char __pyx_doc_4sage_9structure_7element_2have_same_parent[] = "have_same_parent(left, right) -> bool\nFile: sage/structure/element.pxd (starting at line 111)\n\n    Return ``True`` if and only i
f ``left`` and ``right`` have the\n    same parent.\n\n    .. WARNING::\n\n        This function assumes that at least one of the arguments is a\n        Sage :class:`Element`. When in doubt, use the slower\n        ``parent
(left) is parent(right)`` instead.\n\n    EXAMPLES::\n\n        sage: from sage.structure.element import have_same_parent\n        sage: have_same_parent(1, 3)\n        True\n        sage: have_same_parent(1, 1/2)\n        F
alse\n        sage: have_same_parent(gap(1), gap(1/2))\n        True\n\n    These have different types but the same parent::\n\n        sage: a = RLF(2)\n        sage: b = exp(a)\n        sage: type(a)\n        <... 'sage.ri
ngs.real_lazy.LazyWrapper'>\n        sage: type(b)\n        <... 'sage.rings.real_lazy.LazyNamedUnop'>\n        sage: have_same_parent(a, b)\n        True\n    ";
[sagelib-9.2]       |             ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[sagelib-9.2] build/cythonized/sage/tests/stl_vector.cpp:4038:18: warning: ‘PyObject* __pyx_pw_4sage_9structure_7element_1parent(PyObject*, PyObject*)’ defined but not used [-Wunused-function]
[sagelib-9.2]  4038 | static PyObject *__pyx_pw_4sage_9structure_7element_1parent(PyObject *__pyx_self, PyObject *__pyx_v_x) {
[sagelib-9.2]       |                  ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[sagelib-9.2] build/cythonized/sage/tests/stl_vector.cpp:4037:13: warning: ‘__pyx_doc_4sage_9structure_7element_parent’ defined but not used [-Wunused-variable]
[sagelib-9.2]  4037 | static char __pyx_doc_4sage_9structure_7element_parent[] = "parent(x)\nFile: sage/structure/element.pxd (starting at line 6)\n\n    Return the parent of the element ``x``.\n\n    Usually, this means the
mathematical object of which ``x`` is an\n    element.\n\n    INPUT:\n\n    - ``x`` -- an element\n\n    OUTPUT:\n\n    - If ``x`` is a Sage :class:`Element`, return ``x.parent()``.\n\n    - Otherwise, return ``type(x)``.\n
\n    .. SEEALSO::\n\n        `Parents, Conversion and Coercion <http://doc.sagemath.org/html/en/tutorial/tour_coercion.html>`_\n        Section in the Sage Tutorial\n\n    EXAMPLES::\n\n        sage: a = 42\n        sage: p
arent(a)\n        Integer Ring\n        sage: b = 42/1\n        sage: parent(b)\n        Rational Field\n        sage: c = 42.0\n        sage: parent(c)\n        Real Field with 53 bits of precision\n\n    Some more complica
ted examples::\n\n        sage: x = Partition([3,2,1,1,1])\n        sage: parent(x)\n        Partitions\n        sage: v = vector(RDF, [1,2,3])\n        sage: parent(v)\n        Vector space of dimension 3 over Real Double F
ield\n\n    The following are not considered to be elements, so the type is\n    returned::\n\n        sage: d = int(42)  # Python int\n        sage: parent(d)\n        <... 'int'>\n        sage: L = list(range(10))\n       
sage: parent(L)\n        <... 'list'>\n    ";
[sagelib-9.2]       |             ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[sagelib-9.2] g++ -pthread -shared -Wl,-rpath-link,/home/tobias/bin/sage-9.2/local/lib -L/home/tobias/bin/sage-9.2/local/lib -Wl,-rpath,/home/tobias/bin/sage-9.2/local/lib build/temp.linux-x86_64-3.8/build/cythonized/sage/te
sts/stl_vector.o -L/usr/lib64 -lgmp -o build/lib.linux-x86_64-3.8/sage/tests/stl_vector.cpython-38-x86_64-linux-gnu.so -lpari
[sagelib-9.2] error: command 'gcc' failed with exit status 1
[sagelib-9.2]  
[sagelib-9.2] real      45m29,250s
[sagelib-9.2] user      43m28,680s
[sagelib-9.2] sys       1m14,383s
make[4]: *** [Makefile:2163: sagelib-no-deps] Fehler 1
make[3]: *** [Makefile:2163: /home/tobias/bin/sage-9.2/local/var/lib/sage/installed/sagelib-9.2] Fehler 2
make[2]: *** [Makefile:1766: all-start] Fehler 2
make[2]: Verzeichnis „/home/tobias/bin/sage-9.2/build/make“ wird verlassen

real    45m37,045s
user    43m33,440s
sys     1m16,757s
***************************************************************
Error building Sage.

The following package(s) may have failed to build (not necessarily
during this run of 'make all-start'):

It is safe to delete any log files and build directories, but they
contain information that is helpful for debugging build problems.
WARNING: If you now run 'make' again, the build directory of the
same version of the package will, by default, be deleted. Set the
environment variable SAGE_KEEP_BUILT_SPKGS=yes to prevent this.

make[1]: *** [Makefile:33: all-start] Fehler 1
make[1]: Verzeichnis „/home/tobias/bin/sage-9.2“ wird verlassen
make: *** [Makefile:13: all] Fehler 2

Tobias Weiss

unread,
Nov 28, 2020, 5:32:26 PM11/28/20
to sage-support
Because the last g++ command is something with stl vector: Do I need the glibc-static-devel? I only have glibc-devel installed.

Tobias

Dima Pasechnik

unread,
Nov 28, 2020, 6:23:52 PM11/28/20
to sage-support
please post the top-level config.log



--
You received this message because you are subscribed to the Google Groups "sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sage-support...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sage-support/6c0f6d68-2d85-4b70-87e2-d141feabb10dn%40googlegroups.com.

Matthias Koeppe

unread,
Nov 28, 2020, 6:29:26 PM11/28/20
to sage-support
Those who want to help with this problem may find https://trac.sagemath.org/ticket/30619 useful -- builds on this system can be reproduced using "tox -e docker-opensuse-tumbleweed-standard"

Matthias Koeppe

unread,
Nov 28, 2020, 6:47:27 PM11/28/20
to sage-support
The actual error is likely further up. This problem could just be the missing dependency of sagelib on giac, already fixed in https://trac.sagemath.org/ticket/30858
Try compiling the latest development version,
or do "make giac && make" to work around the problem

Tobias Weiss

unread,
Nov 28, 2020, 7:29:11 PM11/28/20
to sage-support
Here the top-level config.log. Giac was compiled without problems bevor sagelib. I give you the install logs of both. Installing the static-devel of glibc didn't help.
sagelib-9.2.log
giac-1.5.0.87p2.p1.log
config.log

Tobias Weiss

unread,
Nov 28, 2020, 7:31:13 PM11/28/20
to sage-support
In what directory I should do "make giac && make" ?

Tobias Weiss

unread,
Nov 28, 2020, 7:41:51 PM11/28/20
to sage-support
I understand: I start a new compilation with "make giac && make". It starts with readline and does pari now very early.

Tobias Weiss

unread,
Nov 28, 2020, 7:52:51 PM11/28/20
to sage-support
Compiling with "make giac && make" stopped with giac. I give you the log.

[giac-1.5.0.87p2.p1] checking for lapack... no
[giac-1.5.0.87p2.p1] configure: error: Package requirements (lapack) were not met:
[giac-1.5.0.87p2.p1]  
[giac-1.5.0.87p2.p1] Package 'lapack', required by 'virtual:world', not found
[giac-1.5.0.87p2.p1]  
[giac-1.5.0.87p2.p1] Consider adjusting the PKG_CONFIG_PATH environment variable if you
[giac-1.5.0.87p2.p1] installed software in a non-standard prefix.
[giac-1.5.0.87p2.p1]  
[giac-1.5.0.87p2.p1] Alternatively, you may set the environment variables LAPACK_CFLAGS
[giac-1.5.0.87p2.p1] and LAPACK_LIBS to avoid the need to call pkg-config.
[giac-1.5.0.87p2.p1] See the pkg-config man page for more details.
[giac-1.5.0.87p2.p1] ***********************************************************************************************************************************************************************************************************
*********************
[giac-1.5.0.87p2.p1] Error configuring giac-1.5.0.87p2.p1
[giac-1.5.0.87p2.p1] See the file
[giac-1.5.0.87p2.p1]     /home/tobias/bin/sage-9.2-v3/local/var/tmp/sage/build/giac-1.5.0.87p2.p1/src/config.log
[giac-1.5.0.87p2.p1] for details.
[giac-1.5.0.87p2.p1] ***********************************************************************************************************************************************************************************************************
*********************
[giac-1.5.0.87p2.p1]  
[giac-1.5.0.87p2.p1] real       0m14.529s
[giac-1.5.0.87p2.p1] user       0m10.550s
[giac-1.5.0.87p2.p1] sys        0m4.271s
[giac-1.5.0.87p2.p1] ************************************************************************
[giac-1.5.0.87p2.p1] Error installing package giac-1.5.0.87p2.p1
[giac-1.5.0.87p2.p1] ************************************************************************
[giac-1.5.0.87p2.p1] Please email sage-devel (http://groups.google.com/group/sage-devel)
[giac-1.5.0.87p2.p1] explaining the problem and including the log file
[giac-1.5.0.87p2.p1]   /home/tobias/bin/sage-9.2-v3/logs/pkgs/giac-1.5.0.87p2.p1.log
[giac-1.5.0.87p2.p1] Describe your computer, operating system, etc.
[giac-1.5.0.87p2.p1] If you want to try to fix the problem yourself, *don't* just cd to
[giac-1.5.0.87p2.p1] /home/tobias/bin/sage-9.2-v3/local/var/tmp/sage/build/giac-1.5.0.87p2.p1 and type 'make' or whatever is appropriate.
[giac-1.5.0.87p2.p1] Instead, the following commands setup all environment variables
[giac-1.5.0.87p2.p1] correctly and load a subshell for you to debug the error:
[giac-1.5.0.87p2.p1]   (cd '/home/tobias/bin/sage-9.2-v3/local/var/tmp/sage/build/giac-1.5.0.87p2.p1' && '/home/tobias/bin/sage-9.2-v3/sage' --buildsh)
[giac-1.5.0.87p2.p1] When you are done debugging, you can type "exit" to leave the subshell.
[giac-1.5.0.87p2.p1] ************************************************************************
make[2]: *** [Makefile:2034: giac-no-deps] Fehler 1
make[1]: *** [Makefile:2034: /home/tobias/bin/sage-9.2-v3/local/var/lib/sage/installed/giac-1.5.0.87p2.p1] Fehler 2
make[1]: Verzeichnis „/home/tobias/bin/sage-9.2-v3/build/make“ wird verlassen


giac-1.5.0.87p2.p1.log

Tobias Weiss

unread,
Nov 28, 2020, 8:03:43 PM11/28/20
to sage-support
On system I had installed giac for all the builds I have done:

giac 1.5.0.85-1.1
giac-devel 1.5.0.85-1.1
libgiac0 1.5.0.85-1.1

But ./configure didn't notice. Should I retry with uninstall giac?

Tobias

Tobias Weiss

unread,
Nov 28, 2020, 8:12:23 PM11/28/20
to sage-support
... when I configured like this, sagelib was compliled without errors. See thread "Building of sage 9.2 stopped because pynac doesn't see libflint" I did before.

./configure --with-system-arb=no --with-system-boost=no --with-system-brial=no --with-system-cddlib=no --with-system-cliquer=no --with-system-ecm=no --with-system-eclib=no --with-system-fflas_ffpack=no --
with-system-flint=no --with-system-flintqs=no --with-system-fplll=no --with-system-freetype=no --with-system-gc=no --with-system-giac=no --with-system-givaro=no --with-system-glpk=no --with-system-gmp=no --with-system-gsl=no
--with-system-iconv=no --with-system-iml=no --with-system-isl=no --with-system-lcalc=no --with-system-libbraiding=no --with-system-libatomic_ops=no --with-system-libffi=no --with-system-libgd=no --with-system-libsemigroups=
no --with-system-lrcalc=no --with-system-m4rie=no --with-system-m4ri=no --with-system-mpc=no --with-system-mpfi=no --with-system-mpfr=no --with-system-mpir=no --with-system-ninja_build=no --with-system-ntl=no --with-system-o
penblas=no --with-system-pandoc=no --with-system-pari=no --with-system-pari_galdata=no --with-system-pari_seadata_small=no --with-system-pcre=no --with-system-perl_term_readline_gnu=no --with-system-planarity=no --with-syste
m-ppl=no --with-system-rw=no --with-system-readline=no --with-system-suitesparse=no --with-system-symmetrica=no --with-system-yasm=no --with-system-zeromq=no --with-system-zn_poly=no --with-system-pynac=no


Tobias

Dima Pasechnik

unread,
Nov 28, 2020, 8:15:18 PM11/28/20
to sage-support


On Sat, 28 Nov 2020, 19:41 Tobias Weiss, <tobwe...@web.de> wrote:
I understand: I start a new compilation with "make giac && make". It starts with readline and does pari now very early.

no, not a new one.
Normally one can (and should) proceed at the point it stopped.

--
You received this message because you are subscribed to the Google Groups "sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sage-support...@googlegroups.com.

Tobias Weiss

unread,
Nov 28, 2020, 8:31:27 PM11/28/20
to sage-support
OK, I have three directories:

~/bin/sage-9.2/: Here I started with ./configure, make and did now proceed with "make giac && make"
~/bin/sage-9.2-v2/: Here started the same, but with glibc-static-devel installed which made no difference
~/bin/sage-9.3-v3/: Here I started with ./configure, "make giac && make"

when I proceeded in ~/bin/sage-9.2/ with "make giac && make" sagelib gave different error - see also log file

[sagelib-9.2] In file included from /home/tobias/bin/sage-9.2/local/include/Lfunction/L.h:537,
[sagelib-9.2]                  from build/cythonized/sage/libs/lcalc/lcalc_sage.h:1,
[sagelib-9.2]                  from build/cythonized/sage/libs/lcalc/lcalc_Lfunction.cpp:675:
[sagelib-9.2] /home/tobias/bin/sage-9.2/local/include/Lfunction/Lvalue.h: In member function ‘Complex L_function<ttype>::value_via_Riemann_sum(Complex, const char*) [with ttype = std::complex<double>]’:
[sagelib-9.2] /home/tobias/bin/sage-9.2/local/include/Lfunction/Lvalue.h:271:29: warning: ‘local_average’ may be used uninitialized in this function [-Wmaybe-uninitialized]
[sagelib-9.2]   271 |         }while(local_average>max_integrand*tolerance_sqrd);
[sagelib-9.2]       |                ~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[sagelib-9.2] /home/tobias/bin/sage-9.2/local/include/Lfunction/Lvalue.h: In member function ‘Complex L_function<ttype>::value_via_Riemann_sum(Complex, const char*) [with ttype = int]’:
[sagelib-9.2] /home/tobias/bin/sage-9.2/local/include/Lfunction/Lvalue.h:271:29: warning: ‘local_average’ may be used uninitialized in this function [-Wmaybe-uninitialized]
[sagelib-9.2]   271 |         }while(local_average>max_integrand*tolerance_sqrd);
[sagelib-9.2]       |                ~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[sagelib-9.2] /home/tobias/bin/sage-9.2/local/include/Lfunction/Lvalue.h: In member function ‘Complex L_function<ttype>::value_via_Riemann_sum(Complex, const char*) [with ttype = double]’:
[sagelib-9.2] /home/tobias/bin/sage-9.2/local/include/Lfunction/Lvalue.h:271:29: warning: ‘local_average’ may be used uninitialized in this function [-Wmaybe-uninitialized]
[sagelib-9.2]   271 |         }while(local_average>max_integrand*tolerance_sqrd);
[sagelib-9.2]       |                ~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[sagelib-9.2] In file included from /home/tobias/bin/sage-9.2/local/include/Lfunction/L.h:538,
[sagelib-9.2]                  from build/cythonized/sage/libs/lcalc/lcalc_sage.h:1,
[sagelib-9.2]                  from build/cythonized/sage/libs/lcalc/lcalc_Lfunction.cpp:675:
[sagelib-9.2] /home/tobias/bin/sage-9.2/local/include/Lfunction/Lfind_zeros.h: In member function ‘void L_function<ttype>::find_zeros_via_N_v(Long, bool, Double, int, bool, std::vector<double>&) [with ttype = std::complex<do
uble>]’:
[sagelib-9.2] /home/tobias/bin/sage-9.2/local/include/Lfunction/Lfind_zeros.h:1281:55: warning: ‘u3’ may be used uninitialized in this function [-Wmaybe-uninitialized]
[sagelib-9.2]  1281 |                                 tmp3=-zeros_zoom_brent(y2_c,x3_c,-v2,-u3);
[sagelib-9.2]       |                                       ~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~
[sagelib-9.2] /home/tobias/bin/sage-9.2/local/include/Lfunction/Lfind_zeros.h:1281:55: warning: ‘x3_c’ may be used uninitialized in this function [-Wmaybe-uninitialized]
[sagelib-9.2] /home/tobias/bin/sage-9.2/local/include/Lfunction/Lfind_zeros.h:1307:54: warning: ‘x3’ may be used uninitialized in this function [-Wmaybe-uninitialized]
[sagelib-9.2]  1307 |                                 tmp2=zeros_zoom_brent(x3,y2,u3,v2);
[sagelib-9.2]       |                                      ~~~~~~~~~~~~~~~~^~~~~~~~~~~~~
[sagelib-9.2] /home/tobias/bin/sage-9.2/local/include/Lfunction/Lfind_zeros.h:1248:56: warning: ‘tmp3’ may be used uninitialized in this function [-Wmaybe-uninitialized]
[sagelib-9.2]  1248 |                                         zeros_S[i+1][0]=tmp3;
[sagelib-9.2]       |                                         ~~~~~~~~~~~~~~~^~~~~
[sagelib-9.2] /home/tobias/bin/sage-9.2/local/include/Lfunction/Lfind_zeros.h:1231:58: warning: ‘tmp2’ may be used uninitialized in this function [-Wmaybe-uninitialized]
[sagelib-9.2]  1231 |                                         if(sn(x2)!=sn(y2)&&tmp2>tmp3){tmp4=tmp2;tmp2=tmp3;tmp3=tmp4;}
[sagelib-9.2]       |                                            ~~~~~~~~~~~~~~^~~~~~~~~~~
[sagelib-9.2] /home/tobias/bin/sage-9.2/local/include/Lfunction/Lfind_zeros.h: In member function ‘void L_function<ttype>::find_zeros_via_N_v(Long, bool, Double, int, bool, std::vector<double>&) [with ttype = int]’:
[sagelib-9.2] /home/tobias/bin/sage-9.2/local/include/Lfunction/Lfind_zeros.h:1281:55: warning: ‘u3’ may be used uninitialized in this function [-Wmaybe-uninitialized]
[sagelib-9.2]  1281 |                                 tmp3=-zeros_zoom_brent(y2_c,x3_c,-v2,-u3);
[sagelib-9.2]       |                                       ~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~
[sagelib-9.2] /home/tobias/bin/sage-9.2/local/include/Lfunction/Lfind_zeros.h:1281:55: warning: ‘x3_c’ may be used uninitialized in this function [-Wmaybe-uninitialized]
[sagelib-9.2] /home/tobias/bin/sage-9.2/local/include/Lfunction/Lfind_zeros.h:1307:54: warning: ‘x3’ may be used uninitialized in this function [-Wmaybe-uninitialized]
[sagelib-9.2]  1307 |                                 tmp2=zeros_zoom_brent(x3,y2,u3,v2);
[sagelib-9.2]       |                                      ~~~~~~~~~~~~~~~~^~~~~~~~~~~~~
[sagelib-9.2] /home/tobias/bin/sage-9.2/local/include/Lfunction/Lfind_zeros.h:1248:56: warning: ‘tmp3’ may be used uninitialized in this function [-Wmaybe-uninitialized]
[sagelib-9.2]  1248 |                                         zeros_S[i+1][0]=tmp3;
[sagelib-9.2]       |                                         ~~~~~~~~~~~~~~~^~~~~
[sagelib-9.2] /home/tobias/bin/sage-9.2/local/include/Lfunction/Lfind_zeros.h:1231:58: warning: ‘tmp2’ may be used uninitialized in this function [-Wmaybe-uninitialized]
[sagelib-9.2]  1231 |                                         if(sn(x2)!=sn(y2)&&tmp2>tmp3){tmp4=tmp2;tmp2=tmp3;tmp3=tmp4;}
[sagelib-9.2]       |                                            ~~~~~~~~~~~~~~^~~~~~~~~~~
[sagelib-9.2] /home/tobias/bin/sage-9.2/local/include/Lfunction/Lfind_zeros.h: In member function ‘void L_function<ttype>::find_zeros_via_N_v(Long, bool, Double, int, bool, std::vector<double>&) [with ttype = double]’:
[sagelib-9.2] /home/tobias/bin/sage-9.2/local/include/Lfunction/Lfind_zeros.h:1281:55: warning: ‘u3’ may be used uninitialized in this function [-Wmaybe-uninitialized]
[sagelib-9.2]  1281 |                                 tmp3=-zeros_zoom_brent(y2_c,x3_c,-v2,-u3);
[sagelib-9.2]       |                                       ~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~
[sagelib-9.2] /home/tobias/bin/sage-9.2/local/include/Lfunction/Lfind_zeros.h:1281:55: warning: ‘x3_c’ may be used uninitialized in this function [-Wmaybe-uninitialized]
[sagelib-9.2] /home/tobias/bin/sage-9.2/local/include/Lfunction/Lfind_zeros.h:1307:54: warning: ‘x3’ may be used uninitialized in this function [-Wmaybe-uninitialized]
[sagelib-9.2]  1307 |                                 tmp2=zeros_zoom_brent(x3,y2,u3,v2);
[sagelib-9.2]       |                                      ~~~~~~~~~~~~~~~~^~~~~~~~~~~~~
[sagelib-9.2] /home/tobias/bin/sage-9.2/local/include/Lfunction/Lfind_zeros.h:1248:56: warning: ‘tmp3’ may be used uninitialized in this function [-Wmaybe-uninitialized]
[sagelib-9.2]  1248 |                                         zeros_S[i+1][0]=tmp3;
[sagelib-9.2]       |                                         ~~~~~~~~~~~~~~~^~~~~
[sagelib-9.2] /home/tobias/bin/sage-9.2/local/include/Lfunction/Lfind_zeros.h:1231:58: warning: ‘tmp2’ may be used uninitialized in this function [-Wmaybe-uninitialized]
[sagelib-9.2]  1231 |                                         if(sn(x2)!=sn(y2)&&tmp2>tmp3){tmp4=tmp2;tmp2=tmp3;tmp3=tmp4;}
[sagelib-9.2]       |                                            ~~~~~~~~~~~~~~^~~~~~~~~~~
[sagelib-9.2] cc1plus: some warnings being treated as errors
[sagelib-9.2] error: command 'gcc' failed with exit status 1
[sagelib-9.2] Exception ignored in: <function Pool.__del__ at 0x7f9757af8430>
[sagelib-9.2] Traceback (most recent call last):
[sagelib-9.2]   File "/usr/lib64/python3.8/multiprocessing/pool.py", line 268, in __del__
[sagelib-9.2]     self._change_notifier.put(None)
[sagelib-9.2]   File "/usr/lib64/python3.8/multiprocessing/queues.py", line 368, in put
[sagelib-9.2]     self._writer.send_bytes(obj)
[sagelib-9.2]   File "/usr/lib64/python3.8/multiprocessing/connection.py", line 200, in send_bytes
[sagelib-9.2]     self._send_bytes(m[offset:offset + size])
[sagelib-9.2]   File "/usr/lib64/python3.8/multiprocessing/connection.py", line 411, in _send_bytes
[sagelib-9.2]     self._send(header + buf)
[sagelib-9.2]   File "/usr/lib64/python3.8/multiprocessing/connection.py", line 368, in _send
[sagelib-9.2]     n = write(self._handle, buf)
[sagelib-9.2] OSError: [Errno 9] Bad file descriptor
[sagelib-9.2]  
[sagelib-9.2] real      1m8,431s
[sagelib-9.2] user      0m21,655s
[sagelib-9.2] sys       0m2,284s
make[4]: *** [Makefile:2163: sagelib-no-deps] Fehler 1
make[3]: *** [Makefile:2163: /home/tobias/bin/sage-9.2/local/var/lib/sage/installed/sagelib-9.2] Fehler 2
make[2]: *** [Makefile:1766: all-start] Fehler 2
make[2]: Verzeichnis „/home/tobias/bin/sage-9.2/build/make“ wird verlassen

real    1m9,181s
user    0m22,030s
sys     0m2,368s
***************************************************************
Error building Sage.


Tobias
sagelib-9.2.log

Tobias Weiss

unread,
Nov 28, 2020, 8:38:29 PM11/28/20
to sage-support
And proceeding started like this - it let giac untouched:

~/bin/sage-9.2> make giac && make
make build/make/Makefile --stop
make[1]: Verzeichnis „/home/tobias/bin/sage-9.2“ wird betreten
make[1]: „build/make/Makefile“ ist bereits aktuell.
make[1]: Verzeichnis „/home/tobias/bin/sage-9.2“ wird verlassen
build/bin/sage-logger \
       "cd build/make && ./install 'giac'" logs/install.log
make[1]: Verzeichnis „/home/tobias/bin/sage-9.2/build/make“ wird betreten
make[1]: Verzeichnis „/home/tobias/bin/sage-9.2/build/make“ wird verlassen
Nothing to (re)build / all up-to-date.
make build/make/Makefile --stop
make[1]: Verzeichnis „/home/tobias/bin/sage-9.2“ wird betreten
make[1]: „build/make/Makefile“ ist bereits aktuell.
make[1]: Verzeichnis „/home/tobias/bin/sage-9.2“ wird verlassen
build/bin/sage-logger \
       "cd build/make && ./install 'base-toolchain'" logs/install.log
make[1]: Verzeichnis „/home/tobias/bin/sage-9.2/build/make“ wird betreten
make[1]: Verzeichnis „/home/tobias/bin/sage-9.2/build/make“ wird verlassen
*** ALL ENVIRONMENT VARIABLES BEFORE BUILD: ***


Tobias Weiss

unread,
Nov 28, 2020, 9:00:05 PM11/28/20
to sage-support
In my opinion it is again a conflict between systemwide packages and tarball. As I said ./configure does not recognize system giac, but maybe make does. Tomorrow I will configure like this and will make:

./configure --with-system-giac=no

What do you think? Is it senseful?


Tobias

Tobias Weiss

unread,
Nov 28, 2020, 9:02:02 PM11/28/20
to sage-support
... or should I uninstall systemwide giac?

Dima Pasechnik

unread,
Nov 28, 2020, 10:52:32 PM11/28/20
to sage-support
If your Sage build is incomplete, some packages have been built, say,
pari, and then you decide to replace pari
with a system package then you need to uninstall it.
In your config.log there is

configure:38410: result: pari-2.11.4.p0:
already installed as an SPKG

e.g. for pari you'd need to run

make pari-clean

The easiest is to clean everything already built by running

make distclean

and then start again, by running ./configure
If it is happy about system's pari, you will see

configure:38410: result: pari-2.11.4.p0:
using system package; SPKG will not be installed

in the output of ./configure (and in config.log)

Tobias Weiss

unread,
Nov 30, 2020, 1:21:55 PM11/30/20
to sage-support
Sagelib compilation worked now, make continued with certifi package. What did I you? At first I uninstalled the whole "giac complex" which contains giac, im, arb, flint, ppl, cddlib pari, sympow - devel, binary libraries and executable packages.

But that was not enough: the problem occures with system python38-devel - so I unsinstalled that package.

Then I configured like this:
./configure --with-system-arb=no --with-system-cddlib=no --with-system-flint=no --with-system-flintqs=no --with-system-giac=no --with-system-iml=no --with-system-pari=no --with-system-pari_galdata=no --wi
th-system-pari_seadata_small=no --with-system-ppl=no --with-system-python3=no --with-python=PYTHON3

Waiting some hours and that worked for sagelib. If I need to install the giac complex I don't know. But I hope this prevents me for the pynac error I posted before - there flint or pari was maybe compiled two times.

I let you know if the whole complilation works.


Tobias

Tobias Weiss

unread,
Nov 30, 2020, 3:36:38 PM11/30/20
to sage-support
The whole sage was build with this configuration!!!!

Should I retry compilation with systemwide "giac complex" installed and just don't use system python? Does anyone care?


Kind regards,
Tobias

Dima Pasechnik

unread,
Nov 30, 2020, 3:47:27 PM11/30/20
to sage-support
we should get opensuse tumbleweed properly supported, with CI.

this entails listing the needed packages in build/pkgs/*/distros/
like we do for Ubuntu, Fedora, etc.

Fedora would be close match, but not 100% it seems.
(currently trying to build in an lxc container)


--
You received this message because you are subscribed to the Google Groups "sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sage-support...@googlegroups.com.

Matthias Koeppe

unread,
Nov 30, 2020, 6:10:03 PM11/30/20
to sage-support
On Monday, November 30, 2020 at 7:47:27 AM UTC-8 Dima Pasechnik wrote:
we should get opensuse tumbleweed properly supported, with CI.

this entails listing the needed packages in build/pkgs/*/distros/
like we do for Ubuntu, Fedora, etc.


Packages for opensuse are already up in https://trac.sagemath.org/ticket/30619

The follow-up ticket https://trac.sagemath.org/ticket/29527 tracks the task of adding it to GH Actions.

 
Reply all
Reply to author
Forward
0 new messages