Re: [sage-devel] Compiling Sage stops at PPL

2018-07-20 Thread Odile
Le Fri, 13 Jul 2018 15:52:07 +0200,
Erik Bray  a écrit :


> > As a simple workaround, you could try for now building with
> > --enable-fat for MPIR, which builds a more machine-generic MPIR by
> > running:
> >
> > SAGE_FAT_BINARY=yes ./sage -f mpir
> >
> > Then, once MPIR has been re-built, run:
> >
> > make build
> >
> > again.  I don't think you necessarily need to keep SAGE_FAT_BINARY on,
> > but you might try it just in case.  
> 
> Alternatively, you can try the patch I just added at
> https://trac.sagemath.org/ticket/25858
> 
> First check out my branch (it's based on 8.3.rc0 so not much else is
> changed, though MPIR has many direct and indirect dependents so most
> of Sage will wind up being rebuilt):
> 
> $ git fetch
> $ git checkout --track origin/u/embray/ticket-25858
> 
> Rebuild MPIR; include SAGE_CHECK=yes to make sure it worked:
> 
> $ SAGE_CHECK=yes make mpir
> 
> If that worked then continue building the rest of Sage:
> 
> $ make
> 

Many thanks, it compiles perfectly this way! (both ways you suggest,
and not just with the 'develop' branch)

-- 
Odile
Open Dream Kit http://www.opendreamkit.org

-- 
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 group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


[sage-devel] Re: SM_Carter-Penrose_diag.ipynb

2018-07-20 Thread Simon King
Hi!

On 2018-07-20, aishen  wrote:
> the 24 input :X_SD_IV. = M_IV.chart(r't r:(0,2*m) 
> th:(0,pi):\theta ph:(0,2*pi):\phi')
> X_SD_IV

It looks very obscure and is certainly nothing that could be executed in
any version of SageMath (neither in command line nor in the notebook).

So, could you please rephrase your question with a self-contained example
that can be copy-and-pasted? In particular, provide definitions so that
the example can actually be executed --- so far, you didn't tell how M_IV
is defined.

Best regards,
Simon

-- 
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 group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


[sage-devel] SM_Carter-Penrose_diag.ipynb

2018-07-20 Thread aishen
Hi,
I don't remenber if it's in this  mailing list for SM , if not sorry :)

the 24 input :X_SD_IV. = M_IV.chart(r't r:(0,2*m) 
th:(0,pi):\theta ph:(0,2*pi):\phi')
X_SD_IV

gives me this error ?

ValueError: Assumption is inconsistent
I am with sagemath 8.3 rc1 and I just noticed I can use 8.2 and bingo there is 
no error in it, well as it's devel maybe you know about it ?

Thanks
Henri

-- 
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 group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


[sage-devel] 8.3.rc1: issue with sage banner

2018-07-20 Thread David . Coudert
I just did a fresh install of sagemath (git clone …) and the starting 
banner is weird. I don’t know if it’s due to my system (recent update to 
fedora 28) or to recent changes in Sagemath.
Any help to solve the issue is more than welcome ;)
David.

==
musclotte:/home/dcoudert/sage> uname -a
Linux musclotte 4.17.6-200.fc28.x86_64 #1 SMP Wed Jul 11 20:29:01 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux
musclotte:/home/dcoudert/sage> gcc --version
gcc (GCC) 8.1.1 20180712 (Red Hat 8.1.1-5)
Copyright (C) 2018 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
musclotte:/home/dcoudert/sage> git branch
* develop
  master
musclotte:/home/dcoudert/sage> ./sage
?
sage: 

===


-- 
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 group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


Re: [sage-devel] Release schedule survey

2018-07-20 Thread Emmanuel Charpentier
Ahem...

Le jeudi 19 juillet 2018 01:20:28 UTC+2, Volker Braun a écrit :

[ Snip... ]

 The same people that wish for a rigid schedule now will complain later 
> that they missed the merge window by a day ;-) 
>

Hmmm... Bayesian suggestion : make the schedule dates random variables and 
publish their distribution ? 

More seriously : did someone do a retrospective analysis of the release 
schedules (both announced an effective) over the last, say, 3 years ? And 
what can/could be learned from this analysis ?

I know that mathematicians may abhor using experimental evidence, but in 
this case, we are trying to solve a "physical" problem (i. e. something 
*really* happening in the φθσις), not a mathematical one...

-- 
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 group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.