Re: [sage-support] Re: Sage Crash Report

This is an ABI incompatibility with clang 14 and 15 where givaro was compiled with 14 and sage was compiled with 15. I suggest downgrading to clang 14 or set flags like https://github.com/conda-forge/sagelib-feedstock/blob/5542b278f642b772ae243b323c7cbc7a170a5f9a/recipe/build.sh#L21-L25 until we

Re: [sage-support] Re: Sage crash report

Now, at the *end* of a Sage session, I get : sage: quit Exiting Sage (CPU time 0m5.63s, Wall time 97m53.10s).

Re: [sage-support] Re: Sage crash report

make giac-clean && make did it ! (*Alla cinese*) 10^4 thanks ! ​ Le vendredi 10 décembre 2021 à 11:56:00 UTC+1, dim...@gmail.com a écrit : > Everything that depends on updated Debian libs has to be rebuilt - looks > like > > make giac-clean > > is needed too, for sure. > > On Fri, Dec 10,

Re: [sage-support] Re: Sage crash report

Everything that depends on updated Debian libs has to be rebuilt - looks like make giac-clean is needed too, for sure. On Fri, Dec 10, 2021 at 10:36 AM Emmanuel Charpentier wrote: > > > > Le vendredi 10 décembre 2021 à 01:04:33 UTC+1, Matthias Koeppe a écrit : >> >> "make sagelib-clean" will

Re: [sage-support] Re: Sage Crash Report: Missing symbols in conda build for macOS?

That works! Similarly conda install -n sage "pynac=0.7.26=py36ha01bd41_0" works for my python 3.6 attempt. I see that you've already opened an issue on pynac-feedstock, so I'll leave you to it. Thanks very much for you help! -- You received this message because you are subscribed to the

Re: [sage-support] Re: Sage Crash Report: Missing symbols in conda build for macOS?

Hi, Can you try doing the following? conda install -n sage27 "pynac=0.7.26=py27ha01bd41_0" Isuru On Tue, Nov 19, 2019 at 11:23 AM Michael Boyle < michael.oliver.bo...@gmail.com> wrote: > Sure. Here it is: > > > conda list > # packages in environment at >

Re: [sage-support] Re: Sage crash report

Дмитрий, спасибо огромное. Установка python2-cypari2 решила проблему. Пишу Вам по-русски, потому что слышал Ваше имя раньше. Добрый вечер. Максим. -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop

Re: [sage-support] Re: Sage Crash Report

On Tuesday, August 15, 2017 at 9:49:35 PM UTC-7, William wrote: > On Tue, Aug 15, 2017 at 7:47 PM John H Palmieri wrote: > >> One of the very last lines of the report says >> >>> ImportError: libgfortran.so.3: cannot open shared object file: No such file or directory >> >> You need to install

Re: [sage-support] Re: Sage Crash Report

On Tuesday, August 15, 2017 at 9:49:35 PM UTC-7, William wrote: > > On Tue, Aug 15, 2017 at 7:47 PM John H Palmieri > wrote: > >> One of the very last lines of the report says >> >>> >>> ImportError: libgfortran.so.3: cannot open shared object file: No such file >>> or

Re: [sage-support] Re: Sage Crash Report

On Tue, Aug 15, 2017 at 7:47 PM John H Palmieri wrote: > One of the very last lines of the report says > >> >> ImportError: libgfortran.so.3: cannot open shared object file: No such file >> or directory >> >> > You need to install gfortran on your computer. > We should

Re: [sage-support] Re: Sage Crash Report

Thanks! Grant On Jul 18, 2017 9:29 AM, "Dima Pasechnik" wrote: > You need to have (lib)gfortran installed, see the bottom of your log: > > ImportError: libgfortran.so.3: cannot open shared object file: No such file > or directory > > > On Tuesday, July 18, 2017 at 9:49:40 AM

Re: [sage-support] Re: Sage Crash Report. appears to have loaded, failed to run.

On Wed, Mar 8, 2017 at 6:56 AM, John H Palmieri wrote: > Just about the last line in your crash report says > >ImportError: libgfortran.so.3: cannot open shared object file: No such > file or directory > > So you need to install gfortran, however that is done with

Re: [sage-support] Re: Sage crash report 7.0

On Wednesday, December 14, 2016 at 3:44:19 PM UTC, NITIN DARKUNDE wrote: > > Hello, I have some old version of sage installed two years ago on my > laptop. Also some worksheets are saved on it. How to upgrade it to latest > 7.4 version? Whether old saved worksheets will remain saved? or get

Re: [sage-support] Re: Sage crash report 7.0

Hello, I have some old version of sage installed two years ago on my laptop. Also some worksheets are saved on it. How to upgrade it to latest 7.4 version? Whether old saved worksheets will remain saved? or get deleted? On Dec 14, 2016 9:08 PM, "Dima Pasechnik" wrote: Is

Re: [sage-support] Re: Sage Crash Report

Your welcome... I like very much this tool because it works fine and is well documented :) I wanted to translate examples but it's too much work, and I guess all people using it are knowing english ! Better original language than a bad translation ! Henri Le 01/04/2016 14:55, Oscar Alberto

