Re: [sage-devel] Host notebook() at localhost:8080/ instead of simply at localhost:8080

> > Is there a way to make make notebook() host at > localhost:8080/ > > instead of simply at localhost:8080? > > sagenb doesn't support base url's, but Jupyter definitely does. There was some work done along these lines in sagenb a while ago by Jonathan Gutow at

Re: [sage-devel] Host notebook() at localhost:8080/ instead of simply at localhost:8080

On Thu, Mar 9, 2017 at 6:00 PM, Gere Mia wrote: > Is there a way to make make notebook() host at localhost:8080/ > instead of simply at localhost:8080? sagenb doesn't support base url's, but Jupyter definitely does. Try searching the jupyter docs for command line options.

[sage-devel] Host notebook() at localhost:8080/ instead of simply at localhost:8080

Is there a way to make make notebook() host at localhost:8080/ instead of simply at localhost:8080? -- 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] Re: git trac try

Thats basically it. The script takes the develop branch and merges in the ticket. And in a "detached head", i.e. without messing up an existing branch. On Thursday, March 9, 2017 at 10:41:07 PM UTC+1, Paul Masson wrote: > > The documentation https://github.com/sagemath/git-trac-command at say

[sage-devel] Re: ipython-5.0.0 crash

I'll try it for building the next release. Is there a way to use binary-pkg with a custom packaging script? Slackware uses a script called makepkg. I'm not exactly sure how binary-pkg makes its packages. thanks On Thursday, March 9, 2017 at 3:06:08 PM UTC-7, Dima Pasechnik wrote: > > > > On

[sage-devel] A question about sage reference manual building

