[sage-support] Re: simple 'solve' error, possibly related to ecl and maxima installation
On 2014-11-23, kcrisman kcris...@gmail.com wrote: See http://trac.sagemath.org/ticket/17375 for some possible details on why if this thread hasn't said so. Anyway, hopefully we'll have a quick update so that Maxima works correctly whether or not you have a compiler available. I'm working on it, for the record. best Robert Dodier -- 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+unsubscr...@googlegroups.com. To post to this group, send email to sage-support@googlegroups.com. Visit this group at http://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout.
[sage-support] Re: simple 'solve' error, possibly related to ecl and maxima installation
*This example is edited with linux mint 17.I tested this example with linux ubuntu 14.10 and sagemath runs correctly !* -- 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+unsubscr...@googlegroups.com. To post to this group, send email to sage-support@googlegroups.com. Visit this group at http://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout.
[sage-support] Re: simple 'solve' error, possibly related to ecl and maxima installation
On Saturday, November 22, 2014 7:09:21 PM UTC-5, moroplogo wrote: *This example is edited with linux mint 17.I tested this example with linux ubuntu 14.10 and sagemath runs correctly !* See http://trac.sagemath.org/ticket/17375 for some possible details on why if this thread hasn't said so. Anyway, hopefully we'll have a quick update so that Maxima works correctly whether or not you have a compiler available. -- 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+unsubscr...@googlegroups.com. To post to this group, send email to sage-support@googlegroups.com. Visit this group at http://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout.
[sage-support] Re: simple 'solve' error, possibly related to ecl and maxima installation
Op vrijdag 21 november 2014 04:34:44 UTC+1 schreef Nils Bruin: On Thursday, November 20, 2014 7:10:15 PM UTC-8, Bozh wrote: Are these warnings signs that maxima is still compiling itself every time I started? It looks like Peter correctly identified the problem. According to his assessment, Maxima compiles *some code* upon startup, but not all of maxima. Since these problems seem to be unique only on my mac (and the weird non-existence of CLT in Xcode), can I assume that the problem actually lies in my OSX or Xcode? The fact that maxima tries to compile something is not unique to your mac. The fact that the compilations failed was something relatively specific to your mac, but not unique to it. Peter sketched a system where it didn't work either. Hopefully, Peter will patch the maxima shipped with sage so that we avoid the compilation. Then probably the next sage release will not have this compilation issue anymore. In the longer run, hopefully the maxima people find a way around compiling some code at init-time. Then we can remove our patched behaviour we're going to need in the mean time. I opened a ticket for this and am now testing a patch: http://trac.sagemath.org/ticket/17375 Peter -- 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+unsubscr...@googlegroups.com. To post to this group, send email to sage-support@googlegroups.com. Visit this group at http://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout.
[sage-support] Re: simple 'solve' error, possibly related to ecl and maxima installation
I have the same problem
{
┌┐
│ Sage Version 6.4, Release Date: 2014-11-14 │
│ Type notebook() for the browser-based notebook interface.│
│ Type help() for help.│
└┘
sage: simplify(2)
2
sage: simplify(sqrt(2))
In file included from
/opt/sage-6.4-x86_64-Linux/local/lib/ecl/ecl/ecl-cmp.h:22:0,
from /tmp/ecl001BSihI6.c:5:
/opt/sage-6.4-x86_64-Linux/local/lib/ecl/ecl/ecl.h:20:65: fatal error:
sys/types.h: No such file or directory
#include sys/types.h /* size_t, pthread_t, pthread_mutex_t */
^
compilation terminated.
;;; Internal error:
;;; ** Error code 1 when executing
;;; (RUN-PROGRAM gcc (-I. -I/opt/sage-6.4-x86_64-Linux/local/lib/ecl/
-I/scratch/buildbot/sage/redhawk-1/sage_git/build/local/include
-I/scratch/buildbot/sage/redhawk-1/sage_git/build/local/include
-D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2 -fPIC -Dlinux -O2
-c /tmp/ecl001BSihI6.c -o
/tmp/ecl001BSihI6.o))---
RuntimeError Traceback (most recent call last)
ipython-input-2-e6abdd24a17e in module()
1 simplify(sqrt(Integer(2)))
/opt/sage-6.4-x86_64-Linux/local/lib/python2.7/site-packages/sage/calculus/functional.pyc
in simplify(f)
49
50 try:
--- 51 return f.simplify()
52 except AttributeError:
53 return f
/opt/sage-6.4-x86_64-Linux/local/lib/python2.7/site-packages/sage/symbolic/expression.so
in sage.symbolic.expression.Expression.simplify
(build/cythonized/sage/symbolic/expression.cpp:39275)()
/opt/sage-6.4-x86_64-Linux/local/lib/python2.7/site-packages/sage/symbolic/expression.so
in sage.symbolic.expression.Expression._maxima_
(build/cythonized/sage/symbolic/expression.cpp:5388)()
/opt/sage-6.4-x86_64-Linux/local/lib/python2.7/site-packages/sage/structure/sage_object.so
in sage.structure.sage_object.SageObject._interface_
(build/cythonized/sage/structure/sage_object.c:4897)()
/opt/sage-6.4-x86_64-Linux/local/lib/python2.7/site-packages/sage/misc/lazy_import.so
in sage.misc.lazy_import.LazyImport.__getattr__
(build/cythonized/sage/misc/lazy_import.c:3030)()
/opt/sage-6.4-x86_64-Linux/local/lib/python2.7/site-packages/sage/misc/lazy_import.so
in sage.misc.lazy_import.LazyImport._get_object
(build/cythonized/sage/misc/lazy_import.c:2030)()
/opt/sage-6.4-x86_64-Linux/local/lib/python2.7/site-packages/sage/interfaces/maxima_lib.py
in module()
79 ecl_eval((setf *compile-verbose* NIL))
80 ecl_eval((setf *load-verbose* NIL))
--- 81 ecl_eval((require 'maxima))
82 ecl_eval((in-package :maxima))
83 ecl_eval((setq $nolabels t)))
/opt/sage-6.4-x86_64-Linux/local/lib/python2.7/site-packages/sage/libs/ecl.so
in sage.libs.ecl.ecl_eval (build/cythonized/sage/libs/ecl.c:9161)()
/opt/sage-6.4-x86_64-Linux/local/lib/python2.7/site-packages/sage/libs/ecl.so
in sage.libs.ecl.ecl_eval (build/cythonized/sage/libs/ecl.c:9094)()
/opt/sage-6.4-x86_64-Linux/local/lib/python2.7/site-packages/sage/libs/ecl.so
in sage.libs.ecl.ecl_safe_eval (build/cythonized/sage/libs/ecl.c:4494)()
RuntimeError: ECL says: The variable C::GAZONK is unbound.
sage: simplify(sqrt(2))
---
RuntimeError Traceback (most recent call last)
ipython-input-3-e6abdd24a17e in module()
1 simplify(sqrt(Integer(2)))
/opt/sage-6.4-x86_64-Linux/local/lib/python2.7/site-packages/sage/calculus/functional.pyc
in simplify(f)
49
50 try:
--- 51 return f.simplify()
52 except AttributeError:
53 return f
/opt/sage-6.4-x86_64-Linux/local/lib/python2.7/site-packages/sage/symbolic/expression.so
in sage.symbolic.expression.Expression.simplify
(build/cythonized/sage/symbolic/expression.cpp:39275)()
/opt/sage-6.4-x86_64-Linux/local/lib/python2.7/site-packages/sage/symbolic/expression.so
in sage.symbolic.expression.Expression._maxima_
(build/cythonized/sage/symbolic/expression.cpp:5388)()
/opt/sage-6.4-x86_64-Linux/local/lib/python2.7/site-packages/sage/structure/sage_object.so
in sage.structure.sage_object.SageObject._interface_
(build/cythonized/sage/structure/sage_object.c:4897)()
/opt/sage-6.4-x86_64-Linux/local/lib/python2.7/site-packages/sage/misc/lazy_import.so
in sage.misc.lazy_import.LazyImport.__getattr__
(build/cythonized/sage/misc/lazy_import.c:3030)()
/opt/sage-6.4-x86_64-Linux/local/lib/python2.7/site-packages/sage/misc/lazy_import.so
in sage.misc.lazy_import.LazyImport._get_object
(build/cythonized/sage/misc/lazy_import.c:2030)()
/opt/sage-6.4-x86_64-Linux/local/lib/python2.7/site-packages/sage/interfaces/maxima_lib.py
in module()
[sage-support] Re: simple 'solve' error, possibly related to ecl and maxima installation
Op dinsdag 18 november 2014 04:07:56 UTC+1 schreef Nils Bruin: On Monday, November 17, 2014 5:49:14 PM UTC-8, Bozh wrote: ;;; (RUN-PROGRAM gcc (-I. -I/Applications/sage/local/lib/ecl/ -I/Users/buildslave-sage/slave/sage_git/build/local/include -I/Users/buildslave-sage/slave/sage_git/build/local/include -g -O2 -fPIC -fno-common -Ddarwin -O2 -c /private/var/folders/gh/26025ywx7w128zfds279s_9rgn/T/ecl001IqKQ2b.c -o /private/var/folders/gh/26025ywx7w128zfds279s_9rgn/T/ecl001IqKQ2b.o)) Condition of type: UNBOUND-VARIABLE The variable C::GAZONK is unbound. You probably downloaded a binary? By the looks of it, ecl has some paths hard-baked into it: -I/Users/buildslave-sage/slave/sage_git/build/local/include. That path probably doesn't exist on your computer, but it was present on the mac on which the binary was built. Compilation would probably fail anyway, because you probably don't have a gcc that is compatible with the rest of the build (I assume we're not shipping gcc with our binary). The odd thing is that maxima deems it necessary to compile itself. Your binary should have a precompiled maxima available already. Something must have gotten damaged or the binary distribution from which you started is broken/incompatible with your OSX. First thing to try might be to try and install a fresh binary if you haven't done so already. It could be caused by the following lines in the Maxima source code (in src/commac.lisp): (defparameter trailing-zeros-regex-f-0 (compile nil (maxima-nregex::regex-compile ^(.*\\.[0-9]*[1-9])00*$))) (defparameter trailing-zeros-regex-f-1 (compile nil (maxima-nregex::regex-compile ^(.*\\.0)00*$))) (defparameter trailing-zeros-regex-e-0 (compile nil (maxima-nregex::regex-compile ^(.*\\.[0-9]*[1-9])00*([^0-9][+-][0-9]*)$))) (defparameter trailing-zeros-regex-e-1 (compile nil (maxima-nregex::regex-compile ^(.*\\.0)00*([^0-9][+-][0-9]*)$))) These are executed each time Maxima starts. The call to compile apparently invokes the C compiler. On a system I use, the /tmp directory is a tmpfs file system mounted with the noexec flag, and unless I set TMPDIR to something else than /tmp, the above lines cause the following error when starting Maxima: ;;; Loading #P/home/bruinpj/src/sage/local/lib/ecl/cmp.fas ;;; OPTIMIZE levels: Safety=2, Space=0, Speed=3, Debug=0 ;;; ;;; End of Pass 1. ;;; Internal error: ;;; ** LOAD: Could not load file #P/tmp/ecl001kpMN0E.fas (Error: /tmp/ecl001kpMN0E.fas: failed to map segment from shared object: Operation not permitted) Condition of type: UNBOUND-VARIABLE The variable C::GAZONK is unbound. Peter -- 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+unsubscr...@googlegroups.com. To post to this group, send email to sage-support@googlegroups.com. Visit this group at http://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout.
[sage-support] Re: simple 'solve' error, possibly related to ecl and maxima installation
On Thursday, November 20, 2014 4:36:52 AM UTC-8, Peter Bruin wrote: It could be caused by the following lines in the Maxima source code (in src/commac.lisp): (defparameter trailing-zeros-regex-f-0 (compile nil (maxima-nregex::regex-compile ^(.*\\.[0-9]*[1-9])00*$))) (defparameter trailing-zeros-regex-f-1 (compile nil (maxima-nregex::regex-compile ^(.*\\.0)00*$))) (defparameter trailing-zeros-regex-e-0 (compile nil (maxima-nregex::regex-compile ^(.*\\.[0-9]*[1-9])00*([^0-9][+-][0-9]*)$))) (defparameter trailing-zeros-regex-e-1 (compile nil (maxima-nregex::regex-compile ^(.*\\.0)00*([^0-9][+-][0-9]*)$))) These are executed each time Maxima starts. The call to compile apparently invokes the C compiler. Indeed, a feature of ECL is that compile defers to the C compiler. It is of course crazy this gets compiled every initialization of maxima. I don't think this happened before either. These definitions seem to have been introduced between 5.33.0 and 5.34.1. They can easily be rewritten in such a way that an init-time compile can be avoided, either by stripping out the compile statement entirely (I don't think this is critical code) or by forcing the compile statement to run at compile time. The short-term solution is probably to patch maxima to not compile these things at all. Longer term: https://sourceforge.net/p/maxima/bugs/2845/ -- 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+unsubscr...@googlegroups.com. To post to this group, send email to sage-support@googlegroups.com. Visit this group at http://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout.
[sage-support] Re: simple 'solve' error, possibly related to ecl and maxima installation
Op donderdag 20 november 2014 21:07:55 UTC+1 schreef Nils Bruin: On Thursday, November 20, 2014 4:36:52 AM UTC-8, Peter Bruin wrote: It could be caused by the following lines in the Maxima source code (in src/commac.lisp): (defparameter trailing-zeros-regex-f-0 (compile nil (maxima-nregex::regex-compile ^(.*\\.[0-9]*[1-9])00*$))) (defparameter trailing-zeros-regex-f-1 (compile nil (maxima-nregex::regex-compile ^(.*\\.0)00*$))) (defparameter trailing-zeros-regex-e-0 (compile nil (maxima-nregex::regex-compile ^(.*\\.[0-9]*[1-9])00*([^0-9][+-][0-9]*)$))) (defparameter trailing-zeros-regex-e-1 (compile nil (maxima-nregex::regex-compile ^(.*\\.0)00*([^0-9][+-][0-9]*)$))) These are executed each time Maxima starts. The call to compile apparently invokes the C compiler. Indeed, a feature of ECL is that compile defers to the C compiler. It is of course crazy this gets compiled every initialization of maxima. I don't think this happened before either. These definitions seem to have been introduced between 5.33.0 and 5.34.1. Yes, I noticed this while working on http://trac.sagemath.org/ticket/16908 but didn't realise that this essentially made a C compiler a requirement for running Sage... Peter -- 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+unsubscr...@googlegroups.com. To post to this group, send email to sage-support@googlegroups.com. Visit this group at http://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout.
[sage-support] Re: simple 'solve' error, possibly related to ecl and maxima installation
I'm completely ignorant of the internal compilation. Can I understand the problem this way: for a binary file, the compilation has been done already, so it should not be necessary for maxima to compile itself every time I call it. After I installed command line tools, the required compiler is there, so it successfully compiled itself though conceptually it is not necessary. This seems logical to me, but there seems to be another problem: I googled and has been told that for newer versions of Xcode (my version is 6.1), command line tools has been installed already. But anyway it all turns out good after I reinstalled CLT. Now I could launch maxima successfully, except that I got this new warnings every time I started calculations: https://groups.google.com/forum/#!topic/sage-support/JxBv382J9tI. Are these warnings signs that maxima is still compiling itself every time I started? Since these problems seem to be unique only on my mac (and the weird non-existence of CLT in Xcode), can I assume that the problem actually lies in my OSX or Xcode? I actually tried uninstall Xcode completely and reinstall, but the warnings are still there. Thanks again for your efforts into this. And apologies for my ignorance. On Friday, November 21, 2014 4:07:55 AM UTC+8, Nils Bruin wrote: On Thursday, November 20, 2014 4:36:52 AM UTC-8, Peter Bruin wrote: It could be caused by the following lines in the Maxima source code (in src/commac.lisp): (defparameter trailing-zeros-regex-f-0 (compile nil (maxima-nregex::regex-compile ^(.*\\.[0-9]*[1-9])00*$))) (defparameter trailing-zeros-regex-f-1 (compile nil (maxima-nregex::regex-compile ^(.*\\.0)00*$))) (defparameter trailing-zeros-regex-e-0 (compile nil (maxima-nregex::regex-compile ^(.*\\.[0-9]*[1-9])00*([^0-9][+-][0-9]*)$))) (defparameter trailing-zeros-regex-e-1 (compile nil (maxima-nregex::regex-compile ^(.*\\.0)00*([^0-9][+-][0-9]*)$))) These are executed each time Maxima starts. The call to compile apparently invokes the C compiler. Indeed, a feature of ECL is that compile defers to the C compiler. It is of course crazy this gets compiled every initialization of maxima. I don't think this happened before either. These definitions seem to have been introduced between 5.33.0 and 5.34.1. They can easily be rewritten in such a way that an init-time compile can be avoided, either by stripping out the compile statement entirely (I don't think this is critical code) or by forcing the compile statement to run at compile time. The short-term solution is probably to patch maxima to not compile these things at all. Longer term: https://sourceforge.net/p/maxima/bugs/2845/ -- 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+unsubscr...@googlegroups.com. To post to this group, send email to sage-support@googlegroups.com. Visit this group at http://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout.
[sage-support] Re: simple 'solve' error, possibly related to ecl and maxima installation
On Thursday, November 20, 2014 7:10:15 PM UTC-8, Bozh wrote: Are these warnings signs that maxima is still compiling itself every time I started? It looks like Peter correctly identified the problem. According to his assessment, Maxima compiles *some code* upon startup, but not all of maxima. Since these problems seem to be unique only on my mac (and the weird non-existence of CLT in Xcode), can I assume that the problem actually lies in my OSX or Xcode? The fact that maxima tries to compile something is not unique to your mac. The fact that the compilations failed was something relatively specific to your mac, but not unique to it. Peter sketched a system where it didn't work either. Hopefully, Peter will patch the maxima shipped with sage so that we avoid the compilation. Then probably the next sage release will not have this compilation issue anymore. In the longer run, hopefully the maxima people find a way around compiling some code at init-time. Then we can remove our patched behaviour we're going to need in the mean time. Thank you for informing us about the problem. It points at something that is undesirable in general, but wasn't really noticed. -- 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+unsubscr...@googlegroups.com. To post to this group, send email to sage-support@googlegroups.com. Visit this group at http://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout.
[sage-support] Re: simple 'solve' error, possibly related to ecl and maxima installation
OK, I got it. Thanks again. On Friday, November 21, 2014 11:34:44 AM UTC+8, Nils Bruin wrote: On Thursday, November 20, 2014 7:10:15 PM UTC-8, Bozh wrote: Are these warnings signs that maxima is still compiling itself every time I started? It looks like Peter correctly identified the problem. According to his assessment, Maxima compiles *some code* upon startup, but not all of maxima. Since these problems seem to be unique only on my mac (and the weird non-existence of CLT in Xcode), can I assume that the problem actually lies in my OSX or Xcode? The fact that maxima tries to compile something is not unique to your mac. The fact that the compilations failed was something relatively specific to your mac, but not unique to it. Peter sketched a system where it didn't work either. Hopefully, Peter will patch the maxima shipped with sage so that we avoid the compilation. Then probably the next sage release will not have this compilation issue anymore. In the longer run, hopefully the maxima people find a way around compiling some code at init-time. Then we can remove our patched behaviour we're going to need in the mean time. Thank you for informing us about the problem. It points at something that is undesirable in general, but wasn't really noticed. -- 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+unsubscr...@googlegroups.com. To post to this group, send email to sage-support@googlegroups.com. Visit this group at http://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout.
[sage-support] Re: simple 'solve' error, possibly related to ecl and maxima installation
Problem solved. I did not install 'Command Line Tools for Xcode' previously on my Mac because I did not read instructions on installing Sage from source code. After installing Command Line Tools, it works now. Though the installation of Sage is still from a binary one. Yes, this would solve it. However, it should not be necessary! Volker, any ideas on what the buildbot was thinking? @Nils and @kcrisman, thanks again for all your help. -- 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+unsubscr...@googlegroups.com. To post to this group, send email to sage-support@googlegroups.com. Visit this group at http://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout.
[sage-support] Re: simple 'solve' error, possibly related to ecl and maxima installation
I run the following code:
$ sage -maxima
And the messages are:
;;; Loading #P/Applications/sage/local/lib/ecl/cmp.fas
;;; OPTIMIZE levels: Safety=2, Space=0, Speed=3, Debug=0
;;;
;;; End of Pass 1.In file included from
/Applications/sage/local/lib/ecl/ecl/ecl-cmp.h:22:0,
from
/private/var/folders/gh/26025ywx7w128zfds279s_9rgn/T/ecl001IqKQ2b.c:5:
/Applications/sage/local/lib/ecl/ecl/ecl.h:20:65: fatal error: sys/types.h:
No such file or directory
#include sys/types.h /* size_t, pthread_t, pthread_mutex_t */
^
compilation terminated.
;;; Internal error:
;;; ** Error code 1 when executing
;;; (RUN-PROGRAM gcc (-I. -I/Applications/sage/local/lib/ecl/
-I/Users/buildslave-sage/slave/sage_git/build/local/include
-I/Users/buildslave-sage/slave/sage_git/build/local/include -g -O2
-fPIC -fno-common -Ddarwin -O2 -c
/private/var/folders/gh/26025ywx7w128zfds279s_9rgn/T/ecl001IqKQ2b.c
-o
/private/var/folders/gh/26025ywx7w128zfds279s_9rgn/T/ecl001IqKQ2b.o))
Condition of type: UNBOUND-VARIABLE
The variable C::GAZONK is unbound.
No restarts available.
Top level.
So the problem lies in Maxima? I also tried 'sage -ecl' and it seems
normal. Thanks in advance.
在 2014年11月18日星期二UTC+8上午8时14分25秒，Bozh写道：
Hi sage-support,
I'm a complete newbie to sage. Currently I started learning the very
first example in the tutorial on algebra, but got the following error in
'solve'. I'm running OS X 10.9.5, and sage version is 6.4.
sage: x=var('x')
sage: solve(x^2 + 3*x + 2, x)
In file included from /Applications/sage/local/lib/ecl/ecl/ecl-cmp.h:22:0,
from
/private/var/folders/gh/26025ywx7w128zfds279s_9rgn/T/ecl001XIVVfM.c:5:
/Applications/sage/local/lib/ecl/ecl/ecl.h:20:65: fatal error:
sys/types.h: No such file or directory
#include sys/types.h /* size_t, pthread_t, pthread_mutex_t */
^
compilation terminated.
;;; Internal error:
;;; ** Error code 1 when executing
;;; (RUN-PROGRAM gcc (-I. -I/Applications/sage/local/lib/ecl/
-I/Users/buildslave-sage/slave/sage_git/build/local/include
-I/Users/buildslave-sage/slave/sage_git/build/local/include -g -O2
-fPIC -fno-common -Ddarwin -O2 -c
/private/var/folders/gh/26025ywx7w128zfds279s_9rgn/T/ecl001XIVVfM.c
-o
/private/var/folders/gh/26025ywx7w128zfds279s_9rgn/T/ecl001XIVVfM.o))
---
RuntimeError Traceback (most recent call
last)
ipython-input-2-b5c9e6391cf6 in module()
1 solve(x**Integer(2) + Integer(3)*x + Integer(2), x)
/Applications/sage/local/lib/python2.7/site-packages/sage/symbolic/relation.pyc
in solve(f, *args, **kwds)
732 from sage.symbolic.expression import is_Expression
733 if is_Expression(f): # f is a single expression
-- 734 ans = f.solve(*args,**kwds)
735 return ans
736
/Applications/sage/local/lib/python2.7/site-packages/sage/symbolic/expression.so
in sage.symbolic.expression.Expression.solve
(build/cythonized/sage/symbolic/expression.cpp:45798)()
/Applications/sage/local/lib/python2.7/site-packages/sage/symbolic/expression.so
in sage.symbolic.expression.Expression._maxima_
(build/cythonized/sage/symbolic/expression.cpp:5388)()
/Applications/sage/local/lib/python2.7/site-packages/sage/structure/sage_object.so
in sage.structure.sage_object.SageObject._interface_
(build/cythonized/sage/structure/sage_object.c:4897)()
/Applications/sage/local/lib/python2.7/site-packages/sage/misc/lazy_import.so
in sage.misc.lazy_import.LazyImport.__getattr__
(build/cythonized/sage/misc/lazy_import.c:3030)()
/Applications/sage/local/lib/python2.7/site-packages/sage/misc/lazy_import.so
in sage.misc.lazy_import.LazyImport._get_object
(build/cythonized/sage/misc/lazy_import.c:2030)()
/Applications/sage/local/lib/python2.7/site-packages/sage/interfaces/maxima_lib.py
in module()
79 ecl_eval((setf *compile-verbose* NIL))
80 ecl_eval((setf *load-verbose* NIL))
--- 81 ecl_eval((require 'maxima))
82 ecl_eval((in-package :maxima))
83 ecl_eval((setq $nolabels t)))
/Applications/sage/local/lib/python2.7/site-packages/sage/libs/ecl.so in
sage.libs.ecl.ecl_eval
(build/cythonized/sage/libs/ecl.c:9161)()
/Applications/sage/local/lib/python2.7/site-packages/sage/libs/ecl.so in
sage.libs.ecl.ecl_eval
(build/cythonized/sage/libs/ecl.c:9094)()
/Applications/sage/local/lib/python2.7/site-packages/sage/libs/ecl.so in
sage.libs.ecl.ecl_safe_eval
(build/cythonized/sage/libs/ecl.c:4494)()
RuntimeError: ECL says: The variable C::GAZONK is unbound.
When I type solve(x^2+3*x+2,x) again, the error message changes to
[sage-support] Re: simple 'solve' error, possibly related to ecl and maxima installation
On Monday, November 17, 2014 8:49:14 PM UTC-5, Bozh wrote: I run the following code: $ sage -maxima And the messages are: Can you see what is in $ ls /usr/include/sys/ presumably types.h should be there. Did you download a binary? Can you say precisely which one you downloaded? It's possible that this one requires some developer headers or something, though that would be unfortunate. -- 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+unsubscr...@googlegroups.com. To post to this group, send email to sage-support@googlegroups.com. Visit this group at http://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout.
[sage-support] Re: simple 'solve' error, possibly related to ecl and maxima installation
On Monday, November 17, 2014 5:49:14 PM UTC-8, Bozh wrote: ;;; (RUN-PROGRAM gcc (-I. -I/Applications/sage/local/lib/ecl/ -I/Users/buildslave-sage/slave/sage_git/build/local/include -I/Users/buildslave-sage/slave/sage_git/build/local/include -g -O2 -fPIC -fno-common -Ddarwin -O2 -c /private/var/folders/gh/26025ywx7w128zfds279s_9rgn/T/ecl001IqKQ2b.c -o /private/var/folders/gh/26025ywx7w128zfds279s_9rgn/T/ecl001IqKQ2b.o)) Condition of type: UNBOUND-VARIABLE The variable C::GAZONK is unbound. You probably downloaded a binary? By the looks of it, ecl has some paths hard-baked into it: -I/Users/buildslave-sage/slave/sage_git/build/local/include. That path probably doesn't exist on your computer, but it was present on the mac on which the binary was built. Compilation would probably fail anyway, because you probably don't have a gcc that is compatible with the rest of the build (I assume we're not shipping gcc with our binary). The odd thing is that maxima deems it necessary to compile itself. Your binary should have a precompiled maxima available already. Something must have gotten damaged or the binary distribution from which you started is broken/incompatible with your OSX. First thing to try might be to try and install a fresh binary if you haven't done so already. -- 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+unsubscr...@googlegroups.com. To post to this group, send email to sage-support@googlegroups.com. Visit this group at http://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout.
[sage-support] Re: simple 'solve' error, possibly related to ecl and maxima installation
I tried 2 other binaries from different locations, but the problem remains. I noted from kcrisman's response that I have no '/usr/include/sys/' directory, so maybe this problem comes with Xcode? On Tuesday, November 18, 2014 11:07:56 AM UTC+8, Nils Bruin wrote: On Monday, November 17, 2014 5:49:14 PM UTC-8, Bozh wrote: ;;; (RUN-PROGRAM gcc (-I. -I/Applications/sage/local/lib/ecl/ -I/Users/buildslave-sage/slave/sage_git/build/local/include -I/Users/buildslave-sage/slave/sage_git/build/local/include -g -O2 -fPIC -fno-common -Ddarwin -O2 -c /private/var/folders/gh/26025ywx7w128zfds279s_9rgn/T/ecl001IqKQ2b.c -o /private/var/folders/gh/26025ywx7w128zfds279s_9rgn/T/ecl001IqKQ2b.o)) Condition of type: UNBOUND-VARIABLE The variable C::GAZONK is unbound. You probably downloaded a binary? By the looks of it, ecl has some paths hard-baked into it: -I/Users/buildslave-sage/slave/sage_git/build/local/include. That path probably doesn't exist on your computer, but it was present on the mac on which the binary was built. Compilation would probably fail anyway, because you probably don't have a gcc that is compatible with the rest of the build (I assume we're not shipping gcc with our binary). The odd thing is that maxima deems it necessary to compile itself. Your binary should have a precompiled maxima available already. Something must have gotten damaged or the binary distribution from which you started is broken/incompatible with your OSX. First thing to try might be to try and install a fresh binary if you haven't done so already. -- 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+unsubscr...@googlegroups.com. To post to this group, send email to sage-support@googlegroups.com. Visit this group at http://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout.
[sage-support] Re: simple 'solve' error, possibly related to ecl and maxima installation
Problem solved. I did not install 'Command Line Tools for Xcode' previously on my Mac because I did not read instructions on installing Sage from source code. After installing Command Line Tools, it works now. Though the installation of Sage is still from a binary one. @Nils and @kcrisman, thanks again for all your help. On Tuesday, November 18, 2014 10:10:39 AM UTC+8, kcrisman wrote: On Monday, November 17, 2014 8:49:14 PM UTC-5, Bozh wrote: I run the following code: $ sage -maxima And the messages are: Can you see what is in $ ls /usr/include/sys/ presumably types.h should be there. Did you download a binary? Can you say precisely which one you downloaded? It's possible that this one requires some developer headers or something, though that would be unfortunate. -- 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+unsubscr...@googlegroups.com. To post to this group, send email to sage-support@googlegroups.com. Visit this group at http://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout.
