[sage-devel] Re: Error starting sage for Ubuntu 16.04-x86_64 binary package

2016-03-30 Thread Eugene E.
The default version of Python in Arch Linux is 3, but I was under the impression that the Sage brings a python version of its own, no? On Wednesday, March 30, 2016 at 12:29:56 AM UTC+3, Dima Pasechnik wrote: > > What version of python do you get if you run python? My guess it is > version 3, and

Re: [sage-devel] Re: Error starting sage for Ubuntu 16.04-x86_64 binary package

2016-03-30 Thread Jan Groenewald
Hi On 30 March 2016 at 14:53, Jeroen Demeyer wrote: > On 2016-03-30 14:49, Eugene E. wrote: > >> The default version of Python in Arch Linux is 3, but I was under the >> impression that the Sage brings a python version of its own, no? >> > > Maybe it doesn't use that to run relocate-once.py > >

Re: [sage-devel] Re: Error starting sage for Ubuntu 16.04-x86_64 binary package

2016-03-30 Thread Jeroen Demeyer
On 2016-03-30 14:49, Eugene E. wrote: The default version of Python in Arch Linux is 3, but I was under the impression that the Sage brings a python version of its own, no? Maybe it doesn't use that to run relocate-once.py -- You received this message because you are subscribed to the Google G

[sage-devel] Re: Sage 7.1 segmentation fault when trying to build from source

2016-03-30 Thread Dima Pasechnik
On Wednesday, March 30, 2016 at 1:47:39 PM UTC+1, Eugene E. wrote: > > Sorry, forgot the log file. > > The packages installed on my system are: > core/gcc 5.3.0-5 (base-devel) > do you have gfortan and g++ ? I guess the only reason for Sage trying to build the gcc is that these are missing. Ins

[sage-devel] Re: Sage 7.1 segmentation fault when trying to build from source

2016-03-30 Thread Dima Pasechnik
forgot the obligatory (:-)) rtfm link: http://doc.sagemath.org/html/en/installation/source.html#prerequisites On Wednesday, March 30, 2016 at 3:10:05 PM UTC+1, Dima Pasechnik wrote: > > > > On Wednesday, March 30, 2016 at 1:47:39 PM UTC+1, Eugene E. wrote: >> >> Sorry, forgot the log file. >> >> T

Re: [sage-devel] Re: Error starting sage for Ubuntu 16.04-x86_64 binary package

2016-03-30 Thread Dima Pasechnik
On Wednesday, March 30, 2016 at 1:57:38 PM UTC+1, Jan Groenewald wrote: > > Hi > > On 30 March 2016 at 14:53, Jeroen Demeyer > wrote: > >> On 2016-03-30 14:49, Eugene E. wrote: >> >>> The default version of Python in Arch Linux is 3, but I was under the >>> impression that the Sage brings a pyth

[sage-devel] Linux on Windows

2016-03-30 Thread Mike Hansen
It's looking like Windows is getting support for the Linux API in its kernel (think the reverse of Wine) allowing it to run native Linux binaries. See http://blog.dustinkirkland.com/2016/03/ubuntu-on-windows.html. It seems like this might be a great alternative to Cygwin for Sage on Windows.

Re: [sage-devel] Re: Sage 7.1 Windows 8.1 Cygwin make error

2016-03-30 Thread Witold Żarowski
I can confirm that I was able to compile mprf using the patch you provided. Then ATLAS was compiling for ages, and after that another error occurred, this time compiling brial: libtool: compile: g++ -DHAVE_CONFIG_H -I. -I../../libpolybori/include/polybori

[sage-devel] Re: Linux on Windows

2016-03-30 Thread Volker Braun
Sounds like the devil is ice-skating to work today ;-) Of course MS had a posix layer since about forever, they just never did anything with it or really made it available for others to use... On Wednesday, March 30, 2016 at 6:51:50 PM UTC+2, Mike Hansen wrote: > > It's looking like Windows is g

Re: [sage-devel] Re: Linux on Windows