Hi, If I switch the current git branch to another in the sage repository and build sage, then sage copies and compiles only updated files. I expected the same happens when I build the sage reference manual. That is, among all rst files under the directories en/reference/*/sage, exactly those

[sage-devel] Re: ipython-5.0.0 crash

On Thursday, March 9, 2017 at 8:55:22 PM UTC, Gere Mia wrote: > > I can run your binary-pkg > > > script after having already finished building Sage? > no, you cannot. You

[sage-devel] Re: git trac try

The documentation https://github.com/sagemath/git-trac-command at say that it creates a detached HEAD merge of the ticket and the develop branch. Since that was written by Volker, perhaps he could provide more information. On Thursday, March 9, 2017 at 1:28:57 AM UTC-8, Eric Gourgoulhon wrote:

Re: [sage-devel] ipython-5.0.0 crash

"LD_LIBRARY_PATH=/opt/sage/local/lib sage" worked. thanks On Thursday, March 9, 2017 at 1:46:31 PM UTC-7, François wrote: > > A band aid may be to set LD_LIBRARY_PATH to /opt/sage/local/lib but that’s > a band aid only. > Would have to check that sage-env doesn’t destroy it. > > François > --

[sage-devel] Re: ipython-5.0.0 crash

I can run your binary-pkg script after having already finished building Sage? thanks On Thursday, March 9, 2017 at 1:48:02 PM UTC-7, Dima Pasechnik wrote: > > It definitely is

[sage-devel] Re: ipython-5.0.0 crash

It definitely is the case: dynamic library locations are hardcoded via the rpath facility. https://github.com/sagemath/binary-pkg I already mentioned builds in a special location and provides a script that edits binaries, replacing the rpaths to the one needed. On Thursday, March 9, 2017 at

Re: [sage-devel] ipython-5.0.0 crash

A band aid may be to set LD_LIBRARY_PATH to /opt/sage/local/lib but that’s a band aid only. Would have to check that sage-env doesn’t destroy it. François > On 10/03/2017, at 09:44, Gere Mia wrote: > > Yes, I built it in /tmp, moved it to /opt/sage (so SAGE_ROOT is

Re: [sage-devel] ipython-5.0.0 crash

Yes, I built it in /tmp, moved it to /opt/sage (so SAGE_ROOT is /opt/sage), and ran ./sage as root once. "sage -root" correctly gives /opt/sage. But now when I run Sage as root or user, I get this crash. On Thursday, March 9, 2017 at 1:33:19 PM UTC-7, François wrote: > > Is this a re-located

[sage-devel] Re: ipython-5.0.0 crash

This might have something to do with my having built Sage in /tmp and moved it to /opt. It ran just fine where I built it. -- 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

Re: [sage-devel] ipython-5.0.0 crash

Is this a re-located install? Francois On 10/03/17 09:30, Gere Mia wrote: ipython-5.0.0 crash in Sage 7.5.1 crashes on Linux: | ┌┐ │SageMathversion 7.5.1,ReleaseDate:2017-01-15 │ │Type"notebook()"forthe

[sage-devel] ipython-5.0.0 crash

ipython-5.0.0 crash in Sage 7.5.1 crashes on Linux: ┌┐ │ SageMath version 7.5.1, Release Date: 2017-01-15 │ │ Type "notebook()" for the browser-based notebook interface.│ │ Type "help()" for help.

Re: [sage-devel] build fails due to giac-1.2.2.103

Hi Francois, Ah! I see now. I started compiling in my office, then it failed and I tried fixing it via ssh. But I ran ssh on a different server. Will try again from my office now. Best regards and thanks for solving the riddle, Darij On Thu, Mar 9, 2017 at 2:22 PM, François Bissey

Re: [sage-devel] build fails due to giac-1.2.2.103

On 10/03/17 09:18, Darij Grinberg wrote: > Hi, > > On Thu, Mar 9, 2017 at 2:16 PM, Isuru Fernando wrote: >> Can you also attach the ntl log? > > Here it goes: https://dl.dropboxusercontent.com/u/83265276/ntl-10.1.0.log > > Best regards, > Darij > Sorry for the echo.

Re: [sage-devel] build fails due to giac-1.2.2.103

Hum, that's definitely a signal that ntl has been compiled with -std=c++11 and eclib doesn't. Which is strange because I put code in configure to make sure it would pick up the c++11 bit myself. I probably didn't take into account a corner case. On the other hand I think eclib should just switch

Re: [sage-devel] build fails due to giac-1.2.2.103

Hi, On Thu, Mar 9, 2017 at 2:16 PM, Isuru Fernando wrote: > Can you also attach the ntl log? Here it goes: https://dl.dropboxusercontent.com/u/83265276/ntl-10.1.0.log Best regards, Darij -- You received this message because you are subscribed to the Google Groups

Re: [sage-devel] build fails due to giac-1.2.2.103

Hi, Can you also attach the ntl log? Isuru Fernando On Fri, Mar 10, 2017 at 1:31 AM, Darij Grinberg wrote: > Hi Isuru, > > thank you. I'm recompiling now (after make distclean) and hitting a > similar-looking problem: >

Re: [sage-devel] build fails due to giac-1.2.2.103

Hi Isuru, thank you. I'm recompiling now (after make distclean) and hitting a similar-looking problem: https://dl.dropboxusercontent.com/u/83265276/eclib-20170104.log Could it be that some parts of the compilation use sage's gcc while others use the system gcc? Is there a way to force them all

Re: [sage-devel] State of sage built with clang/clang++ on OS X - update

On 2017-02-26 08:27, Isuru Fernando wrote: Anybody know why some python extensions with C++ as the language are compiled with -std=c99? I'm using sage-7.5.1 Fix at https://trac.sagemath.org/ticket/22554 -- You received this message because you are subscribed to the Google Groups "sage-devel"

[sage-devel] Re: Can't run binaries

On Wednesday, March 8, 2017 at 9:52:18 PM UTC, Gere Mia wrote: > > I built mine in /tmp, now it wants me to run it in temp. How can I run it > from somewhere else? > > On Wednesday, March 8, 2017 at 2:46:30 PM UTC-7, Gere Mia wrote: >> >> How does one move the sage directory after building it?

[sage-devel] Re: git trac try

Of course I may dig into git-trac sources, but can anyone tell what "git trac try" does in terms of plain git? Eric. -- 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