[sage-support] Sage Crash Report

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), (8,11). With Sage 9.5, I get the attached crash report. With Sage 9.8, I get the following linking error

Re: [sage-support] Sage Crash Report

Can you try the following? conda install mamba -n base conda config --add channels conda-forge conda config --set channel_priority strict mamba create -n sagetest sage conda activate sagetest sage On Sun, Aug 21, 2022 at 6:24 PM Robert Parini wrote: > Using conda on macOS 12.4 (with Apple

Re: [sage-support] Sage Crash Report

Sure, output below, thanks --- # packages in environment at /Users/rparini/opt/miniconda3/envs/sagetest: # # NameVersion Build Channel _r-mutex 1.0.1 anacondar_1conda-forge alabaster 0.7.12

Re: [sage-support] Sage Crash Report

Can you share the output of the following command? conda list -n sagetest On Sun, Aug 21, 2022 at 6:24 PM Robert Parini wrote: > Using conda on macOS 12.4 (with Apple silicon) I get the attached error > after installing sage with: > > conda create -n sagetest sage > conda activate sagetest >

[sage-support] Sage Crash Report

Using conda on macOS 12.4 (with Apple silicon) I get the attached error after installing sage with: conda create -n sagetest sage conda activate sagetest sage -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and

[sage-support] Sage Crash Report

Dear Developers, I am using a MacOs Monterrey v.12.4 on a chip M2. Sage was install using anaconda, with mamba. The funny thing is that I install in two different accounts, one administrator and one regular user. Sage conda environment in the administrator account works fine. In the regular

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

On Wed, 16 Feb 2022, 02:43 'Bharathwaj Palvannan' via sage-support, < sage-support@googlegroups.com> wrote: > Hi, > > > > Please help me! I am unable to get Sagemath working and I really don’t > know what’s happening. I recently got a new laptop. This is a macOS > operating system (Version 12.1

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

Hi, Please help me! I am unable to get Sagemath working and I really don’t know what’s happening. I recently got a new laptop. This is a macOS operating system (Version 12.1 Monterey). I installed SageMath using the dmg file on the Sagemath website. I had already sent a crash report some weeks

Re: [sage-support] Sage Crash Report

On Monday, January 17, 2022, Dima wrote: > This is an M1 machine, right? I don't think we already support these. > The recommended binaries for macOS, namely https://github.com/3-manifolds/Sage_macOS/releases are known to work fine on M1, though using Rosetta emulation for Sage 9.4. An

Re: [sage-support] Sage Crash Report

On Sun, Jan 16, 2022 at 4:56 PM 'Bharathwaj Palvannan' via sage-support wrote: > > Dear developers, > > > > I have been trying to install Sage on my macOS (Version 12.1 Monterey). I > tried installing it via the .tar and the .dmg files, but both methods failed > for various reasons. I am

[sage-support] Sage Crash Report

Dear developers, I have been trying to install Sage on my macOS (Version 12.1 Monterey). I tried installing it via the .tar and the .dmg files, but both methods failed for various reasons. I am attaching the crash report that was generated when I tried using the dmg file. Thanks Best regards

Re: [sage-support] Sage crash report

On Mon, Jan 10, 2022 at 2:12 PM Alba Carrodeguas wrote: > > Hello I´m using sage 6.10 through virtual machine, oracle, for linux. > The problem is when I start the virtual machine everything works fine until > it asks me for login and pasword, I write sage for both and also for the > other one

Re: [sage-support] Sage crash report

On Mon, Jan 10, 2022 at 11:39 AM Alba Carrodeguas wrote: > > Sage crashed when logging in through virtual machine in order to be of any help, we'd need more details: what VM (virtual machine), what OS, what Sage version, how it was installed, how exactly you were trying to start Sage, what was

[sage-support] Sage crash report

Sage crashed when logging in through virtual machine -- 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 view this

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

Same circumstances as in the previous case : on Debian testing running on core i7 + 16 GB RAM, after upgrading Sage 9.5.beta7 compiled from a git tree  to 9.5.beta8, Sage crashes at startup. Crash report enclosed I'll try the same steps as in the last occurrence... -- Emmanuel Charpentier --

Re: [sage-support] Sage Crash Report

I can ask this another way. I have the tarball, and I want to end up with a system wide install. This is not build from source. What is the best way to do this? In the referenced instructions the modification is to SAGE_LOCAL and not SAGE_ROOT. I'm confused as to the difference and effect.

Re: [sage-support] Sage Crash Report

As the directory is in /opt and ownership is root.root, I can't run this as it gets permission denied when writing the log file. On Wednesday, September 1, 2021 at 2:08:56 PM UTC-5 Matthias Koeppe wrote: > See >

Re: [sage-support] Sage Crash Report

See https://github.com/sagemath/sage/blob/develop/README.md#instructions-to-build-from-source point 4 ("./configure --prefix") On Wednesday, September 1, 2021 at 12:00:15 PM UTC-7 hbetx9 wrote: > So I got this working in my home directory but want the SageMath directory > system wide. I moved

Re: [sage-support] Sage Crash Report

So I got this working in my home directory but want the SageMath directory system wide. I moved it to /opt and changed ownership to root.root, however this causes now a disagreement with the SAGE_ROOT environment variable. Should I unpack the tarball as root there to install or is there an easy

Re: [sage-support] Sage Crash Report

On Tuesday, August 31, 2021 at 12:55:46 PM UTC-7 hbetx9 wrote: > On my system, python2 and python3 is installed, but there is no generic > python symlink. Does this need to be created for sage and if so should it > be python3? In installed from tarball, so this is not an issue with the >

Re: [sage-support] Sage Crash Report

On my system, python2 and python3 is installed, but there is no generic python symlink. Does this need to be created for sage and if so should it be python3? In installed from tarball, so this is not an issue with the Ubuntu package. On Monday, August 30, 2021 at 9:13:49 AM UTC-5 hbetx9

Re: [sage-support] Sage Crash Report

I think the issue is a disagreement with python. The package installs fine on a clean machine. I know this isn't the wheelhouse, but how can I diagnose my python configuration for compatibility with sage. In particular, I have python 3.8.10 installed systemwide. On Sunday, August 29, 2021 at

Re: [sage-support] Sage Crash Report

The package log has the following error: /usr/lib/python3/dist-packages/sage/combinat/root_system/branching_rules.py:1753: SyntaxWarning: "is not" with a literal. Did you mean "!="? if len(stypes) is not 2: /usr/lib/python3/dist-packages/sage/graphs/graph_latex.py:1159: SyntaxWarning: 'str'

Re: [sage-support] Sage Crash Report

On Sat, Aug 28, 2021 at 10:57 PM Lance Edward Miller wrote: > > To whom it may concern, > > I'm installing sage from the synaptic package manager on Linux Mint 20.1. > The package is for Sage 9.0, but the app does not run. Following is the crash > report, any advice on how to best resolve

[sage-support] Sage Crash Report

To whom it may concern, I'm installing sage from the synaptic package manager on Linux Mint 20.1. The package is for Sage 9.0, but the app does not run. Following is the crash report, any advice on how to best resolve (uninstall and install from source?) is appreciated:

Re: [sage-support] Sage Crash Report

it appears that installing blender changed Python used to in Sage's venv. All bets are off in such a scenario - you'd need to rebuild Sage. On Tue, 17 Aug 2021, 00:20 Gaël Cousin, wrote: > Ubuntu 20.04 Focal Fossa > > > Dear all, > > Here follows attached a sage crash report. I think the

[sage-support] Sage Crash Report

Ubuntu 20.04 Focal Fossa Dear all, Here follows attached a sage crash report. I think the sage install was broken by installation of Blender. Sage was installed this way on my fresh Ubuntu 20.04 Focal Fossa: sudo apt install sagemath sagetex- texlive-latex-base- sagemath-jupyter-

Re: [sage-support] Sage Crash Report

Thank you Dima and Isuru, creating a new conda environment worked! (I'm guessing you updated the givaro dependency for the conda install) And it looks like manually specifying an older version of givaro will also work, based on Mariusz's report. On Wed, Mar 24, 2021 at 3:21 PM Mariusz Sokolowski

Re: [sage-support] Sage Crash Report

hey, I had similar/same(?) problem as Mike and installing older version of givaro (conda install "givaro=4.1.1=h192cbe9_1") fixed it. -M On Wednesday, March 24, 2021 at 12:55:05 PM UTC-4 isu...@gmail.com wrote: > Mike, > > Can you try creating a new conda environment? This is an issue with

Re: [sage-support] Sage Crash Report

Mike, Can you try creating a new conda environment? This is an issue with the latest givaro build we had and we marked it as broken. Details at https://github.com/conda-forge/givaro-feedstock/issues/13 (You could also try doing `conda install "givaro=4.1.1=h192cbe9_1"` to get the older link.)

Re: [sage-support] Sage Crash Report

Not sure if this is relevant, but I get the following messages when I try running 'conda update givaro' in my sage conda environment (attached). I apologize for multiple messages! On Wed, Mar 24, 2021 at 8:42 AM Mike Lee wrote: > I believe the following line in the output of the nm command you

Re: [sage-support] Sage Crash Report

I believe the following line in the output of the nm command you suggested is the corresponding symbol? 00017da0 T Givaro::Integer::operator std::__cxx11::basic_string, std::allocator >() const I've also attached the full output of the nm command as a txt file below in case it's helpful!

Re: [sage-support] Sage Crash Report

On Tue, Mar 23, 2021 at 10:27 PM Mike Lee wrote: > > Hi, > > I'm facing a similar issue when I tried to install Sage through conda (I > followed the 'Setting Up' directions in https://wiki.sagemath.org/Conda). I > get the following error in my Sage_crash_report.txt (attached) > > 'ImportError:

Re: [sage-support] Sage Crash Report

Hi, I'm facing a similar issue when I tried to install Sage through conda (I followed the 'Setting Up' directions in https://wiki.sagemath.org/Conda). I get the following error in my Sage_crash_report.txt (attached) 'ImportError:

Re: [sage-support] Sage Crash Report

at the bottom of the log you see ImportError: /home/mathieu/opt/SageMath/local/lib/python3.8/site-packages/sage/matrix/matrix_modn_sparse.cpython-38-x86_64-linux-gnu.so: undefined symbol: _ZNK6Givaro7IntegercvNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEB5cxx11Ev which is an indication

[sage-support] Sage Crash Report

-- 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 view this discussion on the web visit

[sage-support] Sage Crash Report

Hi, I encountered the following problems with sage: 1. It crashes when I am using tab auto completion - report attached. 2. Each time I want to use sage (by command 'sage') after restarting the system I need to type 'conda activate sage'. Otherwise command sage is not recognized ('-bash: sage:

[sage-support] Sage Crash Report

Hello, I would appreciate your feedback on a Sage crash that I'm facing after several trials. Please find attached the associated report along with some potentially relevant information below: - Which operating system: MacOS Mojave *$ sw_vers* ProductName: Mac OS X ProductVersion: 10.14.6

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

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, but I think that is not my case. Thanks for the help in advance! --

Re: [sage-support] Sage Crash Report

On Thu, Apr 23, 2020 at 9:42 PM Jean-Florent Raymond wrote: > > Hello, > > Did you try to rebuild since the upgrade? > If you upgraded a package that sage needs, then sage might complain that > it cannot find the version it was used to. > > It seems to be the case with libntl according to the

Re: [sage-support] Sage Crash Report

Hello, Did you try to rebuild since the upgrade? If you upgraded a package that sage needs, then sage might complain that it cannot find the version it was used to. It seems to be the case with libntl according to the crash report you attached: ImportError: libntl.so.35: cannot open shared

[sage-support] Sage Crash Report

Hello, Here is the report of a crash that happened while trying to lunch sage: -Operating system: Ubuntu 20.04 beta, upgraded from 19.10. -Sage (8.9) was build from the source under Ubuntu 19.10 and by following the instructions in this page

Re: [sage-support] Sage Crash Report

Thank you very much for your suggestion. But now I got another problem about the building the package xz-5.2.2.p0. I attached the log file here. Any help will be greatly appreciated! Isuru Fernando 于2020年4月13日周一 下午8:50写道： > Looks like you are using ccache, but CCACHE_DIR is not pointing to the

Re: [sage-support] Sage Crash Report

Looks like you are using ccache, but CCACHE_DIR is not pointing to the scratch folder. Delete $HOME/.ccache and set CCACHE_DIR env variable to some place like /scratch/user/hhuang235/.ccache Isuru On Mon, Apr 13, 2020 at 8:45 PM HANG HUANG wrote: > Thanks very much for your reply. In fact, my

Re: [sage-support] Sage Crash Report

Thanks very much for your reply. In fact, my scratch folder has almost 1T of free space. So I am really confused of why I got that error message. Best, Amy 'Justin C. Walker' via sage-support 于2020年4月13日周一 下午6:16写道： > > > > On Apr 13, 2020, at 14:59 , HANG HUANG wrote: > > > > I am trying

Re: [sage-support] Sage Crash Report

> On Apr 13, 2020, at 14:59 , HANG HUANG wrote: > > I am trying to install Sage version 9.0 on the High performance cluster at my > university, which runs Linux (CentOS 7). I am installing to my local > "scratch" folder since I do not have administrative permissions. I am trying > to

Re: [sage-support] Sage Crash report

I didn't see that option, will use in future, thanks! On Thursday, April 9, 2020 at 2:56:23 PM UTC-5, John H Palmieri wrote: > > Did you look at the file "README.md"? It suggests building in parallel to > speed things up. Have you tried that? > > > On Thursday, April 9, 2020 at 12:35:58 PM

Re: [sage-support] Sage Crash report

Did you look at the file "README.md"? It suggests building in parallel to speed things up. Have you tried that? On Thursday, April 9, 2020 at 12:35:58 PM UTC-7, hbetx9 wrote: > > I htink I know what I did, somehow I change the prefix to a directory that > didn't exist. I'm recompiling to see

Re: [sage-support] Sage Crash report

I htink I know what I did, somehow I change the prefix to a directory that didn't exist. I'm recompiling to see if the error is fixed. Boy does this compile take a LONG time, is that the same for everyone? On Thursday, April 9, 2020 at 2:26:48 PM UTC-5, hbetx9 wrote: > > Okay, I did

Re: [sage-support] Sage Crash report

Okay, I did something apparently odd. For context, I first unpacked in a directory, ran make (took a long time) and would close with an error concerning R as above. Sage would work on command line by running the copy in this directory. However, something I did broke this install, and I'm

Re: [sage-support] Sage Crash report

On Wednesday, April 8, 2020 at 8:01:38 PM UTC-7, hbetx9 wrote: > > No, I just want all users to have this at default. Where should I put the > SAGE_ROOT directory? /usr/local? > Use "./configure --prefix=/usr/local/opt/sage-9.0" to set the installation prefix (SAGE_LOCAL). -- You received

Re: [sage-support] Sage Crash report

No, I just want all users to have this at default. Where should I put the SAGE_ROOT directory? /usr/local? On Wednesday, April 8, 2020 at 9:36:33 PM UTC-5, Dima Pasechnik wrote: > > On Thu, Apr 9, 2020 at 10:30 AM hbetx9 > > wrote: > > > > Hi Matthias, > > > > Boy what a mess this is. I

Re: [sage-support] Sage Crash report

On Thu, Apr 9, 2020 at 10:30 AM hbetx9 wrote: > > Hi Matthias, > > Boy what a mess this is. I didn't realize the rabbit hole went down that far. > Do you think I could skip this and after upgrading sage later stable versions > (I see you and others are working on it), this can be resolved? > >

Re: [sage-support] Sage Crash report

Hi Matthias, Boy what a mess this is. I didn't realize the rabbit hole went down that far. Do you think I could skip this and after upgrading sage later stable versions (I see you and others are working on it), this can be resolved? If I don't resolve this now, then sage works but I'd like

Re: [sage-support] Sage Crash report

Read https://doc.sagemath.org/html/en/developer/ if you wish to make changes to Sage, and https://trac.sagemath.org/ticket/29379 for the change ticket that makes the upgrade to R 3.6.3 On Wednesday, April 8, 2020 at 3:02:01 PM UTC-7, hbetx9 wrote: > > I _almost_ got this to work, I have R

Re: [sage-support] Sage Crash report

I _almost_ got this to work, I have R 3.6.3 but still get the following error: * package: r-3.6.2 log file: /home/lmiller/sage-9.0/logs/pkgs/r-3.6.2.log build directory: /home/lmiller/sage-9.0/local/var/tmp/sage/build/r-3.6.2 Presumably, there is a flag or configure I can send make to use

Re: [sage-support] Sage Crash report

On second thought, I should just fix this now. Am I correct I need to install package r-3.6.2 and rebuld? On Wednesday, April 8, 2020 at 11:54:39 AM UTC-5, hbetx9 wrote: > > Tried from source and got this error: > > Error building Sage. > > The following package(s) may have failed to build

Re: [sage-support] Sage Crash report

Thanks, I'll have to make that adjustment, at the moment I have two versions of sage, so I need to figure out how to make it just version 9 first. Otherwise my home .sage directory won't drive behavior of the things in SAGE_ROOT/local correct? On Wednesday, April 8, 2020 at 12:15:53 PM

Re: [sage-support] Sage Crash report

> can the color scheme for sage on the terminal be changed? > I used a dark background so this is not easy to read. If using the Sage REPL on a dark background, run the command sage: %colors Linux You can also include that command in a file called `init.sage` file, located in the `.sage`

Re: [sage-support] Sage Crash report

Tried from source and got this error: Error building Sage. The following package(s) may have failed to build (not necessarily during this run of 'make all-start'): * package: r-3.6.2 log file: /home/lmiller/sage-9.0/logs/pkgs/r-3.6.2.log build directory:

Re: [sage-support] Sage Crash report

On Wed, Apr 8, 2020 at 11:05 AM hbetx9 wrote: > I installed from package on Mint 19.3. I'm happy to run whatever is > needed to help diagnose. For context, I have installed python 2.7.17 and the > package pulled sage 8.1. I'm not sure why the packages didn't pull the most > up to date. Is

Re: [sage-support] Sage Crash report

Hi Dima. I installed from package on Mint 19.3. I'm happy to run whatever is needed to help diagnose. For context, I have installed python 2.7.17 and the package pulled sage 8.1. I'm not sure why the packages didn't pull the most up to date. Is there a PPA I need to add? Best, Lance On

Re: [sage-support] Sage Crash report

On Sun, Apr 5, 2020 at 7:44 AM Lance Edward Miller wrote: > > After install on Linux Mint 19.3, I got the following crash report. Any help > is appreciated. What exactly have you installed? A binary installation, or done a build from sources? > >

[sage-support] Sage Crash report

After install on Linux Mint 19.3, I got the following crash report. Any help is appreciated. *** IPython post-mortem report {'commit_hash': u'b467d487e', 'commit_source': 'installation', 'default_encoding': 'UTF-8',

Re: [sage-support] Sage Crash Report

Also, sqlite has been updated in sagemath 9.0, as well as we have there https://trac.sagemath.org/ticket/28511 which is meant to help with skew clock issues. On Wed, 25 Mar 2020, 14:42 Dima Pasechnik, wrote: > > > On Wed, 25 Mar 2020, 14:19 Kashif Bari, wrote: > >> I do not believe I I have

Re: [sage-support] Sage Crash Report

On Wed, 25 Mar 2020, 14:19 Kashif Bari, wrote: > I do not believe I I have permissions to build on a disk physically in the > machine being used. > you may ask for, at least, explaining that you have a problem with skew timestamps. The scratch folder is where I was told to install any

Re: [sage-support] Sage Crash Report

I do not believe I I have permissions to build on a disk physically in the machine being used. The scratch folder is where I was told to install any software that I wish to use. The home directory that I have is not large enough to install anything. On Tue, Mar 24, 2020 at 8:43 PM Dima Pasechnik

Re: [sage-support] Sage Crash Report

On Wed, 25 Mar 2020, 02:21 Kashif Bari, wrote: > Hi Dima, > > I am building locally, as this is a university cluster and I only have > access to my local directories. > by "local" I mean the filesystem on a disk physically in the machine you are using, as opposed to a networked file system,

Re: [sage-support] Sage Crash Report

Hi Dima, I am building locally, as this is a university cluster and I only have access to my local directories. Unfortunately, this did not resolve the issue and this line was added to my output: [sqlite-3270100] configure: WARNING: unrecognized options: --disable-maintainer-mode In the log

Re: [sage-support] Sage Crash Report

On Tue, Mar 24, 2020 at 4:51 PM Kashif Bari wrote: > > I believe I was able to resolve the issue with mpc-1.1.0 by loading a more > recent version of the texinfo package! Hopefully others who have this issue > will be able to resolve it similarly. > > However, I ended up running into this issue

Re: [sage-support] Sage Crash Report

I believe I was able to resolve the issue with mpc-1.1.0 by loading a more recent version of the texinfo package! Hopefully others who have this issue will be able to resolve it similarly. However, I ended up running into this issue when running make again: Error building Sage. The following

Re: [sage-support] Sage Crash Report

On Thu, Mar 19, 2020 at 12:25 PM Kashif Bari wrote: > > Thank you, Dima, I was able to load the texinfo package before I did make and > I believe this resolved my issue with mpfr. However, I ran into the same > issue with mpc-1.1.0 now instead of mpfr. hmm, the same? If you have now makeinfo

Re: [sage-support] Sage Crash Report

Thank you, Dima, I was able to load the texinfo package before I did make and I believe this resolved my issue with mpfr. However, I ran into the same issue with mpc-1.1.0 now instead of mpfr. I currently have sage 8.9 installed on my personal laptop, so I figured I would stick with the same

Re: [sage-support] Sage Crash Report

mpfr needs makeinfo program to be installed. This is a pretty standard thing, which on Centos is in texinfo package https://centos.pkgs.org/7/centos-x86_64/texinfo-5.1-5.el7.x86_64.rpm.html By the way, why are you building Sage 8.9, and not 9.0? On Thu, Mar 19, 2020 at 7:00 AM Kashif Bari

Re: [sage-support] Sage Crash Report

Thank you! Best, Kash > On Mar 18, 2020, at 6:48 PM, Isuru Fernando wrote: > >  > One alternative to installing sage is by using the conda package manager. > https://github.com/conda-forge/miniforge#download > It's know to work on CentOS 6 and above. > See

Re: [sage-support] Sage Crash Report

No, it doesn't require sudo privileges. It can be installed in your home directory. Isuru On Wed, Mar 18, 2020 at 8:05 PM wrote: > Hi! > Thanks for responding! Will this require any administrative permissions? > I do not have any sudo privileges. > > On Mar 18, 2020, at 6:48 PM, Isuru

Re: [sage-support] Sage Crash Report

Hi! Thanks for responding! Will this require any administrative permissions? I do not have any sudo privileges. > On Mar 18, 2020, at 6:48 PM, Isuru Fernando wrote: > >  > One alternative to installing sage is by using the conda package manager. >

Re: [sage-support] Sage Crash Report

One alternative to installing sage is by using the conda package manager. https://github.com/conda-forge/miniforge#download It's know to work on CentOS 6 and above. See https://github.com/conda-forge/sage-feedstock#installing-sage Isuru On Wed, Mar 18, 2020 at 6:00 PM Kashif Bari wrote: > I am

[sage-support] Sage Crash Report

I am trying to install Sage version 8.9 on the High performance cluster at my university, which runs Linux (CentOS 7). I am installing to my local "scratch" folder since I do not have administrative permissions. I am trying to install from source code as the pre-built binaries are for Ubuntu

Re: [sage-support] Sage Crash report

at the end of your log: ImportError: libgfortran.so.3: cannot open shared object file: No such file or directory Are you using system's gfortran? (you should) On Wed, Jan 8, 2020 at 4:42 PM Malcolm MacCallum wrote: > > This is from Ubuntu 18.04 Linux 64-bit > Sage built from source. The build

[sage-support] Sage Crash report

This is from Ubuntu 18.04 Linux 64-bit Sage built from source. The build had an error as follows = The following package(s) may have failed to build (not necessarily during this run of 'make all-start'): * package: r-3.6.2 log file: /usr/local/CA/sage-9.0/logs/pkgs/r-3.6.2.log

Re: [sage-support] Sage Crash Report

On Sun, 5 Jan 2020, 18:26 Jean-Florent Raymond, wrote: > Hello, > > Did you succeed building sage from source? If not what is the error > message? > Do you have a system version of ntl? ( pacman -Qs ntl ) > > On Arch linux (similar to Manjaro) I had the same message error > yesterday when trying

Re: [sage-support] Sage Crash Report

On Fri, Jan 3, 2020 at 9:03 AM Artemis Heller wrote: > > Hi, > > Here is the crash report from a freshly installed sagemath 9.0.1 from pacman > on manjaro linux with python 3.8. > > I've been trying to install sage 9.0 all day, sage library crashes the build > from source, I've tried installing

[sage-support] Sage Crash Report

Hi, Here is the crash report from a freshly installed sagemath 9.0.1 from pacman on manjaro linux with python 3.8. I've been trying to install sage 9.0 all day, sage library crashes the build from source, I've tried installing 8.9 from pacman with a pyenv of 3.7.4 in case python 3.8 is the

[sage-support] Sage Crash Report, please help!

/home/andreas/.ipython/Sage_crash_report.txt -- 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 view this discussion

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

I followed the installation instructions for conda with both python=3.6 (the most recent version that could install sage without conflicts) and then python=2.7 (the one specifically cited in the instructions) on macOS 10.13.6, using

Re: [sage-support] Sage Crash Report

Le lundi 14 octobre 2019 08:57:57 UTC+2, Dima Pasechnik a écrit : > > Dear Dave, > > On Mon, Oct 14, 2019 at 1:03 AM dave dobbs > > wrote: > > > > OS: Xubuntu 18.04.1 64-bit > > downloaded from SAGE: sage-8.9-Ubuntu_16.04-x86_64.tar.bz2 > > wrong version - notice that you are running Ubuntu

Re: [sage-support] Sage Crash Report

On Sat, Oct 19, 2019 at 12:07 AM Sinan Kapçak wrote: > > on Linux Ubuntu 19.10 - > Sage installed by binaries downloaded by a torrent. > Downloaded and extracted and ./sage. it would be surprising if a binary for an earlier Ubuntu version worked on 19.10. You might need to build Sage from

[sage-support] Sage Crash Report

*on Linux Ubuntu 19.10 - * *Sage installed by binaries downloaded by a torrent.* *Downloaded and extracted and ./sage.* *** IPython post-mortem report {'commit_hash': u'033ab93c7', 'commit_source': 'installation',

Re: [sage-support] Sage Crash Report

Dear Dave, On Mon, Oct 14, 2019 at 1:03 AM dave dobbs wrote: > > OS: Xubuntu 18.04.1 64-bit > downloaded from SAGE: sage-8.9-Ubuntu_16.04-x86_64.tar.bz2 wrong version - notice that you are running Ubuntu 18.04, and you're trying a tarball fot 16.04. Tarball for 18.04 is not ready yet, I think.

[sage-support] Sage Crash Report

OS: Xubuntu 18.04.1 64-bit downloaded from SAGE: sage-8.9-Ubuntu_16.04-x86_64.tar.bz2 decompressed with tar -xjf sage-8.9... I did a cd to the uncompressed folder, SageMath, and issued the command: ./sage It then went thru a long sequence of patches, put up the following msg box:

Re: [sage-support] sage crash report

Dear Oscar, You should tell precisely what is your installation of Sage that is broken. Looking at the crash report, I assume that you use Sage from the system. In this situation, you would better address your question to some Debian help forum or mailing list. For the bug you encountered, it

[sage-support] sage crash report

Dear community, I've worked extensively with Sage on Debian, either source compiled or installed from the repository. Last month I update my system to Debian Bullseye, and since then I've been unable of using sage! I'm attaching the automatically generated crash report. I thank you in advance

Re: [sage-support] Sage Crash Report

This is built by Debian people, so it's really not our bug, I cc to the relevant list, On Sat, Aug 17, 2019 at 6:32 PM Carlos Mauricio Silva wrote: > > Hi, > I would like to report a crash: > > Operating System: Debian Linux Testing > carlos@arroway:~$ uname -a > Linux arroway 4.19.0-5-amd64 #1

[sage-support] Sage Crash Report

Hi, I would like to report a crash: Operating System: Debian Linux Testing carlos@arroway:~$ uname -a Linux arroway 4.19.0-5-amd64 #1 SMP Debian 4.19.37-6 (2019-07-18) x86_64 GNU/Linux SageMath was installed from Debian Repositories: apt-get install sagemath SageMath crashes right after

Re: [sage-support] Sage Crash Report

Why is the package named "sagemath" not installed? Did you intentionally install only "sagemath-common"? To have a fully working SageMath installation you need the three packages sagemath sagemath-doc-en sagemath-jupyter The package "sagemath-common" is a dependency of the first one of

Re: [sage-support] Sage Crash Report

I still have not received an answer to this. Is the information I provided helpful or do you need more? On Wed, May 1, 2019 at 8:35 AM Erik Wallace wrote: > Here is the output: > > $ apt list --installed | grep sagemath > > sagemath-common/bionic,bionic,now 8.1-7ubuntu1 all [installed] > > $ ls

Re: [sage-support] Sage Crash Report

Hi, I am sorry I double posted but I though my post did not get through (I did not find it because it was added to an existing topic/post, probably due to the subject?) Yes, the sage installation works. The error also occurs if I download the source tarball and try to install from source.

Re: [sage-support] Sage Crash Report

It would be good to know whether your Sage installation is working at all. In case, can you try some simple computations at Sage prompt? On Sat, May 11, 2019 at 4:14 AM Clemens wrote: > > OS: macOS 10.14 > Installed from: sage-8.7-OSX_10.13.6-x86_64.dmg (Extracted to ~/SageMath) > > How to

[sage-support] Sage Crash Report

OS: macOS 10.14 Installed from: sage-8.7-OSX_10.13.6-x86_64.dmg (Extracted to ~/SageMath) How to reproduce: I wanted to use zeta_zeros(). The help documents the dependency "database_odlyzko_zeta", which I then tried to install as follows: ./sage -i database_odlyzko_zeta However, this failed

  1   2   3   >