Mirabile dictu, it worked ! But it's a strange thing : AFAIK, ./configure 
is used to adapt a source to the specifics of a platform. This (usually) 
does not change between recompilations.

Except that Sagemath source carries a lot of its own buildig platform (e. 
g. gcc...). Is that the explanation ?

Thanks, John !

Le mercredi 28 octobre 2015 18:32:06 UTC+1, John H Palmieri a écrit :
>
>
>
> On Wednesday, October 28, 2015 at 10:19:51 AM UTC-7, Emmanuel Charpentier 
> wrote:
>>
>> Case in point : Trac#19469 <http://trac.sagemath.org/ticket/19469>. This 
>> ticket will solve an annoying quirk un the Ipython notebook.
>>
>> I tested it successfully on one installation, by recompiling the whole 
>> hog ( make distclean && make ).
>>
>> I have another installation, now up to 6.10beta1. I did successfully :
>> git trac checkout 
>> make (rebuilds the documentation, by the way...)
>>
>
> Try 
>
> ./configure
> make
>
> (although there is an open ticket which would make ./configure 
> unnecessary).
>
>   John
>
>
>> The resulting Sage still has the "old" behaviour.
>>
>> I also tried ./sage -b in $SAGE_ROOT. Same result.
>>
>> Is there a way to force the recompilation-reinstallation of the Ipythobn 
>> notebook ? I know that neither ./sage -i notebook or ./sage -f notebook 
>> work : these calls fail with complaining that they cannot find the source 
>> tarball... Further attempts to use this installation fail with the same 
>> error (sage has somehow registered that the Ipytho notebook is missing and 
>> tries to install it, unsuccessfully...).
>>
>> What am I missing ?
>>
>>

-- 
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 an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Reply via email to