Thanks Dima. It turns out as absolutely essential for the implementation of
Gosper's algorithm. I can now get WZ certificates for complicated identities in
a few seconds.
Regards,
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe f
On Tuesday, January 24, 2017 at 8:14:23 PM UTC+1, William wrote:
>
> On Tue, Jan 24, 2017 at 11:05 AM, Jeroen Demeyer > wrote:
> > On 2017-01-24 16:14, William Stein wrote:
> >>
> >> I would very likely just get it done keeping the
> >> current behavior as much as possible.
> >
> >
> > As
surely people would not mind a HB based way to build Sage. Long ago HB was a
pain,due to linking to wrong libs all the time. Since then Sage switch to using
rpath, and it is much more robust in this sense.
--
You received this message because you are subscribed to the Google Groups
"sage-devel
P.S.
I looked at the ticket now. I don't know exactly what was wrong on their
end, but I have homebrew gcc (6.3.0) installed, including gfortran, and it
did not break my build, as far as I can tell (at the very least, it was
successfully built and runs fine the simple stuff I usually use it for).
That may be true, but IMHO this is already a specific issue of
incompatibility with a specific package, rather than a systemic
incompatibility with HB itself (e.g. as would be the case if HB relied on
said version of gfortran). I see it as no different than a situation where
the user installed gfor
It depend what compilers are exposed. Last time someone filled
a bug, gfortran from brew was interfering with the gfortran sage
installs. https://trac.sagemath.org/ticket/22112
Francois
On 25/01/17 11:46, Konstantin Kliakhandler wrote:
Ah, I misunderstood the question. AFAICT homebrew does not
Ah, I misunderstood the question. AFAICT homebrew does not adversely affect
the sage built. In particular, I was able to successfully build it several
times with 7.5.betaX 7.5.rcX and 7.5, on two separate machines (on which I
also have HB installed).
--
Konstantin Kliakhandler
http://slumpy.o
The question is, if you have homebrew installed, can you build Sage from
source? That is, extract the source tarball, type 'make' in the sage
directory, and have it complete successfully. I think the motivation behind
the question is, in the past, the presence of fink or macports prevented
Sage
I'm not sure exactly what you mean; I am able to *install* sage via
homebrew - what it does is effectively download the .dmg archive and unpack
it in an appropriate location. There is no homebrew package for building
sage from source, however. I can (probably) make one if necessary, however.
On Th
I made a distclean, and everything is back to normal after that. This issue
can be considered closed.
I think as some point I did a make without seeting SAGE_PYTHON3 to yes, and
quickly interrupted this make, but this had side effects.
Thanks for the help.
Frederic
Le mardi 24 janvier 2017 21
On 2017-01-24 10:40, Frédéric Chapoton wrote:
In fact, it seems that SAGE_PYTHON3=yes is no longer correctly
recognized... Did somebody change something in the build procedure?
Here is a guess: could it be that you set SAGE_PYTHON3=yes at some point
but then unset it later?
--
You received t
On Tue, Jan 24, 2017 at 11:05 AM, Jeroen Demeyer wrote:
> On 2017-01-24 16:14, William Stein wrote:
>>
>> I would very likely just get it done keeping the
>> current behavior as much as possible.
>
>
> As I said, the current behaviour is not documented. So you would have to
> actually reverse-engi
On 2017-01-24 16:14, William Stein wrote:
I would very likely just get it done keeping the
current behavior as much as possible.
As I said, the current behaviour is not documented. So you would have to
actually reverse-engineer the code to find out what the current
behaviour actually is. This
On 2017-01-24 14:29, Frédéric Chapoton wrote:
Jeroen, could you please try to build using SAGE_PYTHON3=yes and tell me
what happens ?
I did that and widgetsnbextension builds. The Python version is 3.5.1. I
did not try to build all of Sage that way.
--
You received this message because you a
That was my suspicion. Now does sage-on-cygwin use openblas?
If not that means the corresponding `.pc` files have to be filled
with something appropriate before installing any blas/lapack dependencies.
The present hack I introduced in gsl and causes this error is to force
the linking of libgsl to
On Tue, Jan 24, 2017 at 3:26 AM, Erik Bray wrote:
> To be clear, while Python 3 got rid of comparisons between built-in
> types that were ill-defined, that doesn't prevent one from
> implementing comparisons between one's own types however we want:
If I were doing the Python3 port (and I'm not,
On Tuesday, January 24, 2017 at 2:00:54 PM UTC, Frank Garvan wrote:
>
>
> Have attached config.log file
>
Thanks. I think what really happens is that openblas did not install
correctly, and gsl
has a dependence on it.
In more detail, your log says:
configure:3502: gcc -g -O2 -L/home/Owner/sa
Have attached config.log file
On Tuesday, January 24, 2017 at 3:26:49 AM UTC-5, François wrote:
>
> Need to see
> /home/Owner/sage/local/var/tmp/sage/build/gsl-2.1.p1/src/config.log
> but I suspect I am responsible.
>
> François
>
> > On 24/01/2017, at 14:51, Frank Garvan >
> wrote:
> >
>
Jeroen, could you please try to build using SAGE_PYTHON3=yes and tell me
what happens ?
Frederic
Le mardi 24 janvier 2017 13:12:34 UTC+1, Jeroen Demeyer a écrit :
>
> On 2017-01-24 09:36, Frédéric Chapoton wrote:
> > Last tentative of "export SAGE_PYTHON3=yes" then "make" fails as
> follows:
On 2017-01-24 09:36, Frédéric Chapoton wrote:
Last tentative of "export SAGE_PYTHON3=yes" then "make" fails as follows:
This is a new behaviour in 7.6.beta0.
I cannot reproduce this. Installing widgetsnbextension works for me,
both with Python 2 and Python 3.
--
You received this message be
Apparently there are two posts with the same subject,
one on sage-support and one on sage-devel. The two
messages you mention are on sage-support at
https://groups.google.com/d/topic/sage-support/m6tGTnuirqY/discussion
Le mardi 24 janvier 2017 09:29:51 UTC+1, Dima Pasechnik a écrit :
>
> I tried t
On Thu, Jan 19, 2017 at 10:53 PM, Jeroen Demeyer wrote:
> On 2017-01-19 17:44, William Stein wrote:
>>
>> On Thu, Jan 19, 2017 at 9:39 AM, Jeroen Demeyer
>> wrote:
>>>
>>> On 2017-01-19 17:17, William Stein wrote:
... and presumably what we already decided is now completely
im
In fact, it seems that SAGE_PYTHON3=yes is no longer correctly
recognized... Did somebody change something in the build procedure?
Frederic.
Le mardi 24 janvier 2017 09:36:11 UTC+1, Frédéric Chapoton a écrit :
>
> Last tentative of "export SAGE_PYTHON3=yes" then "make" fails as follows:
>
> Thi
Last tentative of "export SAGE_PYTHON3=yes" then "make" fails as follows:
This is a new behaviour in 7.6.beta0.
[widgetsnbextension-1.2.6.p0] Successfully installed
widgetsnbextension-1.2.6
[widgetsnbextension-1.2.6.p0] Cleaning up...
[widgetsnbextension-1.2.6.p0] Traceback (most recent call las
I tried to post a message, it got lost during the process (and a message by
Samuel).
I wonder whether the people who get sage-develop by email
can repost copies...
On Tuesday, January 24, 2017 at 8:24:33 AM UTC, Frank Garvan wrote:
>
>
> Have attached log file.
>
> Can this be fixed?
>
> Thanks
Need to see
/home/Owner/sage/local/var/tmp/sage/build/gsl-2.1.p1/src/config.log
but I suspect I am responsible.
François
> On 24/01/2017, at 14:51, Frank Garvan wrote:
>
>
> Have attached log file.
>
> Can this be fixed?
>
> Thanks
>
> PS: Running cygwin64 on windows10
> processor: Intel Co
Have attached log file.
Can this be fixed?
Thanks
PS: Running cygwin64 on windows10
processor: Intel Core i3-6100 CPU @ 3.70 Ghz
RAM: 8.00 GB
system type: 64-bit operating system, x64-based processor
--
You received this message because you are subscribed to the Google Groups
"sage-devel" gr
27 matches
Mail list logo