Re: [sage-support] Re: Sage Crash Report

Thank you HG, Your suggestion worked like a charm. I create a new branch in my sage installation and tried your suggestion, and it works smoothly. Best wishes! Oscar. On Thursday, 31 March 2016 14:56:08 UTC-3, HG wrote: > > sagemanifolds compiles well usually... Just follow the install doc and

Re: [sage-support] Re: Sage Crash Report

sagemanifolds compiles well usually... Just follow the install doc and sm-install.sh : http://sagemanifolds.obspm.fr/download.html#script_install/sm-install.sh I prefer than git. Le 31/03/2016 19:00, Oscar Alberto Castillo Felisola a écrit : Hi Eric, I finally compiled the source of sage

Re: [sage-support] Re: Sage crash report

ipython was get install as dependancy. I have installed sage via dnf using fedora repository. Currently I am Using fedora 22. If I configure and compile sage from source will this error rectify? On 22 September 2015 at 01:27, Dima Pasechnik wrote: > looks like another install

Re: [sage-support] Re: Sage Crash Report

Hi Doaa, Are you running Ubuntu and the PPA Sage install like I showed you? I'd be interested in the output of those commands in case the packaged caused a problem. You can fix this, after you ran the commands, with sudo chown -R doaa:doaa /home/doaa/.sage Regards, Jan On 10 April 2013

Re: [sage-support] Re: Sage Crash Report

Hi, This is the output for the commands doaa@doaa-XPS-L412Z:~$ ls -l /home/doaa/.sage/cache total 8 -rw--- 1 doaa doaa 6 Nov 28 22:12 _usr_lib_sage_devel_sage-main-lazy_import_cache.pickle -rw--- 1 root root 6 Mar 18 20:51 _usr_lib_sagemath_devel_sage-main-lazy_import_cache.pickle

Re: [sage-support] Re: Sage Crash Report

Hi Doaa, The file owned (incorrectly) by root is -rw--- 1 root root 6 Mar 18 20:51 _usr_lib_sagemath_devel_sage-main-lazy_import_cache.pickle Were you busy doing a package upgrade of sage on 18 March at 20:51 ? PS. You can fix this with sudo chown -R doaa.doaa /home/doaa/.sage/cache

Re: [sage-support] Re: Sage Crash Report

Thanks Jan It works now :) On 10 April 2013 09:18, Jan Groenewald j...@aims.ac.za wrote: Hi Doaa, The file owned (incorrectly) by root is -rw--- 1 root root 6 Mar 18 20:51 _usr_lib_sagemath_devel_sage-main-lazy_import_cache.pickle Were you busy doing a package upgrade of sage on 18

Re: [sage-support] Re: Sage Crash Report

Do you remember doing a sage package upgrade at the time I asked? On 10 April 2013 10:28, Doaa El-Sakout d...@aims.ac.za wrote: Thanks Jan It works now :) On 10 April 2013 09:18, Jan Groenewald j...@aims.ac.za wrote: Hi Doaa, The file owned (incorrectly) by root is -rw--- 1 root

Re: [sage-support] Re: Sage Crash Report - Sagecell2 in sage-5.4.rc1

Sage 5.4.rc4 and documentation build fine on a fresh install of Ubuntu 12.10 x64, and Sage Cell Server installs and runs without issue from the above sagecell-2012-11-06.spkg following the same instructions that were successful for sage-5.4.rc3: http://pastebin.com/xQNgiZxQ make ptestlong throws

Re: [sage-support] Re: Sage Crash Report - Sagecell2 in sage-5.4.rc1

On Sat, Nov 3, 2012 at 4:09 PM, Jason Grout jason-s...@creativetrax.comwrote: On 11/3/12 5:06 PM, Brandon Curtis wrote: The proper thing to do is to make a fork on github, push your changes there, and submit a pull request [1]. I'll probably start compiling rc3 and test your changes

Re: [sage-support] Re: Sage Crash Report - Sagecell2 in sage-5.4.rc1

Upon closer observation, two of the listed patches appear to fail: === *./sage --hg -R devel/sage qimport -P http://trac.sagemath.org/sage_trac/raw-attachment/ticket/12719/trac_12719-move_to_preparser_rebased.patch * adding

Re: [sage-support] Re: Sage Crash Report - Sagecell2 in sage-5.4.rc1

This patch [1] always fails when applied to sage-5.4.rc1 compiled from source on Ubuntu 12.04/12.10. I was able to get the Sage Cell Server to install by learning enough about the Mercurial mq patch system to manually apply the changes from the broken patch [1] in a new patch, 'bc_patch_01'. Here

Re: [sage-support] Re: Sage Crash Report - Sagecell2 in sage-5.4.rc1

This: var('x y') y = x^3 show(y) plot(y,x,(-2,2)) Yielded this error: http://pastebin.com/ApVQeY6Q And here is sagecell.log: http://pastebin.com/GDv7FG17 * Brandon Curtis, PhD Candidate UC Berkeley - Chem/Bio Eng http://www.linkedin.com/in/brandoncurtis