emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#57104: closed (Python-symengine fails to build)


From: GNU bug Tracking System
Subject: bug#57104: closed (Python-symengine fails to build)
Date: Thu, 11 Aug 2022 07:40:01 +0000

Your message dated Thu, 11 Aug 2022 15:39:12 +0800
with message-id <87h72jrzz3.fsf@envs.net>
and subject line Re: bug#57104: Python-symengine fails to build
has caused the debbugs.gnu.org bug report #57104,
regarding Python-symengine fails to build
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
57104: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=57104
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
--- Begin Message --- Subject: Python-symengine fails to build Date: Mon, 8 Aug 2022 23:11:10 +0200
Hello,

updating flint, I have also tried to compile python-symengine as a dependent
package, and notice that it fails, but actually it already failed before
with the error
   error: ‘LLVMLongDoubleVisitor’ is not a member of ‘SymEngine’; did you mean 
‘LambdaDoubleVisitor’?

So I have updated symengine to its latest version 0.9.0, and python-symengine
to its latest version 0.9.2, and now the latter fails to build with the
different error message reproduced below.

Since it replaces a broken package by a more modern broken package, I still
took the liberty to push, but it would be nice if someone with knowledge of
python and/or symengine could have a look. Disabling the tests makes the
compilation succeed, but it would be nice to find a better solution...

Thanks,

Andreas


Copying source of python wrappers into: 
/tmp/guix-build-python-symengine-0.9.2.drv-0/symengine-0.9.2
-- Configuring done
-- Generating done
-- Build files have been written to: 
/tmp/guix-build-python-symengine-0.9.2.drv-0/symengine-0.9.2
[ 25%] Cythonizing symengine_wrapper.pyx
[ 50%] Building CXX object 
symengine/lib/CMakeFiles/symengine_wrapper.dir/symengine_wrapper.cpp.o
[ 75%] Building CXX object 
symengine/lib/CMakeFiles/symengine_wrapper.dir/pywrapper.cpp.o
[100%] Linking CXX shared library 
symengine_wrapper.cpython-39-x86_64-linux-gnu.so
[100%] Built target symengine_wrapper
lib (unittest.loader._FailedTest) ... ERROR

======================================================================
ERROR: lib (unittest.loader._FailedTest)
----------------------------------------------------------------------
AttributeError: module 'symengine' has no attribute 'lib'

----------------------------------------------------------------------
Ran 1 test in 0.000s

FAILED (errors=1)
Test failed: <unittest.runner.TextTestResult run=1 errors=1 failures=0>
error: Test failed: <unittest.runner.TextTestResult run=1 errors=1 failures=0>
error: in phase 'check': uncaught exception:
%exception #<&invoke-error program: "python" arguments: ("-c" "import 
setuptools, tokenize;__file__='setup.py';f=getattr(tokenize, 'open', 
open)(__file__);code=f.read().replace('\\r\\n', 
'\\n');f.close();exec(compile(code, __file__, 'exec'))" "test") exit-status: 1 
term-signal: #f stop-signal: #f> 
phase `check' failed after 92.2 seconds
command "python" "-c" "import setuptools, 
tokenize;__file__='setup.py';f=getattr(tokenize, 'open', 
open)(__file__);code=f.read().replace('\\r\\n', 
'\\n');f.close();exec(compile(code, __file__, 'exec'))" "test" failed with 
status 1
builder for 
`/gnu/store/a1fvzjq643azmy4mn2gl86p0xz5v4pl2-python-symengine-0.9.2.drv' failed 
with exit code 1
build of /gnu/store/a1fvzjq643azmy4mn2gl86p0xz5v4pl2-python-symengine-0.9.2.drv 
failed





--- End Message ---
--- Begin Message --- Subject: Re: bug#57104: Python-symengine fails to build Date: Thu, 11 Aug 2022 15:39:12 +0800 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/28.1 (gnu/linux)
Andreas Enge <andreas@enge.fr> writes:

> Since it replaces a broken package by a more modern broken package, I still
> took the liberty to push, but it would be nice if someone with knowledge of
> python and/or symengine could have a look. Disabling the tests makes the
> compilation succeed, but it would be nice to find a better solution...
>

Fixed it by using 'nosetests' to run the tests.

Close now, thanks!


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]