[sage-devel] Re: proposed amendment to code of conduct
On Friday, November 28, 2014 4:58:35 PM UTC, Dima Pasechnik wrote: > > > Let me try a last time, just replace code with book: > If you want to understand how I feel about that name, add > to that doc a subtitle "Mein Kampf" :-) > How about "Godwin's Law": http://en.wikipedia.org/wiki/Godwin%27s_law -- 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: proposed amendment to code of conduct
On Sat, Nov 29, 2014 at 06:09:44AM +0100, Thierry wrote: > OK, sorry if i misunderstood, you seemed to support a vote about that > (even proposing a third alternative name) since your message was: A *poll*, not a *vote*. A poll sounds useful to get a sense of where the community stands to know better in which direction to work toward a consensus. > Some people were opposed to the existence of such a text (i was not > in the absolute, see the beginning of my first e-mail), and this > should be acknowledged, even if those people did not insist (there > are still interesting bits in there). Sure, one should reach toward those people, see how strong their feelings are (is it more than "don't see the point" or "oh well, as long as it's not strict laws"?), etc. > Well, i precisely would like no one to take the lead (nor a small > subgroup as just happened). For me the correct way is the way we > will decide together. Of course i will participate to such > discussion, but i do not plan to impose anything, this would be > inconsistent. Leading is not about taking the decisions, but about organizing the decision process, by the community, for the community. Having people move forward by creating wiki pages, calling for feedback, etc is useful, if not necessary. > > [1] Yes, I am kindly teasing you a bit here :-) > > Tes grands airs de ces derniers temps m'ont un peu agacé ... > > Si tu veux faire une remarque (pas particulierement "kindly") en francais > sur une mailing-liste comme si c'etait un message prive, tu connais mon > adresse mail (non, je ne me refererai pas au code de conduite). Ceci-dit, > ca tombe bien, c'etait le but. Pour info, devoir tirer l'alarme comme je > l'ai fait n'est pas agreable et n'amene que des ennemis (la preuve?), il > m'aurait ete plus facile de rester au chaud quand les tuiles volent bas. Back to English. My comment was not meant to be private. I put it in French for the simple reason that I did not find the right wording in English. I am grateful, really, that you went ahead and pointed potential risks and suggested better ways to proceed. Indeed you took a risk in doing so. Others did too. That being said, I did find the tone not particularly "kindly" and was hurt by it. I allowed myself, in a single line and half jokingly, to use a similar tone. I let you judge on the effect. End of the parenthesis; what had to be said has been said, we can move on (or if you believe it's useful to discuss this a bit further, we should indeed do that privately). Amitiés, Nicolas -- Nicolas M. Thiéry "Isil" http://Nicolas.Thiery.name/ -- 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: proposed amendment to code of conduct
On Fri, Nov 28, 2014 at 07:18:26PM +, Simon King wrote: > If I understand correctly what William and Volker are saying, they claim > it is too late for a change anyway, Please reread. William has explicitly, and in several emails, stated the converse. Cheers, Nicolas -- Nicolas M. Thiéry "Isil" http://Nicolas.Thiery.name/ -- 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] The "code of conduct" is getting out of hand - please stop for 2 weeks.
Discussions on this are not going in a positive direction. The tone of the discussions is far worst than anything I have seen on here in a long time. I think it would be best if everyone stopped discussing it for a couple of weeks, and revisited it later (I propose Monday the 15th December). Maybe if people stop for a while, it will cool the discussions, and perhaps they can more forward in a positive direction. Since at the minute, the whole thing is getting quite nasty. 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] The "code of conduct" is getting out of hand - please stop for 2 weeks.
On 29 November 2014 at 11:58, Dr. David Kirkby (Kirkby Microwave Ltd) wrote: > Discussions on this are not going in a positive direction. The tone of > the discussions is far worst than anything I have seen on here in a > long time. I entirely agree. This has been worse than anything which has been on Sage-devel since I joined it in 2007. I have just downgraded to daily email summaries. Anyone new considering to contribute to Sage who read the content of sage-devel over the last 2 weeks would surely run a mile. John > > I think it would be best if everyone stopped discussing it for a > couple of weeks, and revisited it later (I propose Monday the 15th > December). > > Maybe if people stop for a while, it will cool the discussions, and > perhaps they can more forward in a positive direction. Since at the > minute, the whole thing is getting quite nasty. > > 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. -- 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: The "code of conduct" is getting out of hand - please stop for 2 weeks.
Hi David, hi John, On 2014-11-29, John Cremona wrote: > On 29 November 2014 at 11:58, Dr. David Kirkby (Kirkby Microwave Ltd) > wrote: >> Discussions on this are not going in a positive direction. The tone of >> the discussions is far worst than anything I have seen on here in a >> long time. > > I entirely agree. This has been worse than anything which has been on > Sage-devel since I joined it in 2007. I agree too (even though I guess I was one of the people keeping the discussion running). I planned to not reply to any post till Monday (making an exception now), thinking the whole thing was the worst happening to Sage since William suggested to rewrite Sage in lisp (which fortunately happened on April 1st). See you not before Monday, Simon -- 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] The "code of conduct" is getting out of hand - please stop for 2 weeks.
Hi, +1 Thanks for this proposition, i definitely agree with that (though i was part of the mess), and i will not post on this subject on sage-devel for the next two weeks. Mailing-list (which require quick response) seems not the appropriate format to discuss such issues. Ciao, Thierry On Sat, Nov 29, 2014 at 11:58:29AM +, Dr. David Kirkby (Kirkby Microwave Ltd) wrote: > Discussions on this are not going in a positive direction. The tone of > the discussions is far worst than anything I have seen on here in a > long time. > > I think it would be best if everyone stopped discussing it for a > couple of weeks, and revisited it later (I propose Monday the 15th > December). > > Maybe if people stop for a while, it will cool the discussions, and > perhaps they can more forward in a positive direction. Since at the > minute, the whole thing is getting quite nasty. > > 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. > > -- 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: proposed amendment to code of conduct
Hi, On Sat, Nov 29, 2014 at 12:40:16PM +0100, Nicolas M. Thiery wrote: > On Sat, Nov 29, 2014 at 06:09:44AM +0100, Thierry wrote: > > OK, sorry if i misunderstood, you seemed to support a vote about that > > (even proposing a third alternative name) since your message was: > > A *poll*, not a *vote*. A poll sounds useful to get a sense of where > the community stands to know better in which direction to work toward > a consensus. OK, my bad, my reference in reading english is http://www.wordreference.com/enfr/poll which seems to give a polysemous definition (vote, survey of opinions (indeed!), election). > Leading is not about taking the decisions, but about organizing the > decision process, by the community, for the community. Having people > move forward by creating wiki pages, calling for feedback, etc is > useful, if not necessary. If a single person (or a small group) organizes the decision process for the community, then it is not by the community. I think this organizational task is also a collective task (this prevents situations like the one that is happening), hence i would not call that leading (if i still trust the on-line dictionary). Everybody should feel the right (perhaps even the duty) of doing such collective organization tasks, for example i opposed the way the text was written to the fact of opening an empty page on the wiki, but then Vincent opened it as anybody could have done, and i hope anybody can contribute, not only in giving feedback or fill existing wiki pages, but also in calling for feedback and creating wiki pages (or any kind of organization task). I guess we agree on that point, but i wanted to make it clear, i do not see any particularity of organization compared to other tasks, this is not a reserved area. Ciao, Thierry -- 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: The "code of conduct" is getting out of hand - please stop for 2 weeks.
On 11/29/14, 6:58, Dr. David Kirkby (Kirkby Microwave Ltd) wrote: Discussions on this are not going in a positive direction. The tone of the discussions is far worst than anything I have seen on here in a long time. I think it would be best if everyone stopped discussing it for a couple of weeks, and revisited it later (I propose Monday the 15th December). Maybe if people stop for a while, it will cool the discussions, and perhaps they can more forward in a positive direction. Since at the minute, the whole thing is getting quite nasty. +1. While I've been reading the whole discussion, I've stayed out of it because of the direction, emotion, and tone of it. I think this is the first suggestion I wholeheartedly vote +1 on. 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: The "code of conduct" is getting out of hand - please stop for 2 weeks.
+1 As already said in an other thread: I don't understand this high waves of emotion, and I don't think it is healthy for the community -- 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: The "code of conduct" is getting out of hand - please stop for 2 weeks.
The irony of this is staggering, if not surprising. +1 -- 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: The "code of conduct" is getting out of hand - please stop for 2 weeks.
On 2014-11-29, Tom Boothby wrote: > The irony of this is staggering, if not surprising. +1 "Gentlemen! You can't fight in here -- this is the War Room." quotably, Robert Dodier -- 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: sage-6.4 fallout: the normaliz package is now broken
On Tue, Nov 18, 2014 at 5:53 AM, Dima Pasechnik wrote: > On 2014-11-15, William Stein wrote: >> Hi, >> >> I guess the upgrade to patch broke more optional packages: >> >> sage -i normaliz >> ... >> >> gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) >> >> patching file source/Makefile.configuration >> (Stripping trailing CRs from patch; use --binary to disable.) >> patching file Singular/normaliz.lib >> Hunk #1 FAILED at 1371 (different line endings). >> 1 out of 1 hunk FAILED -- saving rejects to file Singular/normaliz.lib.rej >> Error: Couldn't apply patch. >> >> real0m0.010s >> user0m0.005s >> sys 0m0.005s >> >> Error installing package normaliz-2.8.p0 > > OK, I'll try updating normaliz to the current version (2.12.1). Ping -- still broken after 11 days... -- William -- William Stein Professor of Mathematics University of Washington 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] Compilation Error sage 6.4.1 : installing package ecl-13.5.1.p0
Hi, i did the compilation in a folder with only ascii caracters and it worked. Thank you for your help. Patxi Le mercredi 26 novembre 2014 21:17:27 UTC+1, François a écrit : > > Hi, > > A bit of a shot in the dark but could you try it from a folder with > only ascii characters? "Telechargements" instead of "Téléchargement". > It is possible that the ecl bootstrap doesn't like those characters > very much. > > Francois > > On Wed, 26 Nov 2014 10:58:31 Patxi Laborde Zubieta wrote: > > Hi, > > > > i tried to instal Sage on my computer by compiling the source, but it > > didn't work. > > To do that, i followed the instructions given in the webpage : > > http://www.sagemath.org/download-source.html > > > > Tell me if you need more information about my computer : > > > cat /proc/version > > > Linux version 3.16.0-25-generic (buildd@komainu) (gcc version 4.9.1 > > > (Ubuntu 4.9.1-16ubuntu6) ) #33-Ubuntu SMP Tue Nov 4 12:06:54 UTC 2014 > > > uname -a > > > Linux patxi-HP-EliteBook-820-G1 3.16.0-25-generic #33-Ubuntu SMP Tue > Nov 4 > > > 12:06:54 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux > > > OS : Ubuntu 14.10 > > > > The log file is attached to the discussion (i don't know if it's the > right > > word). > > The end of the log file : > > > > if [ -f CROSS-COMPILER ]; then \ > > > > > ./CROSS-COMPILER compile; \ > > > > > > else \ > > > > > > ECLDIR=`pwd`/ ./ecl_min compile; \ > > > > > > fi > > > > > > ;*** Lisp core booted > > > > > > ECL (Embeddable Common Lisp) > > > > > >> ;;; > > > > > > ;;; Welcome to bare.lsp. Let's bring this instance up! > > > > > > ;;; > > > > > > ;;; > > > > > > ;;; About to load lsp/load.lsp > > > > > > ;;; > > > > > > ;;; Loading src:lsp;export.lsp > > > > > > ;;; Unhandled lisp initialization error > > > > > > ;;; Message: > > > > > > FILE-ERROR > > > > > > ;;; Arguments: > > >> Internal or unrecoverable error in: > > >> > > >> > > >> Lisp initialization error. > > >> > > >> [2: No such file or directory] > > >> > > >> ;;; ECL C Backtrace > > > > > > ;;; ./ecl_min() [0x442726] > > > > > > ;;; ./ecl_min() [0x42daaf] > > > > > > ;;; ./ecl_min() [0x42dc04] > > > > > > ;;; ./ecl_min() [0x40f880] > > > > > > ;;; ./ecl_min() [0x42ea1b] > > > > > > ;;; ./ecl_min() [0x42eb02] > > > > > > ;;; ./ecl_min() [0x42eb2e] > > > > > > ;;; ./ecl_min() [0x420f17] > > > > > > ;;; ./ecl_min() [0x421773] > > > > > > ;;; ./ecl_min() [0x440b4b] > > > > > > ;;; ./ecl_min() [0x441043] > > > > > > ;;; ./ecl_min() [0x4402e5] > > > > > > ;;; ./ecl_min() [0x42dbeb] > > > > > > ;;; ./ecl_min() [0x40f880] > > > > > > ;;; ./ecl_min() [0x42ea1b] > > > > > > ;;; ./ecl_min() [0x42ea68] > > > > > > ;;; ./ecl_min() [0x4628b6] > > > > > > ;;; ./ecl_min() [0x411df3] > > > > > > ;;; ./ecl_min() [0x415ed5] > > > > > > ;;; ./ecl_min() [0x41867d] > > > > > > ;;; ./ecl_min() [0x461d67] > > > > > > ;;; ./ecl_min() [0x40f880] > > > > > > ;;; ./ecl_min() [0x46238f] > > > > > > ;;; ./ecl_min() [0x411df3] > > > > > > ;;; ./ecl_min() [0x415ed5] > > > > > > ;;; ./ecl_min() [0x41867d] > > > > > > ;;; ./ecl_min() [0x461d67] > > > > > > ;;; ./ecl_min() [0x40f880] > > > > > > ;;; ./ecl_min() [0x46238f] > > > > > > ;;; ./ecl_min() [0x411df3] > > > > > > ;;; ./ecl_min() [0x415ed5] > > > > > > ;;; ./ecl_min() [0x41867d] > > > > > > /bin/bash: line 4: 1086 Aborted (core dumped) > > > > > >> ECLDIR=`pwd`/ ./ecl_min compile > > > > > > Makefile:72: recipe for target 'bin/ecl' failed > > > > > > make[4]: *** [bin/ecl] Error 134 > > > > > > make[4]: Leaving directory > > > > > >> > '/home/patxi/Téléchargements/sage-6.4.1/local/var/tmp/sage/build/ecl-13.5 > > >> .1.p0/src/build'> > > > Makefile:70: recipe for target 'all' failed > > > > > > make[3]: *** [all] Error 2 > > > > > > make[3]: Leaving directory > > > > > >> > '/home/patxi/Téléchargements/sage-6.4.1/local/var/tmp/sage/build/ecl-13.5 > > >> .1.p0/src'> > > > Error - Failed to build ECL ... exiting > > -- 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] Compilation Error sage 6.4.1 : installing package ecl-13.5.1.p0
Hi, i did as you said and it worked. Thank you for your help. Patxi. > -- 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: proposed amendment to code of conduct
On 2014-11-29, Volker Braun wrote: > --=_Part_66_1749519742.1417259350569 > Content-Type: multipart/alternative; > boundary="=_Part_67_832209070.1417259350569" > > --=_Part_67_832209070.1417259350569 > Content-Type: text/plain; charset=UTF-8 > > On Friday, November 28, 2014 4:58:35 PM UTC, Dima Pasechnik wrote: >> >> > Let me try a last time, just replace code with book: >> If you want to understand how I feel about that name, add >> to that doc a subtitle "Mein Kampf" :-) >> > > How about "Godwin's Law": http://en.wikipedia.org/wiki/Godwin%27s_law Well, sorry, you were first talking about "cultural baggage", not me, when I was saying that I personally am quite upset about that doc, and you seemed to be unable to understand why this can be the case, from merely "cultural baggage" alone. The fact is that "cultural baggage" can be as tabu as the one Godwin was making fun about. > -- 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] BUG IN COMPILE
hi, 6.3 complies ok but 6.4 dose not! cd /home/sageserver/sage-6.4/local/var/tmp/sage/build/pynac-0.3.2 and autoreconf -i --force checking for python... /home/sageserver/sage-6.4/local/bin/python checking for a version of Python >= '2.1.0'... sys:1: RuntimeWarning: not adding directory '' to sys.path since it's writable by an untrusted group. Untrusted users could put files in this directory which might then be imported by your Python code. As a general precaution from similar exploits, you should not execute Python code from this directory yes checking for the distutils Python package... no configure: error: cannot import Python module "distutils". Please check your Python installation. The error was: sys:1: RuntimeWarning: not adding directory '' to sys.path since it's writable by an untrusted group. Untrusted users could put files in this directory which might then be imported by your Python code. As a general precaution from similar exploits, you should not execute Python code from this directory (sage-sh) root@mpi1:src$ === Error installing package pynac-0.3.2 Please email sage-devel (http://groups.google.com/group/sage-devel) explaining the problem and including the relevant part of the log file /home/sageserver/sage-6.4/logs/pkgs/pynac-0.3.2.log Describe your computer, operating system, etc. If you want to try to fix the problem yourself, *don't* just cd to /home/sageserver/sage-6.4/local/var/tmp/sage/build/pynac-0.3.2 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/sageserver/sage-6.4/local/var/tmp/sage/build/pynac-0.3.2' && '/home/sageserver/sage-6.4/sage' --sh) When you are done debugging, you can type "exit" to leave the subshell. make[2]: *** [/home/sageserver/sage-6.4/local/var/lib/sage/installed/pynac-0.3.2] Error 1 make[2]: Leaving directory `/home/sageserver/sage-6.4/build' make[1]: *** [all] Error 2 make[1]: Leaving directory `/home/sageserver/sage-6.4/build' real0m1.792s user0m0.672s sys0m0.873s *** Error building Sage. The following package(s) may have failed to build: package: pynac-0.3.2 log file: /home/sageserver/sage-6.4/logs/pkgs/pynac-0.3.2.log build directory: /home/sageserver/sage-6.4/local/var/tmp/sage/build/pynac-0.3.2 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. make: *** [build] Error 1 -- 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] BUG IN COMPILE
2014-11-29 20:30 GMT+00:00 Joni-Pekka Kurronen : ... > (sage-sh) root@mpi1:src$ ... Are you compiling as root? Try compiling as a non-root user; Python refuses some things when run as root as a security precaution. Regards, Erik Massop -- 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.
