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
*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
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
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
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.
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
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
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
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
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
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 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
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,
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?
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
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
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,
17 matches
Mail list logo
