Re: [sage-support] Re: [sage 7.4] Error building OpenBlas

2017-02-02 Thread Dima Pasechnik
You can always create a symbolic link in /usr/local/bin/ to some other location. sudo ln -sf /blah/foo/sage /usr/local/bin/sage after building sage in /blah/foo/ -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group

Re: [sage-support] Quadratic form polynomial

2017-02-02 Thread Christophe Bal
Hello. Who is the author of the quote "I would like to die. ..." ? Le 3 févr. 2017 01:40, "Justin C. Walker" a écrit : On Feb 2, 2017, at 12:51 , Watson Ladd wrote: > Dear all, > > I believe the q.polynomial() routine where q is a quadratic form is off by > a factor of 2. Or

Re: [sage-support] Quadratic form polynomial

2017-02-02 Thread Justin C. Walker
On Feb 2, 2017, at 12:51 , Watson Ladd wrote: > Dear all, > > I believe the q.polynomial() routine where q is a quadratic form is off by > a factor of 2. Or at least it should be. If we take the form q of dimension > 2 such that > q(1, 0)=q(0,1)=1, and q(1,1)=2, then q.polynomial() is

Re: [sage-support] Re: [sage 7.4] Error building OpenBlas

2017-02-02 Thread João Alberto Ferreira
Ok, thank you! I would be glad if you could explain how can we put sage in, for example, /usr/local/ or /opt/, if sage force us to compile without root privileges. On Thursday, February 2, 2017 at 11:50:14 PM UTC+1, John H Palmieri wrote: > > > > On Thursday, February 2, 2017 at 1:53:43 PM

Re: [sage-support] Re: [sage 7.4] Error building OpenBlas

2017-02-02 Thread John H Palmieri
On Thursday, February 2, 2017 at 1:53:43 PM UTC-8, João Alberto Ferreira wrote: > > Well, I read somewhere about this procedure of moving the directory before > starting sage, but the Installation Manual seems to tell the same thing. > > "The directory where you built Sage is *NOT* hardcoded.

Re: [sage-support] Re: [sage 7.4] Error building OpenBlas

2017-02-02 Thread João Alberto Ferreira
Well, I read somewhere about this procedure of moving the directory before starting sage, but the Installation Manual seems to tell the same thing. "The directory where you built Sage is *NOT* hardcoded. You should be able to safely move or rename that directory. (It’s a bug if this is not the

[sage-support] Quadratic form polynomial

2017-02-02 Thread Watson Ladd
Dear all, I believe the q.polynomial() routine where q is a quadratic form is off by a factor of 2. Or at least it should be. If we take the form q of dimension 2 such that q(1, 0)=q(0,1)=1, and q(1,1)=2, then q.polynomial() is 2*x_0^2+2*x_1^2, which seems weird to me. Also the documentation

Re: [sage-support] Re: [sage 7.4] Error building OpenBlas

2017-02-02 Thread Henri Girard
I think it has been said on the list : Keep sage where you compiled it ! If you want to change it you have to compile source again ! what I do because I work with git : I make a dir git I compile it there and after I link sage in /usr/bin/sage sudo ln -s /path where is sage/sage

[sage-support] Re: [sage 7.4] Error building OpenBlas

2017-02-02 Thread João Alberto Ferreira
Hi! I just removed "/home/mmsim/tools/lib/64bit" from the LD_LIBRARY_PATH environment variable and sage compiled. I compiled it in my home directory and moved it to /usr/local/ before starting it, and created a symbolic link in /usr/local/bin/, but it shows me python: error while loading

[sage-support] Re: [sage 7.4] Error building OpenBlas

2017-02-02 Thread Dima Pasechnik
On Thursday, February 2, 2017 at 10:36:41 AM UTC, João Alberto Ferreira wrote: > > > > On Wednesday, February 1, 2017 at 7:24:56 PM UTC+1, Dima Pasechnik wrote: >> >> >> >> On Wednesday, February 1, 2017 at 6:00:25 PM UTC, João Alberto Ferreira >> wrote: >>> >>> Well, not yet. >>> >>> openblas

[sage-support] Re: [sage 7.4] Error building OpenBlas

2017-02-02 Thread João Alberto Ferreira
On Wednesday, February 1, 2017 at 7:24:56 PM UTC+1, Dima Pasechnik wrote: > > > > On Wednesday, February 1, 2017 at 6:00:25 PM UTC, João Alberto Ferreira > wrote: >> >> Well, not yet. >> >> openblas has compiled successfully. The problem now is with R. The R log >> follows. >> >> Apparently it