***
IPython post-mortem report
{'commit_hash': u'5c9c918',
'commit_source': 'installation',
'default_encoding': 'ANSI_X3.4-1968',
'ipython_path': '/opt/sage/local/lib/python2.7/site-packages/IPython',
'ipython_version': '
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+uns
>
>
>
> On Thursday, March 9, 2017 at 8:55:22 PM UTC, Gere Mia wrote:
>>
>> I can run your binary-pkg
>> <https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Fsagemath%2Fbinary-pkg&sa=D&sntz=1&usg=AFQjCNEnRuZWLIPZdOQL7_t0kfK9mesuvw>
>>
>&
"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
>
--
ZWLIPZdOQL7_t0kfK9mesuvw>
>
> 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 8:35:16 PM UTC, Gere Mia wrote:
>>
>> This might have something to
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 ins
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 e
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.
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?
>
--
You received this message because you are subscribed to t
How does one move the sage directory after building 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 email
to sage-devel+unsubscr...@googlegroups.com.
To post to this gr
Does this have something to do with my building Sage as root?
On Tuesday, March 7, 2017 at 7:23:40 PM UTC-7, Gere Mia wrote:
>
> Now I get this error regarding installing package pip-8.1.2.p1:
>
>> sys:1: RuntimeWarning: not adding directory '' to sys.path since it
de. As a general precaution from similar
> exploits, you should not execute Python code from this directory
> /tmp/SBo/sage-7.5.1/local/bin/python: No module named pip
>
On Monday, March 6, 2017 at 10:35:25 AM UTC-7, Gere Mia wrote:
>
> I get this build error when trying to build tac
No, it's not part of Slackware. It's something a made. It probably isn't a
good idea. I didn't know about MAKEOPTS. Putting that in /etc/make.conf
sounds like the proper way of doing it. thanks
On Tuesday, March 7, 2017 at 1:39:11 PM UTC-7, François wrote:
>
> On 08/0
Both of you are right. My make is really a bash script/alias for "make
-j4", so that might have messed things up. I thought I tried using a
non-"-j" make, and it didn't work, but "MAKE='make -d' ./sage -p tachyon"
built it successfully. thank you
--
You received this message because you are su
writeable for every user on the box) and
> should not be used for installing)
>
>
> On Monday, March 6, 2017 at 5:35:25 PM UTC, Gere Mia wrote:
>>
>> I get this build error when trying to build tachyon-0.98.9.p5 in the
>> recent Sage 7.5.1.
>> Is there a fix for
I get this build error when trying to build tachyon-0.98.9.p5 in the recent
Sage 7.5.1.
Is there a fix for this?
thanks
--
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 emai
That worked. thanks
On Monday, March 6, 2017 at 9:34:53 AM UTC-7, Isuru Fernando wrote:
>
> You can try placing the patch file in build/pkgs/mpir/patches.
>
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop r
How could I apply this patch automatically during the build process? thanks
On Thursday, February 23, 2017 at 12:38:52 PM UTC-7, Isuru Fernando wrote:
>
> See
> https://github.com/wbhart/mpir/commit/fdb590023f7ca4b2e881a2e9573718e7ed180f03
>
> Isuru Fernando
>
> On Fri, Feb 24, 2017 at 12:46 AM,
Is there a way to solve this issue without downgrading SED?
On Tuesday, January 10, 2017 at 2:36:09 PM UTC-7, moritz wrote:
>
>
>
> On Tuesday, January 10, 2017 at 9:44:09 PM UTC+1, François wrote:
>>
>> Don't think so. Look at the logs at the messages about Sed during
>> configure.
>> Sed is use
19 matches
Mail list logo
