[sage-devel] Re: Error installing package ncurses-5.9.20131221
Seems obvious when you say it... Thankyou that did the job On Saturday, 3 October 2015 16:42:46 UTC+8, Volker Braun wrote: > > Since this is presumably fixed, can you try the latest beta/rc candidate? > > You can get the latest beta version from the "develop" git branch. > Alternatively, the self-contained source tarball is at > http://www.sagemath.org/download-latest.html > > > On Saturday, October 3, 2015 at 10:35:58 AM UTC+2, Tom Kitchen wrote: >> >> I get the following error when trying to compile sage with gcc 5.2. I >> believe it is the same as the ticket here >> http://trac.sagemath.org/ticket/18977#no1. I am running Manjaro linux. >> >> >> >> Error installing package ncurses-5.9.20131221 >> >> Please email sage-devel (http://groups.google.com/group/sage-devel) >> explaining the problem and including the relevant part of the log file >> /home/tom/sage/logs/pkgs/ncurses-5.9.20131221.log >> Describe your computer, operating system, etc. >> If you want to try to fix the problem yourself, *don't* just cd to >> /home/tom/sage/local/var/tmp/sage/build/ncurses-5.9.20131221 and type >> 'make' or whatever is appropriate. >> Instead, the following commands setup all environment variables >> correctly and load a subshell for you to debug the error: >> (cd '/home/tom/sage/local/var/tmp/sage/build/ncurses-5.9.20131221' && >> '/home/tom/sage/sage' --sh) >> When you are done debugging, you can type "exit" to leave the subshell. >> >> Makefile:1249: recipe for target >> '/home/tom/sage/local/var/lib/sage/installed/ncurses-5.9.20131221' failed >> make[2]: *** >> [/home/tom/sage/local/var/lib/sage/installed/ncurses-5.9.20131221] Error 1 >> make[2]: Leaving directory '/home/tom/sage/build/make' >> Makefile:560: recipe for target 'all' failed >> make[1]: *** [all] Error 2 >> make[1]: Leaving directory '/home/tom/sage/build/make' >> >> real 24m8.450s >> user 18m56.620s >> sys 1m4.213s >> *** >> Error building Sage. >> >> The following package(s) may have failed to build (not necessarily >> during this run of 'make all'): >> >> * package: ncurses-5.9.20131221 >> log file: /home/tom/sage/logs/pkgs/ncurses-5.9.20131221.log >> build directory: >> /home/tom/sage/local/var/tmp/sage/build/ncurses-5.9.20131221 >> >> The build directory may contain configuration files and other potentially >> helpful information. WARNING: if you now run 'make' again, the build >> directory will, by default, be deleted. Set the environment variable >> SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this. >> >> Makefile:16: recipe for target 'all' failed >> make: *** [all] Error 1 >> >> >> >> From the log file >> >> [tom@manjaro sage]$ more >> /home/tom/sage/logs/pkgs/ncurses-5.9.20131221.log | grep error >> Configured with: /build/gcc/src/gcc-5.2.0/configure --prefix=/usr >> --libdir=/usr/lib --libexecdir=/usr/lib --mandir=/usr/share/man >> --infodir=/usr/share/info --with-bugurl=https://bugs.archlinux.org/ >> --enable-languages=c,c++,ada,fortran,go,lto,objc,obj-c++ --enable-shared >> --enable-threads=posix --enable-libmpx --with-system-zlib --with-isl >> --enable-__cxa_atexit --disable-libunwind-exceptions --enable-clocale=gnu >> --disable-libstdcxx-pch --disable-libssp --enable-gnu-unique-object >> --enable-linker-build-id --enable-lto --enable-plugin >> --enable-install-libiberty --with-linker-hash-style=gnu >> --enable-gnu-indirect-function --disable-multilib --disable-werror >> --enable-checking=release --with-default-libstdcxx-abi=gcc4-compatible >> gcc -DHAVE_CONFIG_H -I../ncurses -I../../ncurses -I. -I../include >> -I../../ncurses/../include -I/home/tom/sage/local/include -D_GNU_SOURCE >> -DNDEBUG -O2 --param max-inline-insns-single=1200 -fPIC -DUSE_TERMLIB -c >> ../../ncurses/tinfo/comp_error.c -o ../obj_s/comp_error.o >> gcc -O2 --param max-inline-insns-single=1200 -shared >> -Wl,-soname,`basename ../lib/libtinfo.so.5.9 .5.9`.5,-stats,-lc -o >> ../lib/libtinfo.so.5.9 ../obj_s/access.o ../obj_s/add_tries.o >> ../obj_s/alloc_ttype.o ../obj_s/codes.o ../obj_s/comp_captab.o >> ../obj_s/comp_error.o ../obj_s/comp_hash.o ../obj_s/db_iterator.o >> ../obj_s/doalloc.o ../obj_s/entries.o ../obj_s/fallback.o >> ../obj_s/free_ttype.o ../obj_s/getenv_num.o ../obj_s/home_terminfo.o >> ../obj_s/init_keytry.o ../obj_s/lib_acs.o ../obj_s/lib_baudrate.o >> ../obj_s/lib_cur_term.o ../obj_s/lib_data.o ../obj_s/lib_has_cap.o >> ../obj_s/lib_kernel.o ../obj_s/lib_keyname.o ../obj_s/lib_longname.o >> ../obj_s/lib_napms.o ../obj_s/lib_
[sage-devel] Re: Sources of funding - perhaps computer manufacturers?
On 10/3/15 05:27, Jeroen Demeyer wrote: On 2015-10-02 04:01, Jonathan wrote: interactively zoomable by click and drag. To be useable for most people they also need GUI adjustment of colors, symbols, etc. I saw some demo of a IPython/Jupyter widget which does exactly this: the plot is essentially a Javascript applet which allows zooming client-side (even without having Jupyter running). We have several implementations of such a thing in Jupyter community. Matplotlib has a basic implementation of this if you use "%matplotlib notebook" to change to the interactive backend. Bokeh may be what you saw, as it works also without a kernel running. We (at Bloomberg) also just open-sourced a plotting library we've been working on at Bloomberg for the last year or so which has interactivity, based on the Jupyter widgets: https://github.com/bloomberg/bqplot. Thanks, Jason -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: History of notebooks.
On 10/3/15 11:35, Thierry Dumont wrote: Hello, I am preparing a talk I will give to a group of engineers, about "Notebooks". I mean web technology based notebooks (not java, qt or something else, but notebooks which use your web browser); so I will speak about Sage Notebook, Ipython and Jupyter notebooks. My question is: -> Was Sage notebook at the origin of all ? The Sage notebook certainly preceded the IPython and Jupyter notebooks and served as one of the main inspirations for them. I've CCd Fernando and Brian from the Jupyter project to get a more definitive statement. Thanks, Jason -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] History of notebooks.
> > In 2012 maybe (?) some student from I think Brown University started > using sagenb, but described the UI as "making him want to gouge his > eyes out" (exact quote). I think we mustered up $5K of NSF money to > fund his work on improving the frontend. He seemed to not understand > the backend at all, only the frontend, and also deleted much > functionality that was documented, but I guess he hadn't read the > docs. Anyways, this never got merged and I don't know what happened > to it. I think this was the last nontrivial work on sage notebook. > > The newui branch still exists, if that's what you're talking about, and a couple very helpful contributors at the sagenb github site have kept it from getting too stale. I've never had the chance to try it out but from what I understand it's not bad, though as you say I'm sure it's not 100% on the functionality. -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: Sources of funding - perhaps computer manufacturers?
On 3 October 2015 at 16:38, rjf wrote: > > > > Most software developers seeking funding need a "killer app". I don't > know that Mathematica has one -- but maybe it is STEM education, > since that's the major way of selling lots of systems. There were > forays into financial software, engineering, visualization, web hosting, > information storage "curated" (Alpha). All of these were however > premised on the sale of the system to users, or selling of online > services (or maybe ads?) > > I've often wondered where Wolfram Research make their money. Clearly Mathematica is their main product, but based on personal experience, and job adverts, I rarely see any employer wanting skills in Mathematica. Contrast that with MATLAB, and there are a huge number of jobs calling for MATLAB skills. It makes me think that the only significant purchasers of Mathematica are academic institutions. So I don't know what their "killer app" is, as I have never seen any evidence to suggest they have one. I can only think it is selling to academia - as to what areas, I have no idea. Dave -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] History of notebooks.
On Sat, Oct 3, 2015 at 8:35 AM, Thierry Dumont wrote: > Hello, > > I am preparing a talk I will give to a group of engineers, about > "Notebooks". I mean web technology based notebooks (not java, qt or > something else, but notebooks which use your web browser); so I will speak > about Sage Notebook, Ipython and Jupyter notebooks. > > My question is: > > -> Was Sage notebook at the origin of all ? As you define it above, yes, I think it was the origin of all... but it was also *very* heavily influenced by many other things. I wrote the first version with help from Tom Boothby and Alex Clemesha in 2006.Our motivation was (1) A failed summer attempt by two students in San Diego to provide a GUI for iPython, which was not web based, but was demoed in a talk at Sage Days 1. I instantly started prototypingvery crappy approachs to the same problem, maybe minutes after that talk. (2) Mathematica, obviously. Alex Clemesha was a UCSD physics undergrad who like/used Mathematics notebooks. Of course, I had used Maple/Mathematica notebooks myself too back in 1993 as an undergrad. (3) Gmail and Google maps, which pioneered use of "AJAX" = web applications that don't have to refresh the whole page every time you do anything. I clearly remember standing in my office in 2006 and trying to figure out solutions to problems like "make the output appear as it is produced when you run this code: for i in range(10): sleep(1) print i" I demoed the first public web-based sage notebook at a talk I gave at digipen (a video-game programming college near Microsoft). If I remember correctly, there were no accounts -- all users shared everything. There were named worksheets, but I think you could only add new cells (not delete existing stuff). It was all persistent though. I used to teach every summer in this program (SIMUW): http://www.math.washington.edu/~simuw/thisyear/index.html A year after the first sage notebook stuff, mentioned above, mostly me and Bobby Moretti spend a huge amount of time during about *2 weeks* right before 2007 SIMUW writing a new version of the Sage notebook that was much more powerful, in that it had user accounts, making documents public, etc.We had to finish the entire thing in about 2 weeks, since I wanted to use it for SIMUW, and those dates were fixed. Instead of worrying about UI design, we mostly just copied Google docs, so in 2007 Sagenb looked almost exactly the same as Google docs. (I don't think Google docs had synchronized editing back then -- only one at a time, just like sagenb even today.) Actually, sagenb *today* in 2015 looks much the same as Google docs looked in 2007, but nothing like Google docs today, since just as we were releasing sagenb, Google docs's UI got completely redone. Google also had something called "Google notebook" for a little while -- they release it after sage notebook, but it coincidentally looked very similar. It didn't compute anything -- it was like Sage notebook without any computational ability. Of course Google killed it. There was also Google wave, which was again similar, and again got killed. I think in 2008, Alex Clemesha wrote something called Knoboo, which is here: https://github.com/knoboo/knoboo It hasn't been touched in 6 years. He would have continued working on massively improving the sage notebook, but I couldn't afford to pay him. [Repeatedly realizing and actually acknowledging the number of massive lost opportunities for lack of money during the last 10 years really hurts.] So he tried some new experimental open source stuff on his own, but then stopped as he had a fulltime job. Mike Hansen, Robert Bradshaw, Jason Grout and I at some point rewrote some of the notebook backend in FLASK/Twisted so that it would scale up a little more since a lot of people wanted to use it. The site sagenb.org got a lot of traffic, but would routinely die due to overuse, and was massively limited by lack of scalability (not lack of demand). It also regularly got abused in every imaginable way by assholes, causing no end of grief (and having all of the sage.math resources banned from the internet multiple times at UW). For a while Tim Dummol -- a 16 year old high school student in the Philippines (!) -- became the main developer on the sage notebook, polishing many little things, fixing every bug he could find, etc., etc.Then he graduated high school, went to college somewhere, and we never heard from him again. In 2012 maybe (?) some student from I think Brown University started using sagenb, but described the UI as "making him want to gouge his eyes out" (exact quote). I think we mustered up $5K of NSF money to fund his work on improving the frontend. He seemed to not understand the backend at all, only the frontend, and also deleted much functionality that was documented, but I guess he hadn't read the docs. Anyways, this never got merged and I don't know what happened to it. I think this wa
Re: [sage-devel] Sage in Mac OSX 11.11 (El Capitan)
If switching to rpath starts up, it could be a great learning opportunity for those of us who want to ramp up on the Sage build system. It would be great if project wizards leave a trail for others to catch up & help with testing. I have done sage builds on Mac over the last couple years & several times ran into time-consuming challenges. On Sat, Oct 3, 2015 at 12:27 PM, William Stein wrote: > Hi, > > In the meantime, I think ASAP on the OS X binary download page we should: > > (1) move the "Usage:" message to the top (it's *hidden* at the bottom > where nobody will ever see it). > > (2) add that there is no way to run Sage on 10.11 except to either > disable Apple's system integrity protection, or use a virtual machine > running Linux. > > When I searched around for info about "system integrity protection" I > hit numerous other software websites with similar warnings and > notices. > > William > > On Sat, Oct 3, 2015 at 9:47 AM, Dima Pasechnik wrote: > > > > > > On Saturday, 3 October 2015 01:56:21 UTC-7, Volker Braun wrote: > >> > >> On Saturday, October 3, 2015 at 10:49:03 AM UTC+2, kcrisman wrote: > >>> > >>> Is that a sustainable solution for everyone? > >> > >> > >> No its not, we can't go around telling people to disable Apple's system > >> integrity protection. > > > > > > OK, so let's talk about switching to rpath then. Is it basically just > > tweaking of parameters passed to gcc (as a linker)? Do autotools know > about > > them? > > Do we need extra tools (or convoluted calls to linker etc) on OSX? > > Can we keep the LD_*_PATH* functionality, to use it on Cygwin? > > > > > > -- > > 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 group, send email to sage-devel@googlegroups.com. > > Visit this group at http://groups.google.com/group/sage-devel. > > For more options, visit https://groups.google.com/d/optout. > > > > -- > William (http://wstein.org) > > -- > You received this message because you are subscribed to a topic in the > Google Groups "sage-devel" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/sage-devel/OBv5x1v3_6M/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > sage-devel+unsubscr...@googlegroups.com. > To post to this group, send email to sage-devel@googlegroups.com. > Visit this group at http://groups.google.com/group/sage-devel. > For more options, visit https://groups.google.com/d/optout. > -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Sage in Mac OSX 11.11 (El Capitan)
Hi, In the meantime, I think ASAP on the OS X binary download page we should: (1) move the "Usage:" message to the top (it's *hidden* at the bottom where nobody will ever see it). (2) add that there is no way to run Sage on 10.11 except to either disable Apple's system integrity protection, or use a virtual machine running Linux. When I searched around for info about "system integrity protection" I hit numerous other software websites with similar warnings and notices. William On Sat, Oct 3, 2015 at 9:47 AM, Dima Pasechnik wrote: > > > On Saturday, 3 October 2015 01:56:21 UTC-7, Volker Braun wrote: >> >> On Saturday, October 3, 2015 at 10:49:03 AM UTC+2, kcrisman wrote: >>> >>> Is that a sustainable solution for everyone? >> >> >> No its not, we can't go around telling people to disable Apple's system >> integrity protection. > > > OK, so let's talk about switching to rpath then. Is it basically just > tweaking of parameters passed to gcc (as a linker)? Do autotools know about > them? > Do we need extra tools (or convoluted calls to linker etc) on OSX? > Can we keep the LD_*_PATH* functionality, to use it on Cygwin? > > > -- > 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 group, send email to sage-devel@googlegroups.com. > Visit this group at http://groups.google.com/group/sage-devel. > For more options, visit https://groups.google.com/d/optout. -- William (http://wstein.org) -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Sage in Mac OSX 11.11 (El Capitan)
On Saturday, 3 October 2015 01:56:21 UTC-7, Volker Braun wrote: > > On Saturday, October 3, 2015 at 10:49:03 AM UTC+2, kcrisman wrote: > >> Is that a sustainable solution for everyone? > > > No its not, we can't go around telling people to disable Apple's system > integrity protection. > OK, so let's talk about switching to rpath then. Is it basically just tweaking of parameters passed to gcc (as a linker)? Do autotools know about them? Do we need extra tools (or convoluted calls to linker etc) on OSX? Can we keep the LD_*_PATH* functionality, to use it on Cygwin? -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] History of notebooks.
Hello, I am preparing a talk I will give to a group of engineers, about "Notebooks". I mean web technology based notebooks (not java, qt or something else, but notebooks which use your web browser); so I will speak about Sage Notebook, Ipython and Jupyter notebooks. My question is: -> Was Sage notebook at the origin of all ? Yours, Thanks t. -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout. <>
Re: [sage-devel] Re: Sources of funding - perhaps computer manufacturers?
I think that if you look back at the early rave reviews of Mathematica in such notable scientific journals as the New York Times, you will see that the reporters were impressed by color graphics of 3-d plots and endorsement of such scientific notables as Steve Jobs, Also the eccentric aspects of the humble and modest Stephen Wolfram. Also, giving it away on NeXt machines made an impression. They did not notice that there were (at the time) better graphics programs, better computers, and even more eccentric people. They seem to have lots of them coming from British schools. Most software developers seeking funding need a "killer app". I don't know that Mathematica has one -- but maybe it is STEM education, since that's the major way of selling lots of systems. There were forays into financial software, engineering, visualization, web hosting, information storage "curated" (Alpha). All of these were however premised on the sale of the system to users, or selling of online services (or maybe ads?) If you insist on free and open source, it seems to me that you get nothing from your markets. So a killer app does nothing for you. (Is this the killer app du jour: rapid dating ?) Who was it who said (approximately) that "I spend my days writing free software so that I can earn money in the evening delivering pizza"? I suggested that the market for my (free, open source) TILU online integration service could be the selling of advertising, presumably to freshman calculus students. ( soft drinks? acne medication? ) but never pursued it. Maybe online ads for Sage??? Otherwise,I think you are left with finding and impressing one of those rich people who thinks math programs are kool. (You will have to judge for yourself how much of the above note is sarcasm.) Good luck. On Thursday, October 1, 2015 at 7:01:40 PM UTC-7, Jonathan wrote: > > > > On Thursday, October 1, 2015 at 2:32:29 AM UTC-5, Jeroen Demeyer wrote: >> >> On 2015-10-01 04:13, Jonathan wrote: >> > high quality zoomable 2-D graphics >> It's interesting that you think that Sage cannot do this. Because I >> think that Matplotlib's plots (which is what Sage uses) are "high >> quality zoomable 2-D graphics". So I wonder what you're missing. >> > > When I say high-quality zoomable, I mean publication quality (see the kind > of plots that appear in Science, American Scientist, Nature or any American > Chemical Society or American Institute of Physics journals) and > interactively zoomable by click and drag. To be useable for most people > they also need GUI adjustment of colors, symbols, etc. I started to work > on some of these features for the 3-D graphics, but simply do not have the > time necessary. Anyway, I like Sage a lot, but we are very short on > resources to bring things to the necessary level in the user interface. > > The backend is good some places and not others, but is potentially very > strong and robust because of the use of other packages. As I track this > discussion, I think that I like the idea of focusing on how to make all > these things easily added and removed packages as necessary. Maybe > ipython/jupyter with good pypi packaging (I'm still not clear on how to > package non-python stuff this way) is the way to go. That would change > Sagemath a lot, but might be a better use of resources. > > Jonathan > > Jonathan > -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: Sources of funding - perhaps computer manufacturers?
On 2015-10-02 04:01, Jonathan wrote: interactively zoomable by click and drag. To be useable for most people they also need GUI adjustment of colors, symbols, etc. I saw some demo of a IPython/Jupyter widget which does exactly this: the plot is essentially a Javascript applet which allows zooming client-side (even without having Jupyter running). -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Sage in Mac OSX 11.11 (El Capitan)
On Saturday, October 3, 2015 at 10:49:03 AM UTC+2, kcrisman wrote: > Is that a sustainable solution for everyone? No its not, we can't go around telling people to disable Apple's system integrity protection. -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: Sources of funding - perhaps computer manufacturers?
> > > When I say high-quality zoomable, I mean publication quality (see the kind > of plots that appear in Science, American Scientist, Nature or any American > Chemical Society or American Institute of Physics journals) and > interactively zoomable by click and drag. To be useable for most people > they also > Right, this is in principle possible but hasn't been implemented in the notebook yet. William, I thought maybe you had made some pretty significant progress toward this in SMC? -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Sage in Mac OSX 11.11 (El Capitan)
> > > I upgraded to Mac OS 10.11 this afternoon. I tried running sage -b and > found the following error: > > -bash:/Applications/sage/src/sage $ sage -b > python -u setup.py install > Traceback (most recent call last): > File "setup.py", line 4, in > import os, sys, time, errno, platform, subprocess, glob > File "/Applications/sage/local/lib/python/subprocess.py", line 430, in > > import pickle > File "/Applications/sage/local/lib/python/pickle.py", line 34, in > > import struct > File "/Applications/sage/local/lib/python/struct.py", line 1, in > from _struct import * > ImportError: > dlopen(/Applications/sage/local/lib/python2.7/lib-dynload/_struct.so, 2): > Symbol not found: _PyUnicodeUCS4_AsEncodedString > Referenced from: > /Applications/sage/local/lib/python2.7/lib-dynload/_struct.so > Expected in: flat namespace > in /Applications/sage/local/lib/python2.7/lib-dynload/_struct.so > make: *** [sage] Error 1 > > I followed the advice to reboot with command-R and ran the 'csrutil > disable' command in the terminal window. Next time I tried it worked. > > Thanks! > >> Is that a sustainable solution for everyone? (I assume not, e.g. those who only use the notebook.) Also, some people may not have access to that command if their computer is locked down by an employer (or would this escape the notice?). Maybe at the very least there should be a big warning on the download page to not use El Capitan (yet). -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: Error installing package ncurses-5.9.20131221
Since this is presumably fixed, can you try the latest beta/rc candidate? You can get the latest beta version from the "develop" git branch. Alternatively, the self-contained source tarball is at http://www.sagemath.org/download-latest.html On Saturday, October 3, 2015 at 10:35:58 AM UTC+2, Tom Kitchen wrote: > > I get the following error when trying to compile sage with gcc 5.2. I > believe it is the same as the ticket here > http://trac.sagemath.org/ticket/18977#no1. I am running Manjaro linux. > > > > Error installing package ncurses-5.9.20131221 > > Please email sage-devel (http://groups.google.com/group/sage-devel) > explaining the problem and including the relevant part of the log file > /home/tom/sage/logs/pkgs/ncurses-5.9.20131221.log > Describe your computer, operating system, etc. > If you want to try to fix the problem yourself, *don't* just cd to > /home/tom/sage/local/var/tmp/sage/build/ncurses-5.9.20131221 and type > 'make' or whatever is appropriate. > Instead, the following commands setup all environment variables > correctly and load a subshell for you to debug the error: > (cd '/home/tom/sage/local/var/tmp/sage/build/ncurses-5.9.20131221' && > '/home/tom/sage/sage' --sh) > When you are done debugging, you can type "exit" to leave the subshell. > > Makefile:1249: recipe for target > '/home/tom/sage/local/var/lib/sage/installed/ncurses-5.9.20131221' failed > make[2]: *** > [/home/tom/sage/local/var/lib/sage/installed/ncurses-5.9.20131221] Error 1 > make[2]: Leaving directory '/home/tom/sage/build/make' > Makefile:560: recipe for target 'all' failed > make[1]: *** [all] Error 2 > make[1]: Leaving directory '/home/tom/sage/build/make' > > real 24m8.450s > user 18m56.620s > sys 1m4.213s > *** > Error building Sage. > > The following package(s) may have failed to build (not necessarily > during this run of 'make all'): > > * package: ncurses-5.9.20131221 > log file: /home/tom/sage/logs/pkgs/ncurses-5.9.20131221.log > build directory: > /home/tom/sage/local/var/tmp/sage/build/ncurses-5.9.20131221 > > The build directory may contain configuration files and other potentially > helpful information. WARNING: if you now run 'make' again, the build > directory will, by default, be deleted. Set the environment variable > SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this. > > Makefile:16: recipe for target 'all' failed > make: *** [all] Error 1 > > > > From the log file > > [tom@manjaro sage]$ more /home/tom/sage/logs/pkgs/ncurses-5.9.20131221.log > | grep error > Configured with: /build/gcc/src/gcc-5.2.0/configure --prefix=/usr > --libdir=/usr/lib --libexecdir=/usr/lib --mandir=/usr/share/man > --infodir=/usr/share/info --with-bugurl=https://bugs.archlinux.org/ > --enable-languages=c,c++,ada,fortran,go,lto,objc,obj-c++ --enable-shared > --enable-threads=posix --enable-libmpx --with-system-zlib --with-isl > --enable-__cxa_atexit --disable-libunwind-exceptions --enable-clocale=gnu > --disable-libstdcxx-pch --disable-libssp --enable-gnu-unique-object > --enable-linker-build-id --enable-lto --enable-plugin > --enable-install-libiberty --with-linker-hash-style=gnu > --enable-gnu-indirect-function --disable-multilib --disable-werror > --enable-checking=release --with-default-libstdcxx-abi=gcc4-compatible > gcc -DHAVE_CONFIG_H -I../ncurses -I../../ncurses -I. -I../include > -I../../ncurses/../include -I/home/tom/sage/local/include -D_GNU_SOURCE > -DNDEBUG -O2 --param max-inline-insns-single=1200 -fPIC -DUSE_TERMLIB -c > ../../ncurses/tinfo/comp_error.c -o ../obj_s/comp_error.o > gcc -O2 --param max-inline-insns-single=1200 -shared -Wl,-soname,`basename > ../lib/libtinfo.so.5.9 .5.9`.5,-stats,-lc -o ../lib/libtinfo.so.5.9 > ../obj_s/access.o ../obj_s/add_tries.o ../obj_s/alloc_ttype.o > ../obj_s/codes.o ../obj_s/comp_captab.o ../obj_s/comp_error.o > ../obj_s/comp_hash.o ../obj_s/db_iterator.o ../obj_s/doalloc.o > ../obj_s/entries.o ../obj_s/fallback.o ../obj_s/free_ttype.o > ../obj_s/getenv_num.o ../obj_s/home_terminfo.o ../obj_s/init_keytry.o > ../obj_s/lib_acs.o ../obj_s/lib_baudrate.o ../obj_s/lib_cur_term.o > ../obj_s/lib_data.o ../obj_s/lib_has_cap.o ../obj_s/lib_kernel.o > ../obj_s/lib_keyname.o ../obj_s/lib_longname.o ../obj_s/lib_napms.o > ../obj_s/lib_options.o ../obj_s/lib_raw.o ../obj_s/lib_setup.o > ../obj_s/lib_termcap.o ../obj_s/lib_termname.o ../obj_s/lib_tgoto.o > ../obj_s/lib_ti.o ../obj_s/lib_tparm.o ../obj_s/lib_tputs.o > ../obj_s/lib_trace.o ../obj_s/lib_tty
[sage-devel] Error installing package ncurses-5.9.20131221
I get the following error when trying to compile sage with gcc 5.2. I believe it is the same as the ticket here http://trac.sagemath.org/ticket/18977#no1. I am running Manjaro linux. Error installing package ncurses-5.9.20131221 Please email sage-devel (http://groups.google.com/group/sage-devel) explaining the problem and including the relevant part of the log file /home/tom/sage/logs/pkgs/ncurses-5.9.20131221.log Describe your computer, operating system, etc. If you want to try to fix the problem yourself, *don't* just cd to /home/tom/sage/local/var/tmp/sage/build/ncurses-5.9.20131221 and type 'make' or whatever is appropriate. Instead, the following commands setup all environment variables correctly and load a subshell for you to debug the error: (cd '/home/tom/sage/local/var/tmp/sage/build/ncurses-5.9.20131221' && '/home/tom/sage/sage' --sh) When you are done debugging, you can type "exit" to leave the subshell. Makefile:1249: recipe for target '/home/tom/sage/local/var/lib/sage/installed/ncurses-5.9.20131221' failed make[2]: *** [/home/tom/sage/local/var/lib/sage/installed/ncurses-5.9.20131221] Error 1 make[2]: Leaving directory '/home/tom/sage/build/make' Makefile:560: recipe for target 'all' failed make[1]: *** [all] Error 2 make[1]: Leaving directory '/home/tom/sage/build/make' real 24m8.450s user 18m56.620s sys 1m4.213s *** Error building Sage. The following package(s) may have failed to build (not necessarily during this run of 'make all'): * package: ncurses-5.9.20131221 log file: /home/tom/sage/logs/pkgs/ncurses-5.9.20131221.log build directory: /home/tom/sage/local/var/tmp/sage/build/ncurses-5.9.20131221 The build directory may contain configuration files and other potentially helpful information. WARNING: if you now run 'make' again, the build directory will, by default, be deleted. Set the environment variable SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this. Makefile:16: recipe for target 'all' failed make: *** [all] Error 1 >From the log file [tom@manjaro sage]$ more /home/tom/sage/logs/pkgs/ncurses-5.9.20131221.log | grep error Configured with: /build/gcc/src/gcc-5.2.0/configure --prefix=/usr --libdir=/usr/lib --libexecdir=/usr/lib --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=https://bugs.archlinux.org/ --enable-languages=c,c++,ada,fortran,go,lto,objc,obj-c++ --enable-shared --enable-threads=posix --enable-libmpx --with-system-zlib --with-isl --enable-__cxa_atexit --disable-libunwind-exceptions --enable-clocale=gnu --disable-libstdcxx-pch --disable-libssp --enable-gnu-unique-object --enable-linker-build-id --enable-lto --enable-plugin --enable-install-libiberty --with-linker-hash-style=gnu --enable-gnu-indirect-function --disable-multilib --disable-werror --enable-checking=release --with-default-libstdcxx-abi=gcc4-compatible gcc -DHAVE_CONFIG_H -I../ncurses -I../../ncurses -I. -I../include -I../../ncurses/../include -I/home/tom/sage/local/include -D_GNU_SOURCE -DNDEBUG -O2 --param max-inline-insns-single=1200 -fPIC -DUSE_TERMLIB -c ../../ncurses/tinfo/comp_error.c -o ../obj_s/comp_error.o gcc -O2 --param max-inline-insns-single=1200 -shared -Wl,-soname,`basename ../lib/libtinfo.so.5.9 .5.9`.5,-stats,-lc -o ../lib/libtinfo.so.5.9 ../obj_s/access.o ../obj_s/add_tries.o ../obj_s/alloc_ttype.o ../obj_s/codes.o ../obj_s/comp_captab.o ../obj_s/comp_error.o ../obj_s/comp_hash.o ../obj_s/db_iterator.o ../obj_s/doalloc.o ../obj_s/entries.o ../obj_s/fallback.o ../obj_s/free_ttype.o ../obj_s/getenv_num.o ../obj_s/home_terminfo.o ../obj_s/init_keytry.o ../obj_s/lib_acs.o ../obj_s/lib_baudrate.o ../obj_s/lib_cur_term.o ../obj_s/lib_data.o ../obj_s/lib_has_cap.o ../obj_s/lib_kernel.o ../obj_s/lib_keyname.o ../obj_s/lib_longname.o ../obj_s/lib_napms.o ../obj_s/lib_options.o ../obj_s/lib_raw.o ../obj_s/lib_setup.o ../obj_s/lib_termcap.o ../obj_s/lib_termname.o ../obj_s/lib_tgoto.o ../obj_s/lib_ti.o ../obj_s/lib_tparm.o ../obj_s/lib_tputs.o ../obj_s/lib_trace.o ../obj_s/lib_ttyflags.o ../obj_s/lib_twait.o ../obj_s/name_match.o ../obj_s/names.o ../obj_s/obsolete.o ../obj_s/read_entry.o ../obj_s/read_termcap.o ../obj_s/strings.o ../obj_s/tries.o ../obj_s/trim_sgr0.o ../obj_s/unctrl.o ../obj_s/visbuf.o ../obj_s/alloc_entry.o ../obj_s/captoinfo.o ../obj_s/comp_expand.o ../obj_s/comp_parse.o ../obj_s/comp_scan.o ../obj_s/parse_entry.o ../obj_s/write_entry.o ../obj_s/define_key.o ../obj_s/hashed_db.o ../obj_s/key_defined.o ../obj_s/keybound.o ../obj_s
