Re: [sage-devel] Re: Newest Xcode is causing doctest failures

We definitely want to know if that works! > On 1/04/2018, at 08:03, Dima Pasechnik wrote: > > make distclean > and > make ? > > On Saturday, March 31, 2018 at 8:46:41 PM UTC+1, John H Palmieri wrote: > On an OS X machine, I just did a minor upgrade on the operating system

[sage-devel] Re: Newest Xcode is causing doctest failures

make distclean and make ? On Saturday, March 31, 2018 at 8:46:41 PM UTC+1, John H Palmieri wrote: > > On an OS X machine, I just did a minor upgrade on the operating system (to > 10.13.4) and also Xcode and the command line tools. Now I am getting > doctest failures: > > sage -t --long

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

The error message /etc/init.d/xprint: Command not found. repeats many times and this appears to break the configuration tests numpy is running. In the end it fails as e.g. it is unable to confirm that OpenBLAS works. And then it finishes with the error saying that it cannot find Fortran

Re: [sage-devel] Newest Xcode is causing doctest failures

Hum… I’d say a change in the host libc++. That’s annoying, I’d try rebuilding brial and singular and then the bits of sage depending on them. But we should get to the bottom of this, it may mean something is using something it shouldn’t. François > On 1/04/2018, at 07:46, John H Palmieri

[sage-devel] Newest Xcode is causing doctest failures

On an OS X machine, I just did a minor upgrade on the operating system (to 10.13.4) and also Xcode and the command line tools. Now I am getting doctest failures: sage -t --long src/sage/rings/polynomial/multi_polynomial_ideal.py # 1 doctest failed sage -t --long

[sage-devel] PEP draft to fix Python function classes

I have drafted a Python Enhancement Proposal (PEP) to unify built-in and Python functions: https://github.com/jdemeyer/PEP-functions This is just a draft for now, it has not officially been submitted (so there is no PEP number yet). Cython could benefit from this because Cython functions

[sage-devel] Re: openssl licensing

Due notice taken. That would simplify Trac#24107 (which is currently dormant, due to the undergoing changes in the configutation system) enormously. -- Emmanuel Charpentier Le samedi 31 mars 2018 14:06:11 UTC+2, Volker Braun a écrit : > >

[sage-devel] Re: openssl licensing

https://www.openssl.org/blog/blog/2018/03/01/last-license/ They want to change the license in the next release, which is currently in Alpha, and tentatively set for May. On Saturday, March 31, 2018 at 11:44:58 AM UTC+2, Thierry (sage-googlesucks@xxx) wrote: > > Hi, > > not sure whether

[sage-devel] openssl licensing

Hi, not sure whether there is a database access issue, but according to [1], there is no contributor to be found for relicensing openssl. That would be awesome. Ciao, Thierry [1] https://license.openssl.org/trying-to-find -- You received this message because you are subscribed to the Google

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

On Saturday, March 31, 2018 at 1:02:51 AM UTC+1, Samuel Lelievre wrote: > > > > 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

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

On Friday, March 30, 2018 at 8:12:12 PM UTC+1, Paul Mercat wrote: > > I tried to do "./make -i numpy", but I get the same error... What compiler is being used? "same error" with gcc 7.2, or still with gcc 4.8.5? The latter would be very odd. -- You received this message because you are