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

[sage-support] Re: Sage Crash Report

I am focusing on the Sage 9.8 issue of the missing symbol __ZN6FFPACK8CharPolyIN6Givaro8Poly1DomINS1_7ModularIddvEENS1_5DenseERNT_7ElementERKS7_S9_mNS7_8Domain_t11Element_ptrEmRNSC_8RandIterENS_19FFPACK_CHARPOLY_TAGEm Demangled with c++filt, the missing symbol is: Givaro::Poly1Dom,

[sage-support] Re: Sage Crash Report

Sorry for the late reply. Here are the details about my conda environment. I am not exactly sure what other information is useful to debug this. I am familiar with the linux tools, but am struggling with otool and vmmap to figure out what is going on here and see whether I am picking up any

[sage-support] Re: Sage Crash Report

config.log please On Wednesday, May 24, 2023 at 3:16:25 PM UTC-7 Matthias Goerner wrote: > Hi! > > I can't get sage to work when installing it with conda on a new MacBook > Pro with M2 chip and Ventura 13.3. > > I tried > conda -n sage create sage=9.X python=3.Y > for (X,Y) = (5,10), (8,10),

[sage-support] Re: Sage Crash Report

9.7 with python 3.10 seems to work on Ventura 13.3 on a M2. On Wed, May 24, 2023 at 3:16 PM Matthias Goerner wrote: > Hi! > > I can't get sage to work when installing it with conda on a new MacBook > Pro with M2 chip and Ventura 13.3. > > I tried > conda -n sage create sage=9.X python=3.Y > for

[sage-support] Re: Sage Crash Report

That was the problem. I copy the files and now everything works. Many thanks for spotting the problem. On Saturday, 30 July 2022 at 15:25:54 UTC+2 Marc Culler wrote: > The reason it works for one user and not for the other is because > libgsl.25.dylib > exists within one

[sage-support] Re: Sage Crash Report

The reason it works for one user and not for the other is because libgsl.25.dylib exists within one user's.conda/envs/sage/lib directory but it does not exist within the other user's .conda/envs/sage/lib directory. On Saturday, July 30, 2022 at 4:53:36 AM UTC-5 domingo.domingogo...@gmail.com

[sage-support] Re: Sage Crash Report. -- help please !

Hi, Thank you, everyone. Sorry for my late response: I wasn't sure how things worked and I hadn't realized that I needed to check the google groups page. I managed to install Sage on my laptop, but I am not really sure what worked. It was just a lot of trial and error and going through the

[sage-support] Re: Sage Crash Report. -- help please !

In case this problem has not been addressed ... at the bottom of your crash report it says: '/usr/lib/libgfortran.5.dylib' (no such file) That means that you are using an early prelease version of the SageMath app for M1 systems. This problem was fixed in the release version. So just

[sage-support] Re: Sage Crash Report. -- help please !

2022-02-16, 02:43:20 UTC, Bharathwaj Palvannan: > I had already sent a crash report some weeks ago > but I received no response. This question of yours from 2017 was not answered: https://groups.google.com/g/sage-support/c/0dgWgFGxYQU (hopefully you managed to solve that problem since then?)

[sage-support] Re: Sage Crash report (again...)

I’m in trouble: The previous steps (make giac-clean && make fricas-clean && make sagelib-clean && make) failed ; I reverted to (make distclean && make) … which failed. Repeatedly… I’ll report and post logs in sage-release, which seems te “right place” for an installation problem occurring

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

[sage-support] Re: Sage crash report

Le vendredi 10 décembre 2021 à 01:04:33 UTC+1, Matthias Koeppe a écrit : > "make sagelib-clean" will fix this > Nope. `make sagelib-clean` succeeds, but the following `make` fails at documentation ; attempting `make doc-clean && make also fails, *with the very same error*... : ```

[sage-support] Re: Sage crash report

