[sage-devel] Re: Compilation error sage-8.1

Le jeudi 29 mars 2018 18:18:09 UTC+2, Paul Mercat a écrit : > > Hello, > > I've tried to compile sage-8.1 on a linux server, and I get > the following error: > > Error building Sage. > > How can I solve this problem ? What version of Linux is this server running? Did other versions of Sage

[sage-devel] Re: Compilation error sage-8.1

I tried to do "./make -i numpy", but I get the same error... -- 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

[sage-devel] Re: Compilation error sage-8.1

This looks OK (there were download errors, but apparently it did work out in the end looking at the tail of this file shows Successfully installed gcc-7.2.0 Deleting temporary build directory /home/paul.mercat/sage-8.1/local/var/tmp/sage/build/gcc-7.2.0 Finished installing gcc-7.2.0.spkg Now,

Re: [sage-devel] Re: How much do we support the casual user

On Friday, March 30, 2018 at 6:35:12 PM UTC+2, John Cremona wrote: > > I don't think this will satisfy Ralf's casual user who will see 100 > warnings output from their loop and not find any of the primes they were > hoping for. > By default, the warning is only shown once in said loop. If the

Re: [sage-devel] Re: How much do we support the casual user

On 30 March 2018 at 09:22, Simon King wrote: > On 2018-03-30, Volker Braun wrote: > > The obvious answer: Show a warning if you test field elements for > primality > > * easy to implement using standard Python machinery > > * does not introduce

[sage-devel] Re: How much do we support the casual user

What about creating a `is_prime_integer` function? Explicit is better than implicit, and in that case we leave no ambiguity in the mathematical sense, but also cover the use case of the casual user. What i definitely don't want is `.is_prime()` return `True` when it is applied to an element

[sage-devel] Re: Compilation error sage-8.1

https://drive.google.com/open?id=1hHDMc9uEL9_SYrmq8Z6JPPFphL8uBzZ3 Le vendredi 30 mars 2018 17:10:24 UTC+2, Dima Pasechnik a écrit : > > > > On Friday, March 30, 2018 at 3:13:17 PM UTC+1, Paul Mercat wrote: >> >> Here is the file config.log >> > > something does not match here, as this log tells

[sage-devel] Re: Compilation error sage-8.1

On Friday, March 30, 2018 at 3:13:17 PM UTC+1, Paul Mercat wrote: > > Here is the file config.log > something does not match here, as this log tells that it's getting gcc 7.2 installed, but your numpy log still refers to gcc 4.8.5 Has the installation of gcc package been successful? (look for

[sage-devel] Re: Compilation error sage-8.1

Here is the file config.log Le vendredi 30 mars 2018 16:07:12 UTC+2, Paul Mercat a écrit : > > Hi, > > > There is no such file logs/pkgs/config.log. > > I tried to recompile with the option SAGE_INSTALL_GCC='yes', but I get the > same error: > > > real43m24.500s >

[sage-devel] Re: Compilation error sage-8.1

Hi, There is no such file logs/pkgs/config.log. I tried to recompile with the option SAGE_INSTALL_GCC='yes', but I get the same error: real43m24.500s

[sage-devel] Re: How much do we support the casual user

On 2018-03-30, Volker Braun wrote: > The obvious answer: Show a warning if you test field elements for primality > * easy to implement using standard Python machinery > * does not introduce backward-incompatibile changes > * is mathematically correct > * informative to