2016-03-30 Thread William Stein
On Wed, Mar 30, 2016 at 10:54 AM, Volker Braun wrote: > Sounds like the devil is ice-skating to work today ;-) > > Of course MS had a posix layer since about forever, they just never did > anything with it or really made it available for others to use... "the POSIX subsystem was essentially a che

Re: [sage-devel] Re: Linux on Windows

2016-03-30 Thread Volker Braun
On Wednesday, March 30, 2016 at 8:15:06 PM UTC+2, William wrote: > > "the POSIX subsystem was essentially a checkbox feature to meet some > government contracting requirements. [...]" > Thought that refers to the ancient "posix subsystem", not the more recent "windows services for unix" which I

Re: [sage-devel] Re: Linux on Windows

2016-03-30 Thread William Stein
On Wed, Mar 30, 2016 at 11:37 AM, Volker Braun wrote: > On Wednesday, March 30, 2016 at 8:15:06 PM UTC+2, William wrote: >> >> "the POSIX subsystem was essentially a checkbox feature to meet some >> government contracting requirements. [...]" > > > Thought that refers to the ancient "posix subsyst

[sage-devel] Re: Linux on Windows

2016-03-30 Thread 'Bill Hart' via sage-devel
It looks like this thing is going to be pretty solid [1]. I'm actually incredibly excited about it, more than I have been about Windows for about 20 years. Bill. [1] https://channel9.msdn.com/Events/Build/2016/P488 On Wednesday, 30 March 2016 18:51:50 UTC+2, Mike Hansen wrote: > > It's looking

[sage-devel] Re: Linux on Windows

2016-03-30 Thread 'Bill Hart' via sage-devel
It's almost a year since I predicted Microsoft would do something like this. I have an email from September last year which was a followup email some months after I told a colleague something like this would happen. If I recall our conversation correctly, I was pretty specific about being able

[sage-devel] Installation error: "Error: Source directory doesn't contain a conf.py file." & "Unable to fetch..."

2016-03-30 Thread miguel
Hello, I am trying to compile from source. I am running Kubuntu (Ubuntu 15.10) on kernel 4.2.0-34-generic. I have attached the dochtml.log file in .../sage-7.1/logs In awe and thanks, Miguel-Angel Manrique -- Setting permissions of DOT_SAGE direc

Re: [sage-devel] Installation error: "Error: Source directory doesn't contain a conf.py file." & "Unable to fetch..."

2016-03-30 Thread David Roe
I'm not sure what's going on with the docbuild, but FYI you should be able to run Sage (documentation is built after Sage is built). What happens when you run /mnt/zeta/sage-7.1/sage? David On Wed, Mar 30, 2016 at 8:20 PM, miguel wrote: > Hello, > > I am trying to compile from source. I am run

Re: [sage-devel] Installation error: "Error: Source directory doesn't contain a conf.py file." & "Unable to fetch..."

2016-03-30 Thread miguel
Hello Executing ./sage runs Sage beautifully :-) Thank you. Miguel-Angel Manrique On Wednesday, March 30, 2016 at 5:43:12 PM UTC-7, David Roe wrote: > > I'm not sure what's going on with the docbuild, but FYI you should be able > to run Sage (documentation is built after Sage is built). What

Re: [sage-devel] Installation error: "Error: Source directory doesn't contain a conf.py file." & "Unable to fetch..."

2016-03-30 Thread miguel
Hello Executing ./sage runs Sage beautifully :-) Thank you. Miguel-Angel Manrique -- 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...@googleg

[sage-devel] Docbuild: Unable to fetch knots/environment.pickle

2016-03-30 Thread Jori Mäntysalo
I try to work on #19435, which has nothing to do with knot theory. What I got is [reference] history_and_license: 0 todos, 1 index, 0 citations, 0 modules [reference] homology: 1 todos, 19 index, 32 citations, 18 modules [reference] interfaces: 2 todos, 46 index, 2 citations, 45 modules [referen