On Wednesday, March 8, 2017 at 8:59:07 PM UTC+1, Frédéric Chapoton wrote:
>
> * fix the SAGE_PYTHON3 build
>
This should just be a matter of installing our python package dependencies
into python3 as well as python2. I didn't think about that. We should
definitely have some more regression tests
For those of you like me who didn't know about this, git trac try is a fast
way to review tickets without having to build older versions. git trac try
automatically merges the current develop branch with only the changes on a
ticket into a temporary branch. If you've already built the current
d
There used to be a "make install" target but it is deprecated.
You should move the entire install and run
./sage --location
but I never do that. Someone else may have more experience with it.
Francois
On 09/03/17 10:52, Gere Mia wrote:
> I built mine in /tmp, now it wants me to run it in temp. Ho
I built mine in /tmp, now it wants me to run it in temp. How can I run it
from somewhere else?
On Wednesday, March 8, 2017 at 2:46:30 PM UTC-7, Gere Mia wrote:
>
> How does one move the sage directory after building it?
>
--
You received this message because you are subscribed to the Google Gro
How does one move the sage directory after building it?
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To post to this gr
Do not panic, please. Keep calm and carry on !
Two things (among many) where help would be welcome, rather than just
worried comments :
* fix the SAGE_PYTHON3 build
* opinion from a number-theory expert on the doctest failure in #22257
cheers,
Frederic
Le mercredi 8 mars 2017 11:42:29 UTC+1,
Hi,
Did you upgrade your gcc between compiling ntl and compiling giac? It seems
to me like ntl was compiled with gcc 4.x while you are trying to compile
giac with gcc 5.x.
Isuru Fernando
On Wed, Mar 8, 2017 at 8:37 PM, Darij Grinberg
wrote:
> Hi,
>
> I'm failing to build ("make build") 7.6.bet
On Wed, Mar 8, 2017 at 5:16 AM, Clemens Heuberger
wrote:
> Am 2017-03-08 um 12:37 schrieb Daniel Krenn:
>> On 2017-03-08 11:42, Frédéric Chapoton wrote:
>>> * step 1A : cythonizing : there remains only a few calls to cmp() that
>>> prevents cythonization of our pyx files
>>>
>>> -- some of them wi
Hi,
I'm failing to build ("make build") 7.6.beta6 on my university computer:
[giac-1.2.2.103] /home/dgrinber/sage-7.5.1/local/lib/libntl.so: undefined
reference to `vtable for std::__cxx11::basic_stringbuf, std::allocator >@GLIBCXX_3.4.21'
[giac-1.2.2.103] collect2: error: ld returned 1 exit sta
Am 2017-03-08 um 12:37 schrieb Daniel Krenn:
> On 2017-03-08 11:42, Frédéric Chapoton wrote:
>> * step 1A : cythonizing : there remains only a few calls to cmp() that
>> prevents cythonization of our pyx files
>>
>> -- some of them will maybe be handled by ticket #22549, that changes the
>> semanti
On 2017-03-08 11:42, Frédéric Chapoton wrote:
> * step 1A : cythonizing : there remains only a few calls to cmp() that
> prevents cythonization of our pyx files
>
> -- some of them will maybe be handled by ticket #22549, that changes the
> semantics of equality for real and complex interval fields
Hello,
an update on the python3 status. Moving slowly, long way ahead.
* currently, building sage with "SAGE_PYTHON3=yes" breaks much more early
than previously. This prevents to monitor seriously the progress towards
python3 and should be investigated as soon as possible.
* step 1A : cythoniz
Hi, a follow up for mentors: I thought mentors can ask to register,
but no, please contact me to be invited (and if not clear, tell me
which email address)
There is also a little bit of activity here:
https://groups.google.com/group/sage-gsoc/
-- harald
--
You received this message because you
13 matches
Mail list logo