"make sagelib-clean" will fix this On Thursday, December 9, 2021 at 12:18:02 PM UTC-8 Emmanuel Charpentier wrote: > A recent upgrade of Debian testing seems to have broken Sage, which does > not find libgsl.so.25 Crash report attached. > > An attempt at make -b also fails (see attached

[sage-support] Re: Sage Crash Report

I solved the problem. I think the blender ppa came with a strange version of libgivaro9 and libgivaro-dev. I downgraded them and reinstalled Sage. Now it works! Blender also seems to work! Best, G Le 16/08/2021 à 17:08, Gaël Cousin a écrit : Ubuntu 20.04 Focal Fossa Dear all, Here

[sage-support] Re: Sage Crash Report

Glad I can help. This is another reason why these virtual environments are really useful! I have one environment for sage which I never try to update since I know that everything works. Separately, I have my "main" environment that I update regularly, which will occasionally break things. I

[sage-support] Re: Sage Crash Report

ad. 1. It turned out that indeed I had installed the most recent version of jedi. Installing 0.17.2 fixed the problem - thank you very much! ad. 2. I see - I am new to conda and I only used it to install sage; thanks for your explanation. On Monday, January 4, 2021 at 6:38:01 PM UTC+1

[sage-support] Re: Sage Crash Report

1. Did you by any chance accidentally update the jedi package? This is not really a sage problem, but ipython 7.19.0 is incompatible with the most recent version of jedi 0.18.0. In your sage environment you can run "conda list" to see what packages you have installed. If jedi 0.18.0 is

[sage-support] Re: Sage Crash Report: `TypeError` upon startup (Sage 9.0.0)

Problems with the Ubuntu packaging should be reported as an Ubuntu bug. On Sunday, August 2, 2020 at 11:31:57 PM UTC-7, Samuel Tang wrote: > > Hi, > > Thanks for your quick response. I am running on Ubuntu 20.04, and > installed Sagemath via `sudo apt-get install sagemath`. > From what I

[sage-support] Re: Sage Crash Report: `TypeError` upon startup (Sage 9.0.0)

Hi, Thanks for your quick response. I am running on Ubuntu 20.04, and installed Sagemath via `sudo apt-get install sagemath`. >From what I recorded, it was Sage 9.0 on Python 3.8.2 since I've installed Ubuntu (in early July The version are consistent on Sage and Python when I referred just

[sage-support] Re: Sage Crash Report: `TypeError` upon startup (Sage 9.0.0)

Le lundi 3 août 2020 05:31:01 UTC+2, Samuel Tang a écrit : > > Hi team, > > This issue happened to me just one day ago. > > I am aware of https://trac.sagemath.org/ticket/18492 and > https://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg1671690.html > as they have the same TypeError,

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 >

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

Sure. Here it is: > conda list # packages in environment at /Users/myusername/.continuum/miniconda3.7/envs/sage27: # # NameVersion Build Channel _r-mutex 1.0.1 anacondar_1conda-forge alabaster 0.7.12

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

Hi Micheal, could you share the output of `conda list` for that environment? Feel free to open an issue for this at https://github.com/conda-forge/sage-feedstock/issues as well. julian On Tuesday, November 19, 2019 at 6:04:23 PM UTC+1, Michael Boyle wrote: > > I followed the installation

[sage-support] Re: Sage Crash Report

your reports says at the end: ImportError: /home/katsu95i/anaconda3/lib/python3.6/site-packages/sage/matrix/../../../../libgd.so.3: undefined symbol: libiconv do you have libiconv installed? If not, it's a missing dependence in the conda build, so you can install it, and then sage should

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

[sage-support] Re: Sage crash report

On Sunday, August 26, 2018 at 12:51:28 PM UTC+2, Maxim Leyenson wrote: > > Dear friends, > > I would appreciate help with the following crash report (in the > attachment) > > a few details: > > * first run of Sage; > > * System: Fedora 28, 64 bit > > * Sage source: Fedora repository, >

[sage-support] Re: Sage Crash Report

Sat 2018-03-10 11:29:34 UTC, Alasdair: > > As created just now. Enjoy! > > -Alasdair > > -- > facebook twitter wordpress linkedin google+ What is the operating system, and what version of it? How was Sage installed? What led to the crash? The crash report ends with this piece of information:

[sage-support] Re: Sage Crash Report

Yeah, I traced it to my .bash_aliases file and commented it out so it won't be causing me any more problems. On Tuesday, February 20, 2018 at 5:42:16 PM UTC-5, Dima Pasechnik wrote: > > > > On Tuesday, February 20, 2018 at 7:26:25 PM UTC, Dillon Ethier wrote: >> >> Alright, I unset

[sage-support] Re: Sage Crash Report

On Tuesday, February 20, 2018 at 7:26:25 PM UTC, Dillon Ethier wrote: > > Alright, I unset LD_LIBRARY_PATH and changed PATH to > /usr/sbin:/usr/bin:/sbin:/bin:/ then rebuilt it, and it worked. I reran the > tests and only one doctest failed. To check, I rebooted and tried again, > causing a

[sage-support] Re: Sage Crash Report

Alright, I unset LD_LIBRARY_PATH and changed PATH to /usr/sbin:/usr/bin:/sbin:/bin:/ then rebuilt it, and it worked. I reran the tests and only one doctest failed. To check, I rebooted and tried again, causing a crash. But LD_LIBRARY_PATH and PATH had reinitialized to their previous values. I

[sage-support] Re: Sage Crash Report

I bet you have stuff in /usr/local/lib (to which your LD_LIBRARY_PATH is pointing to) that is problematic. Unset it and try again. Also, I'd remove /usr/local/* things from the PATH On Tuesday, February 20, 2018 at 4:11:16 PM UTC, Dillon Ethier wrote: > > I uninstalled Anaconda completely and I

[sage-support] Re: Sage Crash Report

I uninstalled Anaconda completely and I can't find any relevent vars sticking around but the problem persists. This is the output of 'env': CLUTTER_IM_MODULE=xim LC_ALL=en_US.UTF-8 LD_LIBRARY_PATH=.:/usr/local/lib

[sage-support] Re: Sage Crash Report

most probably you have a conflict with Anaconda installation. Unset all the relevant to Anaconda env. vars before rebuilding Sage. -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from

[sage-support] Re: Sage Crash Report

Initially I had never set the SAGE_ROOT variable or any of the build variables other than MAKE, and it worked fine. I only changed it afterward in order to get Jupyter(anaconda) to recognize the kernel. I have tried setting SAGE_ROOT to be /home/dillon/sage-8.1 and rebuilding but the problem

[sage-support] Re: Sage Crash Report

Your log says that your Sage installation is in /home/dillon/sage-8.1 I guess you might want to set it as SAGE_ROOT On Monday, February 19, 2018 at 3:25:04 AM UTC, Dillon Ethier wrote: > > Hello, > > I recently built Sage on my laptop running Ubuntu 17.10 (x86 - 64 bit). It > worked perfectly,

[sage-support] Re: Sage Crash Report

Looks like you used the Sage binary on Fedora 25; That apparently won't work and you need a more recent Fedora version. As a side note: Fedora 25 is EOL, so no more security fixes etc... On Friday, December 29, 2017 at 4:15:09 AM UTC+1, rj wrote: > > > > IPython post-mortem report > >

[sage-support] Re: Sage Crash Report

Hi Dima, On 2017-10-23, Dima Pasechnik wrote: >> ... which means that we should enhance our crash message (if there is any; >> I don't recall what I saw when Sage last crashed for me). >> > if you like to refresh your experience, you might try various 2-liners from >

[sage-support] Re: Sage Crash Report

On Monday, October 23, 2017 at 10:32:30 AM UTC+1, Simon King wrote: > > On 2017-10-23, Jeroen Demeyer > wrote: > > On 2017-10-22 21:01, Jan Groenewald wrote: > >> If you can email this file to the developers > > ...provided with information on how you installed Sage,

[sage-support] Re: Sage Crash Report

On 2017-10-23, Jeroen Demeyer wrote: > On 2017-10-22 21:01, Jan Groenewald wrote: >> If you can email this file to the developers > ...provided with information on how you installed Sage, what OS you are > using, which version of Sage you are running, what command you ran

[sage-support] Re: Sage Crash Report

Thanks Dima for your help. I successfully installed libgfortan however when compiling SageMath a new error appears in the crash report : ImportError: /usr/lib/i386-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by /home/nicolas/SageMath/local/lib/libntl.so.33) Could

[sage-support] Re: Sage Crash Report

At the bottom of your log, one sees: ImportError: libgfortran.so.3: cannot open shared object file: No such file or directory Please install libgfortran (e.g. by installing gfortran), it will fix the problem. On Tuesday, October 10, 2017 at 10:46:35 PM UTC+1, Nicolas Dero Miralles

[sage-support] Re: 'Sage Crash Report

Are you on Fedora 26? Then it looks like this: It looks like you hit this bug: https://bugzilla.redhat.com/show_bug.cgi?id=1464520 You need to install psutils: $ dnf install python2-psutil On Friday, October 6, 2017 at 4:34:09 PM UTC+1, Lee Duke wrote: > >

[sage-support] Re: Sage Crash Report

It's not clear how you're installing Sage. You are running Ubuntu 17 and it appears that you are installing an Ubuntu package of some sort, but how exactly? On Wednesday, September 27, 2017 at 6:58:29 PM UTC+1, The Geeko wrote: > > I'm having problems with new installation of Sage... > > Chris

[sage-support] Re: Sage Crash Report

On Friday, September 1, 2017 at 10:32:17 PM UTC+1, Назар Зибилюк wrote: at the bottom of the log one sees ImportError: No module named psutil Also, it appears to be Sage 7.6 on Fedora 26. First, try sudo dnf install python2-psutil --- I'm not sure whether Sage uses system's Python2, or

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

[sage-support] Re: Sage Crash Report

2017-05-09 18:26:36 UTC+1, Abhishek Kesarwani: > trying to install sagemath on my ubuntu 17.04 it shows the following error: > > Oops, Sage crashed. We do our best to make it stable, but... This might be because Sage requires gfortran to be installed. Try installing gfortran by typing the

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

[sage-support] Re: Sage Crash Report

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. On Tuesday, August 15, 2017 at 6:15:01 PM UTC-7, kats...@gmail.com wrote: > > Sage Crash Report > --

[sage-support] Re: Sage crash report

On Wednesday, December 21, 2016 at 2:14:17 PM UTC-5, leonel torres salinas wrote: > > Hello, i just wanted to try Sagemath in my computer > > Toshiba satellite l745d runing Fedora 25 with LXDE desktop > > I tried to execute it from the binaries but it wasn't enough for it > > Thank you for the

[sage-support] Re: Sage Crash Report

Hi, how is Sage installed in your case? It appears to be some pre-packaged binary installer, but which one? The error is ImportError: No module named psutil On Wednesday, July 19, 2017 at 2:15:59 AM UTC+1, Keivan Monfared wrote: > > > -- You received this message because you are subscribed

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

[sage-support] Re: Sage Crash Report

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 UTC+1, Grant Ellis wrote: > > ​Greetings: > > I originally had Anaconda3 installed on my Ubuntu

[sage-support] Re: Sage Crash Report

It should be enough to run Sage in a shell session where PATH variable does not contain anything from /sw/. (there may be more variable that might affect running Sage, although this is probably a bug then) PS. it is true that Core2 duo is x86_64, but not all such CPUs are created equal.

[sage-support] Re: Sage Crash Report

On Wednesday, June 21, 2017 at 3:01:09 AM UTC-7, Dima Pasechnik wrote: > > > > On Wednesday, June 21, 2017 at 9:04:12 AM UTC+1, whit3rd wrote: >> >> Seconds after install of version 7.6, on MacOS 10.11.6 >> on a MacBook Pro (Core 2 duo, 4GB RAM) >> > > it might be that the executable you

[sage-support] Re: Sage Crash Report

On Wednesday, June 21, 2017 at 9:04:12 AM UTC+1, whit3rd wrote: > > Seconds after install of version 7.6, on MacOS 10.11.6 > on a MacBook Pro (Core 2 duo, 4GB RAM) > it might be that the executable you downloaded needs a better CPU (Core 2 duo is quite old...) What exactly have you installed,

[sage-support] Re: Sage Crash Report

On Sunday, June 18, 2017 at 4:41:22 AM UTC-7, Dima Pasechnik wrote: > > git repo is not relevant, but a python module that shadows a Sage python > module would be a problem. For example, if you have your own file "parser.py", it would interfere with the standard Python module "parser". --

[sage-support] Re: Sage Crash Report

Sorry, it is cause missing gfortran. Now it is working fine. Dne sobota 17. června 2017 12:42:42 UTC+2 vesel...@gmail.com napsal(a): > > Hi, > > i install SageMath from binaries > sage-7.6-Ubuntu_16.04-x86_64.tar.bz2 > > I expand package and run > ./sage > > Then the installation crash. > > My

[sage-support] Re: Sage Crash Report

"ImportError: libgfortran.so.3: cannot open shared object file: No such file or directory" It looks like you need to install fortran on your machine. On Monday, June 5, 2017 at 10:12:12 AM UTC-7, Vincent HERBERT wrote: > > > -- You received this message because you are subscribed to the

[sage-support] Re: Sage crash Report

at the bottom of the report you see ImportError: libgfortran.so.3: cannot open shared object file: No such file or directory You need to install libgfortran in order to fix this. apt-get install libgfortran3 On Wednesday, May 10, 2017 at 9:26:59 AM UTC+1, Abhishek Kesarwani wrote: > > >

[sage-support] Re: Sage Crash Report

What version of Sage is this? It's not clear from the log. The log mentions iPython 4, whereas Sage has switched to iPython 5. It could be that the error comes from some stale content in ~/.sage/ As a 1st check, try to rename ~/.sage/ to something else, and see if it starts then. On Friday,

[sage-support] Re: Sage Crash Report

your log says ImportError: libgfortran.so.3: cannot open shared object file: No such file or directory you need to install this library by the appropriate apt-get call. On Monday, March 27, 2017 at 10:40:42 PM UTC+1, zhang zhou wrote: > > Hello, > > I got a SageMath (7.5.1) crash at its first

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

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

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 Fedora. An internet search suggests something like "yum install gcc-gfortran". -- John

[sage-support] Re: Sage Crash Report

I presume you are trying to install a Sage binary for Ubuntu 16.04 into a VM running this version of Ubuntu, right? At the bottom of your log one sees ImportError: libgfortran.so.3: cannot open shared object file: No such file or directory You need to install libgfortran3 on your (virtual)

[sage-support] Re: Sage Crash Report

is it an installation from source? anyhow, with Sage 7.5 just released, we are already quite far from 7.1 you're trying (why?) to get to work. On Thursday, January 12, 2017 at 3:38:03 PM UTC, Santanu wrote: > > I am getting these. Please help me. > > > santanu@Math-Sans:~/SageMath$ ./sage >

[sage-support] Re: Sage Crash Report

you need libgfortran on your system try doing apt-get install libgfortran3 and re-start sage On Tuesday, December 27, 2016 at 12:13:20 PM UTC, Robert Samal wrote: > > > -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this

[sage-support] Re: Sage crash report 7.0

Yep that did the trick Thanks a lot Le mercredi 14 décembre 2016 14:28:09 UTC+1, Laurent Bakri a écrit : > > > > Hi all, > I am using sage on Debian (sid) > Sagemath 7.0 was working fine until an upgrade of python to version 3 > Then it stop working with an syntax error due to python 3 >

[sage-support] Re: Sage crash report 7.0

On Wednesday, December 14, 2016 at 7:31:30 PM UTC, Laurent Bakri wrote: > > > Hmm.. this is getting hard to follow the thread... > Yes there is a reason I can't upgrade (with the last gcc there is an > error on flint described here "-r and -pie may not be used together" >

[sage-support] Re: Sage crash report 7.0

Hmm.. this is getting hard to follow the thread... Yes there is a reason I can't upgrade (with the last gcc there is an error on flint described here "-r and -pie may not be used together"

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

[sage-support] Re: Sage crash report 7.0

Is there any reason you cannot upgrade to a more recent version? The current stable version is 7.4. On Wednesday, December 14, 2016 at 1:28:09 PM UTC, Laurent Bakri wrote: > > > > Hi all, > I am using sage on Debian (sid) > Sagemath 7.0 was working fine until an upgrade of python to version 3

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

Le vendredi 9 décembre 2016 19:00:35 UTC+1, Girish Belkar a écrit : > > I tried to install Sage 7.4 on my lubuntu using binary > sage-7.4-Ubuntu_16.04-x86_64.tar.bz2. > > I extracted to home folder and the run the command ./sage in terminal > > I got the message that sage has crashed. > > I am

[sage-support] Re: Sage Crash Report

Ok, sorry for my poor message. I installed libgfortran and that solved the problem. Thanks. Em domingo, 6 de novembro de 2016 12:01:34 UTC-3, Afonso Henriques Silva Leite escreveu: > > Please, I need some help here! > -- You received this message because you are subscribed to the Google

[sage-support] Re: Sage Crash Report

On Sunday, November 6, 2016 at 3:01:34 PM UTC, Afonso Henriques Silva Leite wrote: > > Please, I need some help here! > the important line in your report is ImportError: libgfortran.so.3: cannot open shared object file: No such file or directory Probably you are using a binary release of

[sage-support] Re: sage crash report

Eric Gourgoulhon wrote: > Le vendredi 16 septembre 2016 10:37:22 UTC+2, Ralf Stephan a écrit : > > Looks like C++ ABI mismatch. While gcc-4.8.4 should work > you maybe want to install a newer version. What Sage version > is this? > > > I guess this is SageMath 7.3 from the AIMS PPA,

[sage-support] Re: sage crash report

Le vendredi 16 septembre 2016 10:37:22 UTC+2, Ralf Stephan a écrit : > > Looks like C++ ABI mismatch. While gcc-4.8.4 should work > you maybe want to install a newer version. What Sage version > is this? > I guess this is SageMath 7.3 from the AIMS PPA, installed on Ubuntu 16.04. See

[sage-support] Re: sage crash report

Looks like C++ ABI mismatch. While gcc-4.8.4 should work you maybe want to install a newer version. What Sage version is this? -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it,

[sage-support] Re: Sage Crash Report

leif wrote: > Fabio Di Cosmo wrote: >> IPython post-mortem report >> >> {'commit_hash': u'b630b41', >> 'commit_source': 'installation', >> 'default_encoding': 'UTF-8', >> 'ipython_path': >> '/usr/lib/sagemath/local/lib/python2.7/site-packages/IPython', >> 'ipython_version': '4.2.1', >>

[sage-support] Re: Sage Crash Report

Fabio Di Cosmo wrote: > IPython post-mortem report > > {'commit_hash': u'b630b41', > 'commit_source': 'installation', > 'default_encoding': 'UTF-8', > 'ipython_path': > '/usr/lib/sagemath/local/lib/python2.7/site-packages/IPython', > 'ipython_version': '4.2.1', > 'os_name': 'posix', >

[sage-support] Re: Sage Crash Report

Harald Andres Helfgott wrote: > 'platform': 'Linux-3.19.0-66-generic-x86_64-with-debian-jessie-sid', > ... > ImportError: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version > `GLIBCXX_3.4.21' not found (required by > /home/helfgott/Desktop/SageMath/local/lib/libntl.so.25) Smells like you

[sage-support] Re: Sage crash report

Volker Braun wrote: > Missing dependency on gsl on arch? Don't think so, as libgsl.so must have been there during link of the extension module. Either ldconfig has messed up the links, or probably some RUN_PATH issue. (Or he really took some [incomplete] binary built elsewhere.) -leif > >

[sage-support] Re: Sage crash report

Missing dependency on gsl on arch? ImportError: libgsl.so.19: cannot open shared object file: No such file or directory On Monday, August 15, 2016 at 8:48:14 AM UTC+2, leif wrote: > > Dima Pasechnik wrote: > > it is also ipython 5.0, which, as we know, is problematic. > > But -- perhaps

[sage-support] Re: Sage crash report

Dima Pasechnik wrote: > it is also ipython 5.0, which, as we know, is problematic. But -- perhaps surprisingly, the error /here/ is unrelated to IPython. I guess it's Sage 7.4.beta0 though. -leif -- You received this message because you are subscribed to the Google Groups "sage-support"

[sage-support] Re: Sage crash report

it is also ipython 5.0, which, as we know, is problematic. -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-support+unsubscr...@googlegroups.com. To post to

[sage-support] Re: Sage crash report

sebastian bach wrote: > I don't know how to fix this > > *** > > IPython post-mortem report > > {'commit_hash': u'', > 'commit_source': '(none found)', > 'default_encoding': 'UTF-8', > 'ipython_path':

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

[sage-support] Re: Sage Crash Report

Hi Eric, I finally compiled the source of sage from github, but I got a merge conflict when I added the sagemanifolds branch. I'll post further when I get to the office. Hope you could help me. Cheers. On Tuesday, 29 March 2016 15:51:53 UTC-3, Eric Gourgoulhon wrote: > > Hi Oscar, > > I'm

[sage-support] Re: Sage Crash Report

Hi Volker, I discover that a git repository hosted at github. I was able to compile the source from that repository, which is by the way more updated that the repository advertised at the documentation. Nonetheless, I'm still having problems when trying to compile the sagemanifolds branch...

[sage-support] Re: Sage Crash Report

The crash report alone does not say what version of Sage you are using, whether or not you built it yourself, and how to reproduce this crash (just launch Sage in the terminal? something else?) On Friday, February 19, 2016 at 2:52:18 AM UTC, 程海 wrote: > > > -- You received this message because

[sage-support] Re: Sage Crash Report

Thanks, but without knowing how this is obtained, it is not useful, sorry. (we need to know OS, which Sage version, binary or source install, and a sequence of commands that led to the crash) On Saturday, February 6, 2016 at 9:47:13 AM UTC, Herb Doughty wrote: > > > -- You received this

[sage-support] Re: Sage Crash Report

Oh. You're absolutely right! Sorry for wasting bandwidth with that... (I was trying to use the latest Ubuntu 15.10 binary under Mint 17, which is still based on Trusty) Le vendredi 15 janvier 2016 20:28:38 UTC+1, Volker Braun a écrit : > > Presumably you are using a binary that wasn't built for

[sage-support] Re: Sage Crash Report

Presumably you are using a binary that wasn't built for your distribution / version. Compile from source. -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to

  1   2   >