Re: [sage-support] Sage Crash Report

[Isuru Fernando]

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 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 stop receiving emails from it, send an
> email to sage-support+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-support/91AA814C-8330-4F1F-9120-7B11D1941B66%40gmail.com
> .
>

-- 
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 
https://groups.google.com/d/msgid/sage-support/CA%2B01voNjrQosBmSGzG2N-M-9D5zL4QeYT3QYgckE4Py71MNZLQ%40mail.gmail.com.

Re: [sage-support] Sage Crash Report

[Robert Parini]

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 py_0conda-forge
appnope   0.1.3  pyhd8ed1ab_0conda-forge
arb   2.22.1   hb5d1efa_0conda-forge
argon2-cffi   21.3.0 pyhd8ed1ab_0conda-forge
argon2-cffi-bindings  21.2.0   py39hb18efdd_2conda-forge
arpack3.7.0h58ebc17_2conda-forge
attrs 22.1.0 pyh71513ae_1conda-forge
babel 2.10.3 pyhd8ed1ab_0conda-forge
backcall  0.2.0  pyh9f0ad1d_0conda-forge
backports 1.1pyhd3eb1b0_0
backports.functools_lru_cache 1.6.4  pyhd8ed1ab_0conda-forge
bdw-gc8.0.6hc021e02_0conda-forge
beautifulsoup44.11.1 pyha770c72_0conda-forge
beniget   0.4.1  pyhd8ed1ab_0conda-forge
blas-devel3.9.0   16_osxarm64_openblas   
 conda-forge
bleach3.3.1  pyhd8ed1ab_0conda-forge
brial 1.2.11 pyh694c41f_0conda-forge
brotli1.0.9h1c322ee_7conda-forge
brotli-bin1.0.9h1c322ee_7conda-forge
brotlipy  0.7.0   py39hb18efdd_1004conda-forge
bwidget   1.9.14   hce30654_1conda-forge
bzip2 1.0.8h3422bc3_4conda-forge
c-ares1.18.1   h3422bc3_0conda-forge
ca-certificates   2022.07.19   hca03da5_0
cairo 1.16.0had492bb_1012conda-forge
cctools_osx-arm64 949.0.1 h332cad3_24
cddlib1!0.94m  h6d7a090_0conda-forge
certifi   2022.6.15py39h2804cbe_0conda-forge
cffi  1.15.1   py39h04d3946_0conda-forge
charset-normalizer2.1.0  pyhd8ed1ab_0conda-forge
clang 12.0.0   hca03da5_4
clang-12  12.0.0  default_he099f3d_4
clang_osx-arm64   12.0.0   hcb56dc5_3
clangxx   12.0.0  default_he099f3d_4
clangxx_osx-arm64 12.0.0   h39b79ac_3
cliquer   1.22 h27ca646_0conda-forge
colorama  0.4.5  pyhd8ed1ab_0conda-forge
compiler-rt   12.0.0   h4ccfd99_3
compiler-rt_osx-arm64 12.0.0   h4fb70ea_3
cryptography  37.0.4   py39h4cb6239_0conda-forge
curl  7.84.0   h1a28f6b_0
cvxopt1.3.0py39h0786196_1conda-forge
cycler0.11.0 pyhd8ed1ab_0conda-forge
cypari2   2.1.2py39hfa3855d_5conda-forge
cysignals 1.11.2   py39h17b953c_0conda-forge
cython0.29.32  py39h6e3512e_0conda-forge
debugpy   1.6.3py39h3c22d25_0conda-forge
decorator 5.1.1  pyhd8ed1ab_0conda-forge
defusedxml0.7.1  pyhd8ed1ab_0conda-forge
docutils  0.17.1   py39hca03da5_1
dsdp  5.8   h9397a75_1203conda-forge
ecl   21.2.1   h8492d4d_2conda-forge
eclib 20210625 h334b3ce_4conda-forge
ecm   7.0.4 h47c7c1a_1002conda-forge
entrypoints   0.4pyhd8ed1ab_0conda-forge
expat 2.4.8h6b3803e_0conda-forge
fflas-ffpack  2.4.3h11f2abc_2conda-forge
fftw  3.3.10  nompi_h2e33b67_103conda-forge
flintqs   1.0   ha2e105b_1001conda-forge
flit-core 3.7.1  pyhd8ed1ab_0conda-forge
font-ttf-dejavu-sans-mono 2.37 hab24e00_0conda-forge
font-ttf-inconsolata  3.000h77eed37_0conda-forge
font-ttf-source-code-pro  2.038h77eed37_0conda-forge
font-ttf-ubuntu   0.83 hab24e00_0conda-forge
fontconfig2.14.0   hfb34624_0conda-forge
fonts-conda-ecosystem 1 0conda-forge
fonts-conda-forge 1 0conda-forge
fonttools 

Re: [sage-support] Sage Crash Report

[Isuru Fernando]

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
>
> --
> 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
> https://groups.google.com/d/msgid/sage-support/91AA814C-8330-4F1F-9120-7B11D1941B66%40gmail.com
> .
>

-- 
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 
https://groups.google.com/d/msgid/sage-support/CA%2B01voO5KV0G208%2B_kpe%2BgNPbpAeQCX3rDnZrSdKo7zL%3DGoYNw%40mail.gmail.com.

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

[Dima Pasechnik]

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 Monterey). I installed SageMath using the
> dmg file on the Sagemath website. I had already sent a crash report some
> weeks ago but I received no response. I literally just typed in sage on the
> mac terminal and the app crashed.
>

there are a number of such files on the website, you need the right one.

Please post the link to the dmg you downloaded,
and whether you have M1 mac or Intel mac.






>
> Thank you.
>
> Best regards
>
>
>
>
>
> --
> 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
> https://groups.google.com/d/msgid/sage-support/PN3PR01MB77422FCD7A7E2225D795ECA4F7359%40PN3PR01MB7742.INDPRD01.PROD.OUTLOOK.COM
> 
> .
>

-- 
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 
https://groups.google.com/d/msgid/sage-support/CAAWYfq3UAH4wKsoPLCfmAM6woZf9CmL16wLwQpRW6p7kk4piWg%40mail.gmail.com.

Re: [sage-support] Sage Crash Report

[Nathan Dunfield]

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 M1-native version should be available for the upcoming SageMath 9.5, and 
a prerelease version has been posted at the above, though it has some known 
issues.

Best,

Nathan

-- 
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 
https://groups.google.com/d/msgid/sage-support/682dfacf-5d62-4095-ab4f-edabd2a6e3ebn%40googlegroups.com.

Re: [sage-support] Sage Crash Report

[Dima Pasechnik]

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 attaching the crash report that was generated when 
> I tried using the dmg file.

This is an M1 machine, right?
I don't think we already support these. See
https://trac.sagemath.org/ticket/30592

>
>
>
> Thanks
>
> Best regards
>
> --
> 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 
> https://groups.google.com/d/msgid/sage-support/PN3PR01MB774291BC0556E56BBA2E0168F7569%40PN3PR01MB7742.INDPRD01.PROD.OUTLOOK.COM.

-- 
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 
https://groups.google.com/d/msgid/sage-support/CAAWYfq0Ct8Q032o6Z-R%3D2%3DVyPvqQnJU2tmB4mU%2BVM9kd_4058g%40mail.gmail.com.

Re: [sage-support] Sage crash report

[Dima Pasechnik]

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 that is asked. But after all the problem comes up like in the 
> attached picture.

the error message on the right might mean that you just need to
increase the amount of disk space available to your VM.

> Thank you so much, I need to get a worksheet that is just in there and need 
> to get it back.

Anyhow, you don't need to run Sage to get your worksheets.
They are stored in ~/.sage/
directory.

What's the output of

ls -lR ~/.sage/

?

> Thank you for your time
>
> El lunes, 10 de enero de 2022 a las 13:22:51 UTC+1, dim...@gmail.com escribió:
>>
>> 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 the error message.
>>
>>
>> >
>> > --
>> > 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...@googlegroups.com.
>> > To view this discussion on the web visit 
>> > https://groups.google.com/d/msgid/sage-support/CAAYgug8_g6%2BR3wqLdhFCYjKceqjOqstPLWLJNPSuReNZoT6a9w%40mail.gmail.com.
>
> --
> 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 
> https://groups.google.com/d/msgid/sage-support/7bbdfa0e-f895-48a3-9f88-1102cbbf2d71n%40googlegroups.com.

-- 
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 
https://groups.google.com/d/msgid/sage-support/CAAWYfq2MD-KdUj-H-MQMx-cSPTevPc1pqJs_HLLMq8Rwz1HhfA%40mail.gmail.com.

Re: [sage-support] Sage crash report

[Dima Pasechnik]

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 the error message.


>
> --
> 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 
> https://groups.google.com/d/msgid/sage-support/CAAYgug8_g6%2BR3wqLdhFCYjKceqjOqstPLWLJNPSuReNZoT6a9w%40mail.gmail.com.

-- 
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 
https://groups.google.com/d/msgid/sage-support/CAAWYfq0HnXKyzm69peLDxU-jNtpn149KKwjTtJL0psW_H3Wu_g%40mail.gmail.com.

Re: [sage-support] Sage Crash Report

[hbetx9]

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.

On Wednesday, September 1, 2021 at 2:27:46 PM UTC-5 hbetx9 wrote:

> 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 
>> 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 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 config/make that I can run on this directory to get it 
>>> to work as a system wide install?
>>>
>>> On Tuesday, August 31, 2021 at 4:22:10 PM UTC-5 Matthias Koeppe wrote:
>>>
 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 Ubuntu package.


 The latest binary for Linux (https://www.sagemath.org/download.html) 
 is Sage 9.3. If you are using this binary tarball, you will have to make 
 sure that the symlink python->python3 exists; there is a package that 
 provides it. See also 
 https://wiki.sagemath.org/ReleaseTours/sage-9.3#Availability_in_distributions_and_as_binaries

 The latest version is Sage 9.4. Using the source tarball, there is no 
 need to do anything about python/python3. Just follow the instructions in 
 the README. 

  

>>>

-- 
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 
https://groups.google.com/d/msgid/sage-support/024ab17b-41e5-4643-a0a7-c7c435b6266en%40googlegroups.com.

Re: [sage-support] Sage Crash Report

[hbetx9]

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 
> 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 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 config/make that I can run on this directory to get it 
>> to work as a system wide install?
>>
>> On Tuesday, August 31, 2021 at 4:22:10 PM UTC-5 Matthias Koeppe wrote:
>>
>>> 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 
 Ubuntu package.
>>>
>>>
>>> The latest binary for Linux (https://www.sagemath.org/download.html) is 
>>> Sage 9.3. If you are using this binary tarball, you will have to make sure 
>>> that the symlink python->python3 exists; there is a package that provides 
>>> it. See also 
>>> https://wiki.sagemath.org/ReleaseTours/sage-9.3#Availability_in_distributions_and_as_binaries
>>>
>>> The latest version is Sage 9.4. Using the source tarball, there is no 
>>> need to do anything about python/python3. Just follow the instructions in 
>>> the README. 
>>>
>>>  
>>>
>>

-- 
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 
https://groups.google.com/d/msgid/sage-support/3aec31b3-85a5-45f0-af52-1243a1b5b0afn%40googlegroups.com.

Re: [sage-support] Sage Crash Report

[Matthias Koeppe]

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 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 
> config/make that I can run on this directory to get it to work as a system 
> wide install?
>
> On Tuesday, August 31, 2021 at 4:22:10 PM UTC-5 Matthias Koeppe wrote:
>
>> 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 
>>> Ubuntu package.
>>
>>
>> The latest binary for Linux (https://www.sagemath.org/download.html) is 
>> Sage 9.3. If you are using this binary tarball, you will have to make sure 
>> that the symlink python->python3 exists; there is a package that provides 
>> it. See also 
>> https://wiki.sagemath.org/ReleaseTours/sage-9.3#Availability_in_distributions_and_as_binaries
>>
>> The latest version is Sage 9.4. Using the source tarball, there is no 
>> need to do anything about python/python3. Just follow the instructions in 
>> the README. 
>>
>>  
>>
>

-- 
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 
https://groups.google.com/d/msgid/sage-support/b8a59d1a-9c4a-4715-8ae6-f2df0a6c4877n%40googlegroups.com.

Re: [sage-support] Sage Crash Report

[hbetx9]

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 
config/make that I can run on this directory to get it to work as a system 
wide install?

On Tuesday, August 31, 2021 at 4:22:10 PM UTC-5 Matthias Koeppe wrote:

> 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 
>> Ubuntu package.
>
>
> The latest binary for Linux (https://www.sagemath.org/download.html) is 
> Sage 9.3. If you are using this binary tarball, you will have to make sure 
> that the symlink python->python3 exists; there is a package that provides 
> it. See also 
> https://wiki.sagemath.org/ReleaseTours/sage-9.3#Availability_in_distributions_and_as_binaries
>
> The latest version is Sage 9.4. Using the source tarball, there is no need 
> to do anything about python/python3. Just follow the instructions in the 
> README. 
>
>  
>

-- 
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 
https://groups.google.com/d/msgid/sage-support/546ebc75-e04c-4587-be1d-760018dab54en%40googlegroups.com.

Re: [sage-support] Sage Crash Report

[Matthias Koeppe]

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 
> Ubuntu package.


The latest binary for Linux (https://www.sagemath.org/download.html) is 
Sage 9.3. If you are using this binary tarball, you will have to make sure 
that the symlink python->python3 exists; there is a package that provides 
it. See 
also 
https://wiki.sagemath.org/ReleaseTours/sage-9.3#Availability_in_distributions_and_as_binaries

The latest version is Sage 9.4. Using the source tarball, there is no need 
to do anything about python/python3. Just follow the instructions in the 
README. 

 

-- 
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 
https://groups.google.com/d/msgid/sage-support/a16547b7-1dd7-4c5d-97fa-2e231cd702adn%40googlegroups.com.

Re: [sage-support] Sage Crash Report

[hbetx9]

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 wrote:

> 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 4:49:52 PM UTC-5 hbetx9 wrote:
>
>> 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' object is not callable; perhaps you missed a comma?
>>   raise TypeError('%s option must be a dictionary, not %s' (name, value))
>> /usr/lib/python3/dist-packages/sage/graphs/graph_latex.py:1168: 
>> SyntaxWarning: 'str' object is not callable; perhaps you missed a comma?
>>   raise TypeError('%s option must be a dictionary, not %s' (name, value))
>> /usr/lib/python3/dist-packages/sage/graphs/graph_latex.py:1175: 
>> SyntaxWarning: 'str' object is not callable; perhaps you missed a comma?
>>   raise TypeError('%s option must be a dictionary, not %s' (name, value))
>> /usr/lib/python3/dist-packages/sage/graphs/graph_latex.py:1182: 
>> SyntaxWarning: 'str' object is not callable; perhaps you missed a comma?
>>   raise TypeError('%s option must be a dictionary, not %s' (name, value))
>> /usr/lib/python3/dist-packages/sage/graphs/graph_latex.py:1189: 
>> SyntaxWarning: 'str' object is not callable; perhaps you missed a comma?
>>   raise TypeError('%s option must be a dictionary, not %s' (name, value))
>> /usr/lib/python3/dist-packages/sage/graphs/graph_latex.py:1196: 
>> SyntaxWarning: 'str' object is not callable; perhaps you missed a comma?
>>   raise TypeError('%s option must be a dictionary, not %s' (name, value))
>> /usr/lib/python3/dist-packages/sage/graphs/graph_latex.py:1203: 
>> SyntaxWarning: 'str' object is not callable; perhaps you missed a comma?
>>   raise TypeError('%s option must be a dictionary, not %s' (name, value))
>>
>> I think there is something about the way sage is trying to be installed 
>> and python, but I'm unsure how to diagnose. Installing from source is an 
>> option yes, but I fear it will have the same issue. 
>> On Sunday, August 29, 2021 at 2:14:38 AM UTC-5 dim...@gmail.com wrote:
>>
>>> 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 (uninstall and install 
>>> from source?) is appreciated: 
>>>
>>> This has to be reported to Linux Mint - we don't do packaging for 
>>> particular Linux distributions, and it looks like a packaging error, 
>>> not anything we can help with. 
>>> You can install Sage in several other ways: 
>>> https://doc.sagemath.org/html/en/installation/index.html 
>>>
>>> > 
>>> > 
>>> > 
>>> *** 
>>> > 
>>> > IPython post-mortem report 
>>> > 
>>> > {'commit_hash': '', 
>>> > 'commit_source': '(none found)', 
>>> > 'default_encoding': 'utf-8', 
>>> > 'ipython_path': '/usr/lib/python3/dist-packages/IPython', 
>>> > 'ipython_version': '7.13.0', 
>>> > 'os_name': 'posix', 
>>> > 'platform': 'Linux-5.4.0-81-generic-x86_64-with-glibc2.29', 
>>> > 'sys_executable': '/usr/bin/python3', 
>>> > 'sys_platform': 'linux', 
>>> > 'sys_version': '3.8.10 (default, Jun 2 2021, 10:49:15) \n[GCC 9.4.0]'} 
>>> > 
>>> > 
>>> *** 
>>> > 
>>> > 
>>> > 
>>> > 
>>> *** 
>>> > 
>>> > Crash traceback: 
>>> > 
>>> > 
>>> --- 
>>> > 
>>> --- 
>>> > ImportError Python 3.8.10: /usr/bin/python3 
>>> > Sat Aug 28 16:48:31 2021 
>>> > A problem occurred executing Python code. Here is the sequence of 
>>> function 
>>> > calls leading up to the error, with the most recent (innermost) call 
>>> last. 
>>> > /usr/share/sagemath/bin/sage-ipython in  
>>> > 1 #!/usr/bin/env sage-python 
>>> > 2 # -*- coding: utf-8 -*- 
>>> > 3 """ 
>>> > 4 Sage IPython startup script. 
>>> > 5 """ 
>>> > 6 
>>> > 7 # Display startup banner. Do this before anything else to give the 
>>> user 
>>> > 8 # early feedback that Sage is starting. 

Re: [sage-support] Sage Crash Report

[hbetx9]

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 4:49:52 PM UTC-5 hbetx9 wrote:

> 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' object is not callable; perhaps you missed a comma?
>   raise TypeError('%s option must be a dictionary, not %s' (name, value))
> /usr/lib/python3/dist-packages/sage/graphs/graph_latex.py:1168: 
> SyntaxWarning: 'str' object is not callable; perhaps you missed a comma?
>   raise TypeError('%s option must be a dictionary, not %s' (name, value))
> /usr/lib/python3/dist-packages/sage/graphs/graph_latex.py:1175: 
> SyntaxWarning: 'str' object is not callable; perhaps you missed a comma?
>   raise TypeError('%s option must be a dictionary, not %s' (name, value))
> /usr/lib/python3/dist-packages/sage/graphs/graph_latex.py:1182: 
> SyntaxWarning: 'str' object is not callable; perhaps you missed a comma?
>   raise TypeError('%s option must be a dictionary, not %s' (name, value))
> /usr/lib/python3/dist-packages/sage/graphs/graph_latex.py:1189: 
> SyntaxWarning: 'str' object is not callable; perhaps you missed a comma?
>   raise TypeError('%s option must be a dictionary, not %s' (name, value))
> /usr/lib/python3/dist-packages/sage/graphs/graph_latex.py:1196: 
> SyntaxWarning: 'str' object is not callable; perhaps you missed a comma?
>   raise TypeError('%s option must be a dictionary, not %s' (name, value))
> /usr/lib/python3/dist-packages/sage/graphs/graph_latex.py:1203: 
> SyntaxWarning: 'str' object is not callable; perhaps you missed a comma?
>   raise TypeError('%s option must be a dictionary, not %s' (name, value))
>
> I think there is something about the way sage is trying to be installed 
> and python, but I'm unsure how to diagnose. Installing from source is an 
> option yes, but I fear it will have the same issue. 
> On Sunday, August 29, 2021 at 2:14:38 AM UTC-5 dim...@gmail.com wrote:
>
>> 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 (uninstall and install 
>> from source?) is appreciated: 
>>
>> This has to be reported to Linux Mint - we don't do packaging for 
>> particular Linux distributions, and it looks like a packaging error, 
>> not anything we can help with. 
>> You can install Sage in several other ways: 
>> https://doc.sagemath.org/html/en/installation/index.html 
>>
>> > 
>> > 
>> > 
>> *** 
>> > 
>> > IPython post-mortem report 
>> > 
>> > {'commit_hash': '', 
>> > 'commit_source': '(none found)', 
>> > 'default_encoding': 'utf-8', 
>> > 'ipython_path': '/usr/lib/python3/dist-packages/IPython', 
>> > 'ipython_version': '7.13.0', 
>> > 'os_name': 'posix', 
>> > 'platform': 'Linux-5.4.0-81-generic-x86_64-with-glibc2.29', 
>> > 'sys_executable': '/usr/bin/python3', 
>> > 'sys_platform': 'linux', 
>> > 'sys_version': '3.8.10 (default, Jun 2 2021, 10:49:15) \n[GCC 9.4.0]'} 
>> > 
>> > 
>> *** 
>> > 
>> > 
>> > 
>> > 
>> *** 
>> > 
>> > Crash traceback: 
>> > 
>> > 
>> --- 
>> > 
>> --- 
>> > ImportError Python 3.8.10: /usr/bin/python3 
>> > Sat Aug 28 16:48:31 2021 
>> > A problem occurred executing Python code. Here is the sequence of 
>> function 
>> > calls leading up to the error, with the most recent (innermost) call 
>> last. 
>> > /usr/share/sagemath/bin/sage-ipython in  
>> > 1 #!/usr/bin/env sage-python 
>> > 2 # -*- coding: utf-8 -*- 
>> > 3 """ 
>> > 4 Sage IPython startup script. 
>> > 5 """ 
>> > 6 
>> > 7 # Display startup banner. Do this before anything else to give the 
>> user 
>> > 8 # early feedback that Sage is starting. 
>> > 9 from sage.misc.banner import banner 
>> > 10 banner() 
>> > 11 
>> > 12 from sage.repl.interpreter import SageTerminalApp 
>> > 13 
>> > 14 app = SageTerminalApp.instance() 
>> > ---> 15 app.initialize() 
>> > global app.initialize = > > 
>> > 16 app.start() 
>> > 
>> >  in 
>> initialize(self=, argv=None) 
>> > 
>> > /usr/lib/python3/dist-packages/traitlets/config/application.py in 
>> 

Re: [sage-support] Sage Crash Report

[hbetx9]

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' object is not callable; perhaps you missed a comma?
  raise TypeError('%s option must be a dictionary, not %s' (name, value))
/usr/lib/python3/dist-packages/sage/graphs/graph_latex.py:1168: 
SyntaxWarning: 'str' object is not callable; perhaps you missed a comma?
  raise TypeError('%s option must be a dictionary, not %s' (name, value))
/usr/lib/python3/dist-packages/sage/graphs/graph_latex.py:1175: 
SyntaxWarning: 'str' object is not callable; perhaps you missed a comma?
  raise TypeError('%s option must be a dictionary, not %s' (name, value))
/usr/lib/python3/dist-packages/sage/graphs/graph_latex.py:1182: 
SyntaxWarning: 'str' object is not callable; perhaps you missed a comma?
  raise TypeError('%s option must be a dictionary, not %s' (name, value))
/usr/lib/python3/dist-packages/sage/graphs/graph_latex.py:1189: 
SyntaxWarning: 'str' object is not callable; perhaps you missed a comma?
  raise TypeError('%s option must be a dictionary, not %s' (name, value))
/usr/lib/python3/dist-packages/sage/graphs/graph_latex.py:1196: 
SyntaxWarning: 'str' object is not callable; perhaps you missed a comma?
  raise TypeError('%s option must be a dictionary, not %s' (name, value))
/usr/lib/python3/dist-packages/sage/graphs/graph_latex.py:1203: 
SyntaxWarning: 'str' object is not callable; perhaps you missed a comma?
  raise TypeError('%s option must be a dictionary, not %s' (name, value))

I think there is something about the way sage is trying to be installed and 
python, but I'm unsure how to diagnose. Installing from source is an option 
yes, but I fear it will have the same issue. 
On Sunday, August 29, 2021 at 2:14:38 AM UTC-5 dim...@gmail.com wrote:

> 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 (uninstall and install 
> from source?) is appreciated:
>
> This has to be reported to Linux Mint - we don't do packaging for
> particular Linux distributions, and it looks like a packaging error,
> not anything we can help with.
> You can install Sage in several other ways:
> https://doc.sagemath.org/html/en/installation/index.html
>
> >
> >
> > 
> ***
> >
> > IPython post-mortem report
> >
> > {'commit_hash': '',
> > 'commit_source': '(none found)',
> > 'default_encoding': 'utf-8',
> > 'ipython_path': '/usr/lib/python3/dist-packages/IPython',
> > 'ipython_version': '7.13.0',
> > 'os_name': 'posix',
> > 'platform': 'Linux-5.4.0-81-generic-x86_64-with-glibc2.29',
> > 'sys_executable': '/usr/bin/python3',
> > 'sys_platform': 'linux',
> > 'sys_version': '3.8.10 (default, Jun 2 2021, 10:49:15) \n[GCC 9.4.0]'}
> >
> > 
> ***
> >
> >
> >
> > 
> ***
> >
> > Crash traceback:
> >
> > 
> ---
> > 
> ---
> > ImportError Python 3.8.10: /usr/bin/python3
> > Sat Aug 28 16:48:31 2021
> > A problem occurred executing Python code. Here is the sequence of 
> function
> > calls leading up to the error, with the most recent (innermost) call 
> last.
> > /usr/share/sagemath/bin/sage-ipython in 
> > 1 #!/usr/bin/env sage-python
> > 2 # -*- coding: utf-8 -*-
> > 3 """
> > 4 Sage IPython startup script.
> > 5 """
> > 6
> > 7 # Display startup banner. Do this before anything else to give the user
> > 8 # early feedback that Sage is starting.
> > 9 from sage.misc.banner import banner
> > 10 banner()
> > 11
> > 12 from sage.repl.interpreter import SageTerminalApp
> > 13
> > 14 app = SageTerminalApp.instance()
> > ---> 15 app.initialize()
> > global app.initialize =  >
> > 16 app.start()
> >
> >  in 
> initialize(self=, argv=None)
> >
> > /usr/lib/python3/dist-packages/traitlets/config/application.py in 
> catch_config_error(method=, 
> app=, *args=(None,), 
> **kwargs={})
> > 72 TRAITLETS_APPLICATION_RAISE_CONFIG_FILE_ERROR = False
> > 73 else:
> > 74 raise ValueError("Unsupported value for environment variable: 
> 'TRAITLETS_APPLICATION_RAISE_CONFIG_FILE_ERROR' is set to '%s' which is 
> none of {'0', '1', 'false', 'true', ''}."% _envvar )
> > 75
> > 76
> > 77 @decorator
> > 78 def catch_config_error(method, app, *args, **kwargs):
> > 79 """Method decorator for catching invalid config 
> (Trait/ArgumentErrors) during init.
> > 80
> > 81 On a 

Re: [sage-support] Sage Crash Report

[Dima Pasechnik]

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 (uninstall and install from 
> source?) is appreciated:

This has to be reported to Linux Mint - we don't do packaging for
particular Linux distributions, and it looks like a packaging error,
not anything we can help with.
You can install Sage in several other ways:
https://doc.sagemath.org/html/en/installation/index.html

>
>
> ***
>
> IPython post-mortem report
>
> {'commit_hash': '',
>  'commit_source': '(none found)',
>  'default_encoding': 'utf-8',
>  'ipython_path': '/usr/lib/python3/dist-packages/IPython',
>  'ipython_version': '7.13.0',
>  'os_name': 'posix',
>  'platform': 'Linux-5.4.0-81-generic-x86_64-with-glibc2.29',
>  'sys_executable': '/usr/bin/python3',
>  'sys_platform': 'linux',
>  'sys_version': '3.8.10 (default, Jun  2 2021, 10:49:15) \n[GCC 9.4.0]'}
>
> ***
>
>
>
> ***
>
> Crash traceback:
>
> ---
> ---
> ImportError Python 3.8.10: /usr/bin/python3
>Sat Aug 28 16:48:31 2021
> A problem occurred executing Python code.  Here is the sequence of function
> calls leading up to the error, with the most recent (innermost) call last.
> /usr/share/sagemath/bin/sage-ipython in 
>   1 #!/usr/bin/env sage-python
>   2 # -*- coding: utf-8 -*-
>   3 """
>   4 Sage IPython startup script.
>   5 """
>   6
>   7 # Display startup banner. Do this before anything else to give the 
> user
>   8 # early feedback that Sage is starting.
>   9 from sage.misc.banner import banner
>  10 banner()
>  11
>  12 from sage.repl.interpreter import SageTerminalApp
>  13
>  14 app = SageTerminalApp.instance()
> ---> 15 app.initialize()
> global app.initialize =  of >
>  16 app.start()
>
>  in initialize(self= object>, argv=None)
>
> /usr/lib/python3/dist-packages/traitlets/config/application.py in 
> catch_config_error(method=, 
> app=, *args=(None,), 
> **kwargs={})
>  72 TRAITLETS_APPLICATION_RAISE_CONFIG_FILE_ERROR = False
>  73 else:
>  74 raise ValueError("Unsupported value for environment variable: 
> 'TRAITLETS_APPLICATION_RAISE_CONFIG_FILE_ERROR' is set to '%s' which is none 
> of  {'0', '1', 'false', 'true', ''}."% _envvar )
>  75
>  76
>  77 @decorator
>  78 def catch_config_error(method, app, *args, **kwargs):
>  79 """Method decorator for catching invalid config 
> (Trait/ArgumentErrors) during init.
>  80
>  81 On a TraitError (generally caused by bad config), this will print 
> the trait's
>  82 message, and exit the app.
>  83
>  84 For use on init methods, to prevent invoking excepthook on 
> invalid input.
>  85 """
>  86 try:
> ---> 87 return method(app, *args, **kwargs)
> method = 
> app = 
> args = (None,)
> kwargs = {}
>  88 except (TraitError, ArgumentError) as e:
>  89 app.print_help()
>  90 app.log.fatal("Bad config encountered during initialization:")
>  91 app.log.fatal(str(e))
>  92 app.log.debug("Config at the time: %s", app.config)
>  93 app.exit(1)
>  94
>  95
>  96 class ApplicationError(Exception):
>  97 pass
>  98
>  99
> 100 class LevelFormatter(logging.Formatter):
> 101 """Formatter with additional `highlevel` record
> 102
>
> /usr/lib/python3/dist-packages/IPython/terminal/ipapp.py in 
> initialize(self=, argv=None)
> 302
> 303 return super(TerminalIPythonApp, 
> self).parse_command_line(argv)
> 304
> 305 @catch_config_error
> 306 def initialize(self, argv=None):
> 307 """Do actions after construct, but before starting the app."""
> 308 super(TerminalIPythonApp, self).initialize(argv)
> 309 if self.subapp is not None:
> 310 # don't bother initializing further, starting subapp
> 311 return
> 312 # print self.extra_args
> 313 if self.extra_args and not self.something_to_run:
> 314 self.file_to_run = self.extra_args[0]
> 315 self.init_path()
> 316 # create the shell
> --> 317 self.init_shell()
> self.init_shell =  >
> 318 # and draw the banner
> 319 

Re: [sage-support] Sage Crash Report

[Dima Pasechnik]

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 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- 
> pari-doc- sagemath-doc-
>
> (afterwards I did
>
> sudo apt install jupyter
>
> and
>
> sudo apt install sagemath-jupyter
>
> everything was working fine)
>
>
> Today I installed Blender
>
>   sudo add-apt-repository ppa:savoury1/ffmpeg4
>
>   sudo add-apt-repository ppa:savoury1/blender
>
>   sudo apt-get update
>
>   sudo apt-get upgrade && sudo apt-get dist-upgrade
>
>   sudo apt-get install blender
>
>
> Afterwards
> I tried the command
>
> maxima('plotdf([-y,-x],[x,y],[x,-2,2],[y,-2,2])')
>
> in the jupyter notebook and I got a missing Kernel error
>
> afterwards the kernel would not restart successfully and I restarted my
> computer.
>
>
> Then I run
>
> sage
>
> in the terminal, which generated this crash report.
>
> Currently, Sage is not working anymore on my computer.
>
>
> There are strange things about python and numpy written in Blender's ppa
> description. I attach this description too (see lines 23 and 43).
>
> I checked the result of python3 --version in the terminal and got
>
> Python 3.8.10
>
>
> Any hint towards the resolution of this sad situation is welcome.
>
> Thanks fo your work on Sage.
>
>
> Best,
>
> Gaël Cousin.
>
>
>
>
> --
> 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
> https://groups.google.com/d/msgid/sage-support/4600086d-51fa-f96c-c725-08ad013ab42c%40gmail.com
> 
> .
>

-- 
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 
https://groups.google.com/d/msgid/sage-support/CAAWYfq1LP5cvFuWm46-_GML7JV0YRxDBddhd_C51BGv2fs%2BBpA%40mail.gmail.com.

Re: [sage-support] Sage Crash Report

[Mike Lee]

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 
wrote:

> 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 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.)
>>
>> Isuru
>>
>> On Wed, Mar 24, 2021 at 9:07 AM Mike Lee  wrote:
>>
>>> 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
 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!

 On Wed, Mar 24, 2021 at 5:41 AM Dima Pasechnik 
 wrote:

> 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:
> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/
> matrix_modn_sparse.cpython-39-x86_64-linux-gnu.so: undefined symbol:
> _ZNK6Givaro7IntegercvNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEB5cxx11Ev'
>
> this is, demangled:
>
> $ c++filt
> _ZNK6Givaro7IntegercvNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEB5cxx11Ev
> Givaro::Integer::operator std::__cxx11::basic_string std::char_traits, std::allocator >[abi:cxx11]() const
>
> Can you find this in the output of
>
> $ nm -D --demangle
> /home/msl/software/miniconda3/envs/sage/lib/libgivaro.so.9
>
> Perhaps, wrong C++ standard version chosen somewhere?
>
> Maybe Isuru knows what's wrong there.
>
> >
> > What could I do to fix this issue? Thank you in advance for the help!
> >
> > By the way, when I run 'ldd
> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/
> matrix_modn_sparse.cpython-39-x86_64-linux-gnu.so ' I get the
> following output:
> >
> > linux-vdso.so.1 (0x7ffde17a7000)
> > liblinbox.so.0 =>
> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../../liblinbox.so.0
> (0x7fa325ba)
> > libfflas.so.1 =>
> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../../libfflas.so.1
> (0x7fa325ad4000)
> > libblas.so.3 =>
> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../../libblas.so.3
> (0x7fa323ae3000)
> > libgivaro.so.9 =>
> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../../libgivaro.so.9
> (0x7fa323a88000)
> > libflint.so.14 =>
> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../../libflint.so.14
> (0x7fa32320d000)
> > libntl.so.43 =>
> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../../libntl.so.43
> (0x7fa322fca000)
> > libgmp.so.10 =>
> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../../libgmp.so.10
> (0x7fa322f24000)
> > libstdc++.so.6 =>
> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../../libstdc++.so.6
> (0x7fa322daf000)
> > libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7fa3229fb000)
> > libgcc_s.so.1 =>
> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../../libgcc_s.so.1
> (0x7fa3229e7000)
> > libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fa3225f6000)
> > libffpack.so.1 =>
> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../.././libffpack.so.1
> (0x7fa3224e3000)
> > libgmpxx.so.4 =>
> 

Re: [sage-support] Sage Crash Report

[Mariusz Sokolowski]

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 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.)
>
> Isuru
>
> On Wed, Mar 24, 2021 at 9:07 AM Mike Lee  wrote:
>
>> 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 
>>> 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!
>>>
>>> On Wed, Mar 24, 2021 at 5:41 AM Dima Pasechnik  wrote:
>>>
 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: 
 /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/
 matrix_modn_sparse.cpython-39-x86_64-linux-gnu.so: undefined symbol: 
 _ZNK6Givaro7IntegercvNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEB5cxx11Ev'

 this is, demangled:

 $ c++filt 
 _ZNK6Givaro7IntegercvNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEB5cxx11Ev
 Givaro::Integer::operator std::__cxx11::basic_string>>> std::char_traits, std::allocator >[abi:cxx11]() const

 Can you find this in the output of

 $ nm -D --demangle 
 /home/msl/software/miniconda3/envs/sage/lib/libgivaro.so.9

 Perhaps, wrong C++ standard version chosen somewhere?

 Maybe Isuru knows what's wrong there.

 >
 > What could I do to fix this issue? Thank you in advance for the help!
 >
 > By the way, when I run 'ldd 
 /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/
 matrix_modn_sparse.cpython-39-x86_64-linux-gnu.so ' I get the 
 following output:
 >
 > linux-vdso.so.1 (0x7ffde17a7000)
 > liblinbox.so.0 => 
 /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../../liblinbox.so.0
  
 (0x7fa325ba)
 > libfflas.so.1 => 
 /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../../libfflas.so.1
  
 (0x7fa325ad4000)
 > libblas.so.3 => 
 /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../../libblas.so.3
  
 (0x7fa323ae3000)
 > libgivaro.so.9 => 
 /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../../libgivaro.so.9
  
 (0x7fa323a88000)
 > libflint.so.14 => 
 /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../../libflint.so.14
  
 (0x7fa32320d000)
 > libntl.so.43 => 
 /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../../libntl.so.43
  
 (0x7fa322fca000)
 > libgmp.so.10 => 
 /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../../libgmp.so.10
  
 (0x7fa322f24000)
 > libstdc++.so.6 => 
 /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../../libstdc++.so.6
  
 (0x7fa322daf000)
 > libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7fa3229fb000)
 > libgcc_s.so.1 => 
 /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../../libgcc_s.so.1
  
 (0x7fa3229e7000)
 > libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fa3225f6000)
 > libffpack.so.1 => 
 /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../.././libffpack.so.1
  
 (0x7fa3224e3000)
 > libgmpxx.so.4 => 
 /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../.././libgmpxx.so.4
  
 (0x7fa3224da000)
 > libmpfr.so.6 => 
 /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../.././libmpfr.so.6
  
 (0x7fa32245b000)
 > libiml.so.0 => 
 

Re: [sage-support] Sage Crash Report

[Isuru Fernando]

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.)

Isuru

On Wed, Mar 24, 2021 at 9:07 AM Mike Lee  wrote:

> 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
>> 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!
>>
>> On Wed, Mar 24, 2021 at 5:41 AM Dima Pasechnik  wrote:
>>
>>> 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:
>>> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/
>>> matrix_modn_sparse.cpython-39-x86_64-linux-gnu.so: undefined symbol:
>>> _ZNK6Givaro7IntegercvNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEB5cxx11Ev'
>>>
>>> this is, demangled:
>>>
>>> $ c++filt
>>> _ZNK6Givaro7IntegercvNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEB5cxx11Ev
>>> Givaro::Integer::operator std::__cxx11::basic_string>> std::char_traits, std::allocator >[abi:cxx11]() const
>>>
>>> Can you find this in the output of
>>>
>>> $ nm -D --demangle
>>> /home/msl/software/miniconda3/envs/sage/lib/libgivaro.so.9
>>>
>>> Perhaps, wrong C++ standard version chosen somewhere?
>>>
>>> Maybe Isuru knows what's wrong there.
>>>
>>> >
>>> > What could I do to fix this issue? Thank you in advance for the help!
>>> >
>>> > By the way, when I run 'ldd
>>> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/
>>> matrix_modn_sparse.cpython-39-x86_64-linux-gnu.so ' I get the following
>>> output:
>>> >
>>> > linux-vdso.so.1 (0x7ffde17a7000)
>>> > liblinbox.so.0 =>
>>> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../../liblinbox.so.0
>>> (0x7fa325ba)
>>> > libfflas.so.1 =>
>>> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../../libfflas.so.1
>>> (0x7fa325ad4000)
>>> > libblas.so.3 =>
>>> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../../libblas.so.3
>>> (0x7fa323ae3000)
>>> > libgivaro.so.9 =>
>>> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../../libgivaro.so.9
>>> (0x7fa323a88000)
>>> > libflint.so.14 =>
>>> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../../libflint.so.14
>>> (0x7fa32320d000)
>>> > libntl.so.43 =>
>>> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../../libntl.so.43
>>> (0x7fa322fca000)
>>> > libgmp.so.10 =>
>>> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../../libgmp.so.10
>>> (0x7fa322f24000)
>>> > libstdc++.so.6 =>
>>> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../../libstdc++.so.6
>>> (0x7fa322daf000)
>>> > libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7fa3229fb000)
>>> > libgcc_s.so.1 =>
>>> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../../libgcc_s.so.1
>>> (0x7fa3229e7000)
>>> > libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fa3225f6000)
>>> > libffpack.so.1 =>
>>> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../.././libffpack.so.1
>>> (0x7fa3224e3000)
>>> > libgmpxx.so.4 =>
>>> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../.././libgmpxx.so.4
>>> (0x7fa3224da000)
>>> > libmpfr.so.6 =>
>>> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../.././libmpfr.so.6
>>> (0x7fa32245b000)
>>> > libiml.so.0 =>
>>> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../.././libiml.so.0
>>> (0x7fa322436000)
>>> > libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
>>> (0x7fa322217000)
>>> > libgfortran.so.5 =>
>>> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../.././libgfortran.so.5
>>> (0x7fa322075000)
>>> > /lib64/ld-linux-x86-64.so.2 (0x7fa325aa8000)
>>> > libgf2x.so.3 =>
>>> 

Re: [sage-support] Sage Crash Report

[Mike Lee]

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
> 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!
>
> On Wed, Mar 24, 2021 at 5:41 AM Dima Pasechnik  wrote:
>
>> 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:
>> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/
>> matrix_modn_sparse.cpython-39-x86_64-linux-gnu.so: undefined symbol:
>> _ZNK6Givaro7IntegercvNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEB5cxx11Ev'
>>
>> this is, demangled:
>>
>> $ c++filt
>> _ZNK6Givaro7IntegercvNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEB5cxx11Ev
>> Givaro::Integer::operator std::__cxx11::basic_string> std::char_traits, std::allocator >[abi:cxx11]() const
>>
>> Can you find this in the output of
>>
>> $ nm -D --demangle
>> /home/msl/software/miniconda3/envs/sage/lib/libgivaro.so.9
>>
>> Perhaps, wrong C++ standard version chosen somewhere?
>>
>> Maybe Isuru knows what's wrong there.
>>
>> >
>> > What could I do to fix this issue? Thank you in advance for the help!
>> >
>> > By the way, when I run 'ldd
>> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/
>> matrix_modn_sparse.cpython-39-x86_64-linux-gnu.so ' I get the following
>> output:
>> >
>> > linux-vdso.so.1 (0x7ffde17a7000)
>> > liblinbox.so.0 =>
>> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../../liblinbox.so.0
>> (0x7fa325ba)
>> > libfflas.so.1 =>
>> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../../libfflas.so.1
>> (0x7fa325ad4000)
>> > libblas.so.3 =>
>> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../../libblas.so.3
>> (0x7fa323ae3000)
>> > libgivaro.so.9 =>
>> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../../libgivaro.so.9
>> (0x7fa323a88000)
>> > libflint.so.14 =>
>> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../../libflint.so.14
>> (0x7fa32320d000)
>> > libntl.so.43 =>
>> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../../libntl.so.43
>> (0x7fa322fca000)
>> > libgmp.so.10 =>
>> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../../libgmp.so.10
>> (0x7fa322f24000)
>> > libstdc++.so.6 =>
>> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../../libstdc++.so.6
>> (0x7fa322daf000)
>> > libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7fa3229fb000)
>> > libgcc_s.so.1 =>
>> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../../libgcc_s.so.1
>> (0x7fa3229e7000)
>> > libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fa3225f6000)
>> > libffpack.so.1 =>
>> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../.././libffpack.so.1
>> (0x7fa3224e3000)
>> > libgmpxx.so.4 =>
>> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../.././libgmpxx.so.4
>> (0x7fa3224da000)
>> > libmpfr.so.6 =>
>> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../.././libmpfr.so.6
>> (0x7fa32245b000)
>> > libiml.so.0 =>
>> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../.././libiml.so.0
>> (0x7fa322436000)
>> > libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
>> (0x7fa322217000)
>> > libgfortran.so.5 =>
>> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../.././libgfortran.so.5
>> (0x7fa322075000)
>> > /lib64/ld-linux-x86-64.so.2 (0x7fa325aa8000)
>> > libgf2x.so.3 =>
>> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../.././libgf2x.so.3
>> (0x7fa322062000)
>> > libquadmath.so.0 =>
>> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../.././libquadmath.so.0
>> (0x7fa322028000)
>> >
>> > Mike
>> >
>> > On Sunday, January 24, 2021 at 1:16:24 PM UTC-5 dim...@gmail.com wrote:
>> >>
>> >> at the bottom of the log you see
>> >>
>> >> ImportError:
>> 

Re: [sage-support] Sage Crash Report

[Mike Lee]

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!

On Wed, Mar 24, 2021 at 5:41 AM Dima Pasechnik  wrote:

> 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:
> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/
> matrix_modn_sparse.cpython-39-x86_64-linux-gnu.so: undefined symbol:
> _ZNK6Givaro7IntegercvNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEB5cxx11Ev'
>
> this is, demangled:
>
> $ c++filt
> _ZNK6Givaro7IntegercvNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEB5cxx11Ev
> Givaro::Integer::operator std::__cxx11::basic_string std::char_traits, std::allocator >[abi:cxx11]() const
>
> Can you find this in the output of
>
> $ nm -D --demangle
> /home/msl/software/miniconda3/envs/sage/lib/libgivaro.so.9
>
> Perhaps, wrong C++ standard version chosen somewhere?
>
> Maybe Isuru knows what's wrong there.
>
> >
> > What could I do to fix this issue? Thank you in advance for the help!
> >
> > By the way, when I run 'ldd
> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/
> matrix_modn_sparse.cpython-39-x86_64-linux-gnu.so ' I get the following
> output:
> >
> > linux-vdso.so.1 (0x7ffde17a7000)
> > liblinbox.so.0 =>
> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../../liblinbox.so.0
> (0x7fa325ba)
> > libfflas.so.1 =>
> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../../libfflas.so.1
> (0x7fa325ad4000)
> > libblas.so.3 =>
> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../../libblas.so.3
> (0x7fa323ae3000)
> > libgivaro.so.9 =>
> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../../libgivaro.so.9
> (0x7fa323a88000)
> > libflint.so.14 =>
> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../../libflint.so.14
> (0x7fa32320d000)
> > libntl.so.43 =>
> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../../libntl.so.43
> (0x7fa322fca000)
> > libgmp.so.10 =>
> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../../libgmp.so.10
> (0x7fa322f24000)
> > libstdc++.so.6 =>
> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../../libstdc++.so.6
> (0x7fa322daf000)
> > libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7fa3229fb000)
> > libgcc_s.so.1 =>
> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../../libgcc_s.so.1
> (0x7fa3229e7000)
> > libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fa3225f6000)
> > libffpack.so.1 =>
> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../.././libffpack.so.1
> (0x7fa3224e3000)
> > libgmpxx.so.4 =>
> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../.././libgmpxx.so.4
> (0x7fa3224da000)
> > libmpfr.so.6 =>
> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../.././libmpfr.so.6
> (0x7fa32245b000)
> > libiml.so.0 =>
> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../.././libiml.so.0
> (0x7fa322436000)
> > libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
> (0x7fa322217000)
> > libgfortran.so.5 =>
> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../.././libgfortran.so.5
> (0x7fa322075000)
> > /lib64/ld-linux-x86-64.so.2 (0x7fa325aa8000)
> > libgf2x.so.3 =>
> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../.././libgf2x.so.3
> (0x7fa322062000)
> > libquadmath.so.0 =>
> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../.././libquadmath.so.0
> (0x7fa322028000)
> >
> > Mike
> >
> > On Sunday, January 24, 2021 at 1:16:24 PM UTC-5 dim...@gmail.com wrote:
> >>
> >> 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 that something went wrong with linking givaro.
> >> E.g. you might be linking to a system-wide
> >> installed givaro, but it's expected to 

Re: [sage-support] Sage Crash Report

[Dima Pasechnik]

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: 
> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/matrix_modn_sparse.cpython-39-x86_64-linux-gnu.so:
>  undefined symbol: 
> _ZNK6Givaro7IntegercvNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEB5cxx11Ev'

this is, demangled:

$ c++filt 
_ZNK6Givaro7IntegercvNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEB5cxx11Ev
Givaro::Integer::operator std::__cxx11::basic_string, std::allocator >[abi:cxx11]() const

Can you find this in the output of

$ nm -D --demangle /home/msl/software/miniconda3/envs/sage/lib/libgivaro.so.9

Perhaps, wrong C++ standard version chosen somewhere?

Maybe Isuru knows what's wrong there.

>
> What could I do to fix this issue? Thank you in advance for the help!
>
> By the way, when I run 'ldd 
> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/matrix_modn_sparse.cpython-39-x86_64-linux-gnu.so
>  ' I get the following output:
>
> linux-vdso.so.1 (0x7ffde17a7000)
> liblinbox.so.0 => 
> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../../liblinbox.so.0
>  (0x7fa325ba)
> libfflas.so.1 => 
> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../../libfflas.so.1
>  (0x7fa325ad4000)
> libblas.so.3 => 
> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../../libblas.so.3
>  (0x7fa323ae3000)
> libgivaro.so.9 => 
> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../../libgivaro.so.9
>  (0x7fa323a88000)
> libflint.so.14 => 
> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../../libflint.so.14
>  (0x7fa32320d000)
> libntl.so.43 => 
> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../../libntl.so.43
>  (0x7fa322fca000)
> libgmp.so.10 => 
> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../../libgmp.so.10
>  (0x7fa322f24000)
> libstdc++.so.6 => 
> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../../libstdc++.so.6
>  (0x7fa322daf000)
> libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7fa3229fb000)
> libgcc_s.so.1 => 
> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../../libgcc_s.so.1
>  (0x7fa3229e7000)
> libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fa3225f6000)
> libffpack.so.1 => 
> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../.././libffpack.so.1
>  (0x7fa3224e3000)
> libgmpxx.so.4 => 
> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../.././libgmpxx.so.4
>  (0x7fa3224da000)
> libmpfr.so.6 => 
> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../.././libmpfr.so.6
>  (0x7fa32245b000)
> libiml.so.0 => 
> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../.././libiml.so.0
>  (0x7fa322436000)
> libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x7fa322217000)
> libgfortran.so.5 => 
> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../.././libgfortran.so.5
>  (0x7fa322075000)
> /lib64/ld-linux-x86-64.so.2 (0x7fa325aa8000)
> libgf2x.so.3 => 
> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../.././libgf2x.so.3
>  (0x7fa322062000)
> libquadmath.so.0 => 
> /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../.././libquadmath.so.0
>  (0x7fa322028000)
>
> Mike
>
> On Sunday, January 24, 2021 at 1:16:24 PM UTC-5 dim...@gmail.com wrote:
>>
>> 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 that something went wrong with linking givaro.
>> E.g. you might be linking to a system-wide
>> installed givaro, but it's expected to be the one built by Sage -
>> whether the latter is the case can be found out in the top-level
>> config.log.
>>
>> What is the output of
>>
>> ldd 
>> /home/mathieu/opt/SageMath/local/lib/python3.8/site-packages/sage/matrix/matrix_modn_sparse.cpython-38-x86_64-linux-gnu.so
>>
>> ?
>>
>>
>> On Sun, Jan 24, 2021 at 4:22 PM Mathieu Dutour  wrote:
>> >
>> >
>> > --
>> > You received this message because you are subscribed to the Google Groups 
>> > 

Re: [sage-support] Sage Crash Report

[Mike Lee]

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: 
/home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/matrix_modn_sparse.cpython-39-x86_64-linux-gnu.so:
 
undefined symbol: 
_ZNK6Givaro7IntegercvNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEB5cxx11Ev'

What could I do to fix this issue? Thank you in advance for the help!

By the way, when I run 'ldd 
/home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/matrix_modn_sparse.cpython-39-x86_64-linux-gnu.so
 
' I get the following output:

linux-vdso.so.1 (0x7ffde17a7000)
liblinbox.so.0 => 
/home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../../liblinbox.so.0
 
(0x7fa325ba)
libfflas.so.1 => 
/home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../../libfflas.so.1
 
(0x7fa325ad4000)
libblas.so.3 => 
/home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../../libblas.so.3
 
(0x7fa323ae3000)
libgivaro.so.9 => 
/home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../../libgivaro.so.9
 
(0x7fa323a88000)
libflint.so.14 => 
/home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../../libflint.so.14
 
(0x7fa32320d000)
libntl.so.43 => 
/home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../../libntl.so.43
 
(0x7fa322fca000)
libgmp.so.10 => 
/home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../../libgmp.so.10
 
(0x7fa322f24000)
libstdc++.so.6 => 
/home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../../libstdc++.so.6
 
(0x7fa322daf000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7fa3229fb000)
libgcc_s.so.1 => 
/home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../../libgcc_s.so.1
 
(0x7fa3229e7000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fa3225f6000)
libffpack.so.1 => 
/home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../.././libffpack.so.1
 
(0x7fa3224e3000)
libgmpxx.so.4 => 
/home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../.././libgmpxx.so.4
 
(0x7fa3224da000)
libmpfr.so.6 => 
/home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../.././libmpfr.so.6
 
(0x7fa32245b000)
libiml.so.0 => 
/home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../.././libiml.so.0
 
(0x7fa322436000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7fa322217000)
libgfortran.so.5 => 
/home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../.././libgfortran.so.5
 
(0x7fa322075000)
/lib64/ld-linux-x86-64.so.2 (0x7fa325aa8000)
libgf2x.so.3 => 
/home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../.././libgf2x.so.3
 
(0x7fa322062000)
libquadmath.so.0 => 
/home/msl/software/miniconda3/envs/sage/lib/python3.9/site-packages/sage/matrix/../../../.././libquadmath.so.0
 
(0x7fa322028000)

Mike

On Sunday, January 24, 2021 at 1:16:24 PM UTC-5 dim...@gmail.com wrote:

> 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 that something went wrong with linking givaro.
> E.g. you might be linking to a system-wide
> installed givaro, but it's expected to be the one built by Sage -
> whether the latter is the case can be found out in the top-level
> config.log.
>
> What is the output of
>
> ldd 
> /home/mathieu/opt/SageMath/local/lib/python3.8/site-packages/sage/matrix/
> matrix_modn_sparse.cpython-38-x86_64-linux-gnu.so
>
> ?
>
>
> On Sun, Jan 24, 2021 at 4:22 PM Mathieu Dutour  
> wrote:
> >
> >
> > --
> > 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...@googlegroups.com.
> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-support/CADm_teOrk03gf8bzyUxtvt9m16wEAP3%2BOsfkzxbjSjz4VN9bKw%40mail.gmail.com
> .
>

-- 
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 

Re: [sage-support] Sage Crash Report

[Dima Pasechnik]

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 that something went wrong with linking givaro.
E.g. you might be linking to a system-wide
installed givaro, but it's expected to be the one built by Sage -
whether the latter is the case can be found out in the top-level
config.log.

What is the output of

ldd 
/home/mathieu/opt/SageMath/local/lib/python3.8/site-packages/sage/matrix/matrix_modn_sparse.cpython-38-x86_64-linux-gnu.so

?


On Sun, Jan 24, 2021 at 4:22 PM Mathieu Dutour  wrote:
>
>
> --
> 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 
> https://groups.google.com/d/msgid/sage-support/CADm_teOrk03gf8bzyUxtvt9m16wEAP3%2BOsfkzxbjSjz4VN9bKw%40mail.gmail.com.

-- 
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 
https://groups.google.com/d/msgid/sage-support/CAAWYfq0t31jRmd00TZ%3DMCD_ROqjb8i-Jm358NPXSur62WWhhLQ%40mail.gmail.com.

Re: [sage-support] Sage Crash Report

[Dima Pasechnik]

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 crash report you
> attached:
> ImportError: libntl.so.35: cannot open shared object file: No such file
> or directory

indeed, this is to be expected - an OS update updates libraries your
application is built against, and so
it needs to be re-linked.


>
>
>
> Le 23/04/2020 à 15:10, Soufiane Lakhlifi a écrit :
> > 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
> > http://doc.sagemath.org/html/en/installation/source.html.
> >  No special flags were used except to change the build directory.
> > -The crash happened by lunching sage (with no arguments) from the terminal,
> >  it is worth noting that the crash happened just after I upgraded my Ubuntu
> > from
> >  19.10 to 20.10.
> >
> > Best regards,
> > Soufiane Lakhlifi.
> > Zone contenant les pièces jointes
> >
>
> --
> 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 
> https://groups.google.com/d/msgid/sage-support/31ae06a6-0ace-d577-6d46-ce5e16ca7073%40uca.fr.

-- 
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 
https://groups.google.com/d/msgid/sage-support/CAAWYfq1tie20oSyrJXs3ddSzVfRE-UvaDg7TKWci8CX0ENL1Zg%40mail.gmail.com.

Re: [sage-support] Sage Crash Report

[Jean-Florent Raymond]

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 object file: No such file
or directory



Le 23/04/2020 à 15:10, Soufiane Lakhlifi a écrit :
> 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
> http://doc.sagemath.org/html/en/installation/source.html.
>  No special flags were used except to change the build directory.
> -The crash happened by lunching sage (with no arguments) from the terminal,
>  it is worth noting that the crash happened just after I upgraded my Ubuntu
> from
>  19.10 to 20.10.
> 
> Best regards,
> Soufiane Lakhlifi.
> Zone contenant les pièces jointes
> 

-- 
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 
https://groups.google.com/d/msgid/sage-support/31ae06a6-0ace-d577-6d46-ce5e16ca7073%40uca.fr.

Re: [sage-support] Sage Crash Report

[HANG HUANG]

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
> 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 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 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 install from source code as the installing from pre-built
>>> binaries also gives me some other error. I was able  to run ./configure
>>> without any issues and then when i did make, I received the following log
>>> file (attached) and error:
>>> >
>>> > Error building Sage.
>>> >
>>> > The following package(s) may have failed to build (not necessarily
>>> > during this run of 'make all-start'):
>>> >
>>> > * package: flint-2.5.2.p5
>>> >   log file:
>>> /scratch/user/hhuang235/sage-9.0/logs/pkgs/flint-2.5.2.p5.log
>>> >   build directory:
>>> /scratch/user/hhuang235/sage-9.0/local/var/tmp/sage/build/flint-2.5.2.p5
>>> >
>>> > 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[1]: *** [all-start] Error 1
>>> > make[1]: Leaving directory `/scratch/user/hhuang235/sage-9.0'
>>> > make: *** [all] Error 2
>>>
>>> Checking the log file for flint that you attached, there is this:
>>>
>>> ccache: error: Failed to create temporary file for
>>> /home/hhuang235/.ccache/2/9/8e02d78d68b9638edd65c3e5744171-2001.manifest.tmp:
>>> Disk quota exceeded
>>>
>>> I think that should explain the problem you are having.  Is the “scratch
>>> folder” on a disk of small size, or does it have a small amount of free
>>> space?  The source build of Sage does take a lot of space.  On my system,
>>> Sage 9.0 uses about 7.5 GB (when complete).
>>>
>>> HTH
>>>
>>> Justin
>>>
>>> --
>>> Justin C. Walker
>>> Curmudgeon-at-large
>>> Director
>>> Institute for the Absorption of Federal Funds
>>> 
>>> 186,000 Miles per Second
>>> Not just a good idea:
>>>   it's the law!
>>> 
>>>
>>> --
>>> 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
>>> https://groups.google.com/d/msgid/sage-support/8F194F5B-3706-4290-AB20-9E16425014D4%40mac.com
>>> .
>>>
>> --
>> 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
>> https://groups.google.com/d/msgid/sage-support/CADTeGQetEtmqpEKvGXQ-Y6tOHqUaVX_NMdBQnVXqwv%3Dq7Kxr7A%40mail.gmail.com
>> 
>> .
>>
> --
> 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
> https://groups.google.com/d/msgid/sage-support/CA%2B01voOSBEF-8L3NkKreYmK3HTC808pjE2Ni4ss3n5DwMY%2B1HA%40mail.gmail.com
> 
> .
>

-- 
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 
https://groups.google.com/d/msgid/sage-support/CADTeGQcFJSmsYZR7ViQe1iwq6-5bd8WWz_kSSQZGv%3DneGGuiSw%40mail.gmail.com.
Found local metadata for xz-5.2.2.p0
Using cached file /scratch/user/hhuang235/sage-9.0/upstream/xz-5.2.2.tar.gz
xz-5.2.2.p0

Setting up build 

Re: [sage-support] Sage Crash Report

[Isuru Fernando]

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 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 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 install from source code as the installing from pre-built
>> binaries also gives me some other error. I was able  to run ./configure
>> without any issues and then when i did make, I received the following log
>> file (attached) and error:
>> >
>> > Error building Sage.
>> >
>> > The following package(s) may have failed to build (not necessarily
>> > during this run of 'make all-start'):
>> >
>> > * package: flint-2.5.2.p5
>> >   log file:
>> /scratch/user/hhuang235/sage-9.0/logs/pkgs/flint-2.5.2.p5.log
>> >   build directory:
>> /scratch/user/hhuang235/sage-9.0/local/var/tmp/sage/build/flint-2.5.2.p5
>> >
>> > 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[1]: *** [all-start] Error 1
>> > make[1]: Leaving directory `/scratch/user/hhuang235/sage-9.0'
>> > make: *** [all] Error 2
>>
>> Checking the log file for flint that you attached, there is this:
>>
>> ccache: error: Failed to create temporary file for
>> /home/hhuang235/.ccache/2/9/8e02d78d68b9638edd65c3e5744171-2001.manifest.tmp:
>> Disk quota exceeded
>>
>> I think that should explain the problem you are having.  Is the “scratch
>> folder” on a disk of small size, or does it have a small amount of free
>> space?  The source build of Sage does take a lot of space.  On my system,
>> Sage 9.0 uses about 7.5 GB (when complete).
>>
>> HTH
>>
>> Justin
>>
>> --
>> Justin C. Walker
>> Curmudgeon-at-large
>> Director
>> Institute for the Absorption of Federal Funds
>> 
>> 186,000 Miles per Second
>> Not just a good idea:
>>   it's the law!
>> 
>>
>> --
>> 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
>> https://groups.google.com/d/msgid/sage-support/8F194F5B-3706-4290-AB20-9E16425014D4%40mac.com
>> .
>>
> --
> 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
> https://groups.google.com/d/msgid/sage-support/CADTeGQetEtmqpEKvGXQ-Y6tOHqUaVX_NMdBQnVXqwv%3Dq7Kxr7A%40mail.gmail.com
> 
> .
>

-- 
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 
https://groups.google.com/d/msgid/sage-support/CA%2B01voOSBEF-8L3NkKreYmK3HTC808pjE2Ni4ss3n5DwMY%2B1HA%40mail.gmail.com.

Re: [sage-support] Sage Crash Report

[HANG HUANG]

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 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 install from source code as the installing from pre-built
> binaries also gives me some other error. I was able  to run ./configure
> without any issues and then when i did make, I received the following log
> file (attached) and error:
> >
> > Error building Sage.
> >
> > The following package(s) may have failed to build (not necessarily
> > during this run of 'make all-start'):
> >
> > * package: flint-2.5.2.p5
> >   log file: /scratch/user/hhuang235/sage-9.0/logs/pkgs/flint-2.5.2.p5.log
> >   build directory:
> /scratch/user/hhuang235/sage-9.0/local/var/tmp/sage/build/flint-2.5.2.p5
> >
> > 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[1]: *** [all-start] Error 1
> > make[1]: Leaving directory `/scratch/user/hhuang235/sage-9.0'
> > make: *** [all] Error 2
>
> Checking the log file for flint that you attached, there is this:
>
> ccache: error: Failed to create temporary file for
> /home/hhuang235/.ccache/2/9/8e02d78d68b9638edd65c3e5744171-2001.manifest.tmp:
> Disk quota exceeded
>
> I think that should explain the problem you are having.  Is the “scratch
> folder” on a disk of small size, or does it have a small amount of free
> space?  The source build of Sage does take a lot of space.  On my system,
> Sage 9.0 uses about 7.5 GB (when complete).
>
> HTH
>
> Justin
>
> --
> Justin C. Walker
> Curmudgeon-at-large
> Director
> Institute for the Absorption of Federal Funds
> 
> 186,000 Miles per Second
> Not just a good idea:
>   it's the law!
> 
>
> --
> 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
> https://groups.google.com/d/msgid/sage-support/8F194F5B-3706-4290-AB20-9E16425014D4%40mac.com
> .
>

-- 
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 
https://groups.google.com/d/msgid/sage-support/CADTeGQetEtmqpEKvGXQ-Y6tOHqUaVX_NMdBQnVXqwv%3Dq7Kxr7A%40mail.gmail.com.

Re: [sage-support] Sage Crash Report

['Justin C. Walker' via sage-support]

> 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 install from source code as the installing from pre-built binaries also 
> gives me some other error. I was able  to run ./configure without any issues 
> and then when i did make, I received the following log file (attached) and 
> error: 
> 
> Error building Sage.
> 
> The following package(s) may have failed to build (not necessarily
> during this run of 'make all-start'):
> 
> * package: flint-2.5.2.p5
>   log file: /scratch/user/hhuang235/sage-9.0/logs/pkgs/flint-2.5.2.p5.log
>   build directory: 
> /scratch/user/hhuang235/sage-9.0/local/var/tmp/sage/build/flint-2.5.2.p5
> 
> 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[1]: *** [all-start] Error 1
> make[1]: Leaving directory `/scratch/user/hhuang235/sage-9.0'
> make: *** [all] Error 2

Checking the log file for flint that you attached, there is this:

ccache: error: Failed to create temporary file for 
/home/hhuang235/.ccache/2/9/8e02d78d68b9638edd65c3e5744171-2001.manifest.tmp: 
Disk quota exceeded

I think that should explain the problem you are having.  Is the “scratch 
folder” on a disk of small size, or does it have a small amount of free space?  
The source build of Sage does take a lot of space.  On my system, Sage 9.0 uses 
about 7.5 GB (when complete).

HTH

Justin

--
Justin C. Walker
Curmudgeon-at-large
Director
Institute for the Absorption of Federal Funds

186,000 Miles per Second
Not just a good idea:
  it's the law!


-- 
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 
https://groups.google.com/d/msgid/sage-support/8F194F5B-3706-4290-AB20-9E16425014D4%40mac.com.

Re: [sage-support] Sage Crash report

[hbetx9]

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 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 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 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 wondering if I should just erase and start 
>>> over. 
>>>
>>> Now make finishes with 
>>>
>>> Makefile:31: recipe for target 'base-toolchain' failed
>>> make: *** [base-toolchain] Error 1
>>>
>>> and when running I get only the following message 
>>>
>>> 
>>> It seems that you are attempting to run Sage from an unpacked source
>>> tarball, but you have not compiled it yet (or maybe the build has not
>>> finished). You should run `make` in the Sage root directory first.
>>> If you did not intend to build Sage from source, you should download
>>> a binary tarball instead. Read README.txt for more information.
>>> 
>>>
>>> Should I just start over or is there an easy way to repair this issue? 
>>>
>>> On Wednesday, April 8, 2020 at 11:12:19 PM UTC-5, Matthias Koeppe wrote:

 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 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 
https://groups.google.com/d/msgid/sage-support/ec967a81-8172-4ea1-a17e-c7ce16c4ddde%40googlegroups.com.

Re: [sage-support] Sage Crash report

[John H Palmieri]

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 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 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 wondering if I should just erase and start 
>> over. 
>>
>> Now make finishes with 
>>
>> Makefile:31: recipe for target 'base-toolchain' failed
>> make: *** [base-toolchain] Error 1
>>
>> and when running I get only the following message 
>>
>> 
>> It seems that you are attempting to run Sage from an unpacked source
>> tarball, but you have not compiled it yet (or maybe the build has not
>> finished). You should run `make` in the Sage root directory first.
>> If you did not intend to build Sage from source, you should download
>> a binary tarball instead. Read README.txt for more information.
>> 
>>
>> Should I just start over or is there an easy way to repair this issue? 
>>
>> On Wednesday, April 8, 2020 at 11:12:19 PM UTC-5, Matthias Koeppe wrote:
>>>
>>> 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 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 
https://groups.google.com/d/msgid/sage-support/aef99461-ab90-41a7-a198-9585503996e8%40googlegroups.com.

Re: [sage-support] Sage Crash report

[hbetx9]

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 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 wondering if I should just erase and start 
> over. 
>
> Now make finishes with 
>
> Makefile:31: recipe for target 'base-toolchain' failed
> make: *** [base-toolchain] Error 1
>
> and when running I get only the following message 
>
> 
> It seems that you are attempting to run Sage from an unpacked source
> tarball, but you have not compiled it yet (or maybe the build has not
> finished). You should run `make` in the Sage root directory first.
> If you did not intend to build Sage from source, you should download
> a binary tarball instead. Read README.txt for more information.
> 
>
> Should I just start over or is there an easy way to repair this issue? 
>
> On Wednesday, April 8, 2020 at 11:12:19 PM UTC-5, Matthias Koeppe wrote:
>>
>> 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 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 
https://groups.google.com/d/msgid/sage-support/0b78b6ed-3fcf-4820-8bef-8ee59e5a99ab%40googlegroups.com.

Re: [sage-support] Sage Crash report

[hbetx9]

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 wondering if I should just erase and start 
over. 

Now make finishes with 

Makefile:31: recipe for target 'base-toolchain' failed
make: *** [base-toolchain] Error 1

and when running I get only the following message 


It seems that you are attempting to run Sage from an unpacked source
tarball, but you have not compiled it yet (or maybe the build has not
finished). You should run `make` in the Sage root directory first.
If you did not intend to build Sage from source, you should download
a binary tarball instead. Read README.txt for more information.


Should I just start over or is there an easy way to repair this issue? 

On Wednesday, April 8, 2020 at 11:12:19 PM UTC-5, Matthias Koeppe wrote:
>
> 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 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 
https://groups.google.com/d/msgid/sage-support/211879d7-0157-432f-b390-68658853cc5e%40googlegroups.com.

Re: [sage-support] Sage Crash report

[Matthias Koeppe]

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 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 
https://groups.google.com/d/msgid/sage-support/394ece00-bd5a-4ac2-9e2f-257fd84999c3%40googlegroups.com.

Re: [sage-support] Sage Crash report

[hbetx9]

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 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 to globalize 
> this install. Its likely a basic question but what is the best way to do 
> this? 
>
> "globalize" seems to be something from JavaScript world. Do you mean 
> multi-language support? 
>
> > 
> > On Wednesday, April 8, 2020 at 6:11:33 PM UTC-5, Matthias Koeppe wrote: 
> >> 
> >> 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 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 3.6.3 
> correct? 
> >>> 
> >>> 
> >>> After all this is addressed, how to make this available system wide? 
> Is there a script in the SAGE_LOCAL that will do it? I know that's a basic 
> question but I'm curious. I removed Sage 8 so there should be no conflict. 
> > 
> > -- 
> > 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-s...@googlegroups.com . 
> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-support/5fb29a7d-db79-4f13-83bf-4a7b3a904961%40googlegroups.com.
>  
>
>

-- 
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 
https://groups.google.com/d/msgid/sage-support/912f231f-d2e2-4af6-897f-57da5c27503b%40googlegroups.com.

Re: [sage-support] Sage Crash report

[Dima Pasechnik]

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?
>
> If I don't resolve this now, then sage works but I'd like to globalize this 
> install. Its likely a basic question but what is the best way to do this?

"globalize" seems to be something from JavaScript world. Do you mean
multi-language support?

>
> On Wednesday, April 8, 2020 at 6:11:33 PM UTC-5, Matthias Koeppe wrote:
>>
>> 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 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 3.6.3 
>>> correct?
>>>
>>>
>>> After all this is addressed, how to make this available system wide? Is 
>>> there a script in the SAGE_LOCAL that will do it? I know that's a basic 
>>> question but I'm curious. I removed Sage 8 so there should be no conflict.
>
> --
> 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 
> https://groups.google.com/d/msgid/sage-support/5fb29a7d-db79-4f13-83bf-4a7b3a904961%40googlegroups.com.

-- 
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 
https://groups.google.com/d/msgid/sage-support/CAAWYfq2N%2BucCL2HoA0rbcjvGdiwtbtZtQpXzkksoCCxiMzTgzA%40mail.gmail.com.

Re: [sage-support] Sage Crash report

[hbetx9]

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 to globalize this 
install. Its likely a basic question but what is the best way to do this? 

On Wednesday, April 8, 2020 at 6:11:33 PM UTC-5, Matthias Koeppe wrote:
>
> 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 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 3.6.3 
>> correct? 
>>
>>
>> After all this is addressed, how to make this available system wide? Is 
>> there a script in the SAGE_LOCAL that will do it? I know that's a basic 
>> question but I'm curious. I removed Sage 8 so there should be no conflict.
>>
>

-- 
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 
https://groups.google.com/d/msgid/sage-support/5fb29a7d-db79-4f13-83bf-4a7b3a904961%40googlegroups.com.

Re: [sage-support] Sage Crash report

[Matthias Koeppe]

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 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 3.6.3 
> correct? 
>
>
> After all this is addressed, how to make this available system wide? Is 
> there a script in the SAGE_LOCAL that will do it? I know that's a basic 
> question but I'm curious. I removed Sage 8 so there should be no conflict.
>

-- 
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 
https://groups.google.com/d/msgid/sage-support/5a3ec927-0f24-4e0f-951f-aa643386d033%40googlegroups.com.

Re: [sage-support] Sage Crash report

[hbetx9]

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 3.6.3 
correct? 


After all this is addressed, how to make this available system wide? Is 
there a script in the SAGE_LOCAL that will do it? I know that's a basic 
question but I'm curious. I removed Sage 8 so there should be no conflict. 

On Wednesday, April 8, 2020 at 12:56:29 PM UTC-5, hbetx9 wrote:
>
> 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 (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: /home/lmiller/sage-9.0/local/var/tmp/sage/build/r-3.6.2
>>
>> which I'm guessing is only needed if one wants to use integration with R. 
>> At this time I don't but in future I might, should I install R and 
>> rebuild?  Build took a LONG time. 
>>
>> Also, version 9 is now in ~/SAGE_ROOT/local but the system version is 
>> still 8.1. I guess I need to modify path or create a symlink to get sage 
>> available to terminal on boot? 
>>
>> Finally, can the color scheme for sage on the terminal be changed? I used 
>> a dark background so this is not easy to read. 
>>
>> Thanks in advance!
>>
>> On Wednesday, April 8, 2020 at 12:14:48 AM UTC-5, Dima Pasechnik wrote:
>>>
>>> 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 there a PPA I need to add? 
>>> > 
>>>
>>> my understanding is that MInt 19 by default follows Ubunu 18.04 (which 
>>> indeed has Sage 8.1). 
>>> We'd recommend you to build Sage (say, the latest stable version, 9.0) 
>>> from source instead. 
>>> While latest Ubuntu does have Sage 9.0, I don't know how to get it 
>>> installed on your Mint, from PPA or otherwise. 
>>> Perhaps you can ask on a Mint forum. 
>>>
>>> HTH 
>>> Dima 
>>>
>>>
>>> > Best, 
>>> > Lance 
>>> > 
>>> > On Saturday, April 4, 2020 at 9:49:09 PM UTC-5, Dima Pasechnik wrote: 
>>> >> 
>>> >> 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? 
>>> >> 
>>> >> > 
>>> >> > 
>>> *** 
>>> >> > 
>>> >> > IPython post-mortem report 
>>> >> > 
>>> >> > {'commit_hash': u'b467d487e', 
>>> >> >  'commit_source': 'installation', 
>>> >> >  'default_encoding': 'UTF-8', 
>>> >> >  'ipython_path': '/usr/lib/python2.7/dist-packages/IPython', 
>>> >> >  'ipython_version': '5.5.0', 
>>> >> >  'os_name': 'posix', 
>>> >> >  'platform': 
>>> 'Linux-5.3.0-40-generic-x86_64-with-LinuxMint-19.3-tricia', 
>>> >> >  'sys_executable': '/usr/bin/python', 
>>> >> >  'sys_platform': 'linux2', 
>>> >> >  'sys_version': '2.7.17 (default, Nov  7 2019, 10:07:09) \n[GCC 
>>> 7.4.0]'} 
>>> >> > 
>>> >> > 
>>> *** 
>>> >> > 
>>> >> > 
>>> >> > 
>>> >> > 
>>> *** 
>>> >> > 
>>> >> > Crash traceback: 
>>> >> > 
>>> >> > 
>>> --- 
>>> >> > 
>>> --- 
>>> >> > ImportError  Python 2.7.17: 
>>> /usr/bin/python 
>>> >> >Sat Apr  4 
>>> 18:39:09 2020 
>>> >> > A problem occurred executing Python code.  Here is the sequence of 
>>> function 
>>> >> > calls leading up to the error, with the most recent (innermost) 
>>> call last. 
>>> >> > /usr/share/sagemath/bin/sage-ipython in () 
>>> >> >   1 #!/usr/bin/env python 
>>> >> >   2 # -*- coding: utf-8 -*- 
>>> >> >   3 """ 
>>> >> >   4 Sage IPython startup script. 
>>> >> >   5 """ 
>>> >> >   6 
>>> >> >   7 from sage.repl.interpreter import SageTerminalApp 
>>> >> >   8 
>>> >> >   9 app = SageTerminalApp.instance() 
>>> >> > ---> 10 app.initialize() 
>>> >> > global app.initialize = >> SageTerminalApp.initialize of >> at 0x7f76836e7150>> 
>>> >> >  11 app.start() 
>>> >> > 
>>> >> >  

Re: [sage-support] Sage Crash report

[hbetx9]

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 (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: /home/lmiller/sage-9.0/local/var/tmp/sage/build/r-3.6.2
>
> which I'm guessing is only needed if one wants to use integration with R. 
> At this time I don't but in future I might, should I install R and 
> rebuild?  Build took a LONG time. 
>
> Also, version 9 is now in ~/SAGE_ROOT/local but the system version is 
> still 8.1. I guess I need to modify path or create a symlink to get sage 
> available to terminal on boot? 
>
> Finally, can the color scheme for sage on the terminal be changed? I used 
> a dark background so this is not easy to read. 
>
> Thanks in advance!
>
> On Wednesday, April 8, 2020 at 12:14:48 AM UTC-5, Dima Pasechnik wrote:
>>
>> 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 there a PPA I need to add? 
>> > 
>>
>> my understanding is that MInt 19 by default follows Ubunu 18.04 (which 
>> indeed has Sage 8.1). 
>> We'd recommend you to build Sage (say, the latest stable version, 9.0) 
>> from source instead. 
>> While latest Ubuntu does have Sage 9.0, I don't know how to get it 
>> installed on your Mint, from PPA or otherwise. 
>> Perhaps you can ask on a Mint forum. 
>>
>> HTH 
>> Dima 
>>
>>
>> > Best, 
>> > Lance 
>> > 
>> > On Saturday, April 4, 2020 at 9:49:09 PM UTC-5, Dima Pasechnik wrote: 
>> >> 
>> >> 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? 
>> >> 
>> >> > 
>> >> > 
>> *** 
>> >> > 
>> >> > IPython post-mortem report 
>> >> > 
>> >> > {'commit_hash': u'b467d487e', 
>> >> >  'commit_source': 'installation', 
>> >> >  'default_encoding': 'UTF-8', 
>> >> >  'ipython_path': '/usr/lib/python2.7/dist-packages/IPython', 
>> >> >  'ipython_version': '5.5.0', 
>> >> >  'os_name': 'posix', 
>> >> >  'platform': 
>> 'Linux-5.3.0-40-generic-x86_64-with-LinuxMint-19.3-tricia', 
>> >> >  'sys_executable': '/usr/bin/python', 
>> >> >  'sys_platform': 'linux2', 
>> >> >  'sys_version': '2.7.17 (default, Nov  7 2019, 10:07:09) \n[GCC 
>> 7.4.0]'} 
>> >> > 
>> >> > 
>> *** 
>> >> > 
>> >> > 
>> >> > 
>> >> > 
>> *** 
>> >> > 
>> >> > Crash traceback: 
>> >> > 
>> >> > 
>> --- 
>> >> > 
>> --- 
>> >> > ImportError  Python 2.7.17: 
>> /usr/bin/python 
>> >> >Sat Apr  4 
>> 18:39:09 2020 
>> >> > A problem occurred executing Python code.  Here is the sequence of 
>> function 
>> >> > calls leading up to the error, with the most recent (innermost) call 
>> last. 
>> >> > /usr/share/sagemath/bin/sage-ipython in () 
>> >> >   1 #!/usr/bin/env python 
>> >> >   2 # -*- coding: utf-8 -*- 
>> >> >   3 """ 
>> >> >   4 Sage IPython startup script. 
>> >> >   5 """ 
>> >> >   6 
>> >> >   7 from sage.repl.interpreter import SageTerminalApp 
>> >> >   8 
>> >> >   9 app = SageTerminalApp.instance() 
>> >> > ---> 10 app.initialize() 
>> >> > global app.initialize = > SageTerminalApp.initialize of > at 0x7f76836e7150>> 
>> >> >  11 app.start() 
>> >> > 
>> >> >  in 
>> initialize(self=, argv=None) 
>> >> > 
>> >> > /usr/lib/python2.7/dist-packages/traitlets/config/application.pyc in 
>> catch_config_error(method=, 
>> app=, *args=(None,), 
>> **kwargs={}) 
>> >> >  72 TRAITLETS_APPLICATION_RAISE_CONFIG_FILE_ERROR = False 
>> >> >  73 else: 
>> >> >  74 raise ValueError("Unsupported value for environment 
>> variable: 'TRAITLETS_APPLICATION_RAISE_CONFIG_FILE_ERROR' is set to '%s' 
>> which is none of  {'0', '1', 'false', 'true', ''}."% _envvar ) 
>> >> >  75 
>> >> >  76 
>> >> >  77 @decorator 
>> >> >  78 def catch_config_error(method, app, *args, **kwargs): 
>> >> >  79 """Method decorator for catching invalid config 
>> 

Re: [sage-support] Sage Crash report

[hbetx9]

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 UTC-5, slelievre wrote:
>
> > 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`
> folder in hour home, so that it will be run
> each time you start 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 it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/3cb9f550-e43f-4d40-9975-14324daf0693%40googlegroups.com.

Re: [sage-support] Sage Crash report

[slelievre]

> 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`
folder in hour home, so that it will be run
each time you start 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 it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/5bc0257f-8666-4915-9d8a-f72f559f69d7%40googlegroups.com.

Re: [sage-support] Sage Crash report

[hbetx9]

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: /home/lmiller/sage-9.0/local/var/tmp/sage/build/r-3.6.2

which I'm guessing is only needed if one wants to use integration with R. 
At this time I don't but in future I might, should I install R and 
rebuild?  Build took a LONG time. 

Also, version 9 is now in ~/SAGE_ROOT/local but the system version is still 
8.1. I guess I need to modify path or create a symlink to get sage 
available to terminal on boot? 

Finally, can the color scheme for sage on the terminal be changed? I used a 
dark background so this is not easy to read. 

Thanks in advance!

On Wednesday, April 8, 2020 at 12:14:48 AM UTC-5, Dima Pasechnik wrote:
>
> 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 there a PPA I need to add? 
> > 
>
> my understanding is that MInt 19 by default follows Ubunu 18.04 (which 
> indeed has Sage 8.1). 
> We'd recommend you to build Sage (say, the latest stable version, 9.0) 
> from source instead. 
> While latest Ubuntu does have Sage 9.0, I don't know how to get it 
> installed on your Mint, from PPA or otherwise. 
> Perhaps you can ask on a Mint forum. 
>
> HTH 
> Dima 
>
>
> > Best, 
> > Lance 
> > 
> > On Saturday, April 4, 2020 at 9:49:09 PM UTC-5, Dima Pasechnik wrote: 
> >> 
> >> 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? 
> >> 
> >> > 
> >> > 
> *** 
> >> > 
> >> > IPython post-mortem report 
> >> > 
> >> > {'commit_hash': u'b467d487e', 
> >> >  'commit_source': 'installation', 
> >> >  'default_encoding': 'UTF-8', 
> >> >  'ipython_path': '/usr/lib/python2.7/dist-packages/IPython', 
> >> >  'ipython_version': '5.5.0', 
> >> >  'os_name': 'posix', 
> >> >  'platform': 
> 'Linux-5.3.0-40-generic-x86_64-with-LinuxMint-19.3-tricia', 
> >> >  'sys_executable': '/usr/bin/python', 
> >> >  'sys_platform': 'linux2', 
> >> >  'sys_version': '2.7.17 (default, Nov  7 2019, 10:07:09) \n[GCC 
> 7.4.0]'} 
> >> > 
> >> > 
> *** 
> >> > 
> >> > 
> >> > 
> >> > 
> *** 
> >> > 
> >> > Crash traceback: 
> >> > 
> >> > 
> --- 
> >> > 
> --- 
> >> > ImportError  Python 2.7.17: 
> /usr/bin/python 
> >> >Sat Apr  4 
> 18:39:09 2020 
> >> > A problem occurred executing Python code.  Here is the sequence of 
> function 
> >> > calls leading up to the error, with the most recent (innermost) call 
> last. 
> >> > /usr/share/sagemath/bin/sage-ipython in () 
> >> >   1 #!/usr/bin/env python 
> >> >   2 # -*- coding: utf-8 -*- 
> >> >   3 """ 
> >> >   4 Sage IPython startup script. 
> >> >   5 """ 
> >> >   6 
> >> >   7 from sage.repl.interpreter import SageTerminalApp 
> >> >   8 
> >> >   9 app = SageTerminalApp.instance() 
> >> > ---> 10 app.initialize() 
> >> > global app.initialize =  SageTerminalApp.initialize of  at 0x7f76836e7150>> 
> >> >  11 app.start() 
> >> > 
> >> >  in 
> initialize(self=, argv=None) 
> >> > 
> >> > /usr/lib/python2.7/dist-packages/traitlets/config/application.pyc in 
> catch_config_error(method=, 
> app=, *args=(None,), 
> **kwargs={}) 
> >> >  72 TRAITLETS_APPLICATION_RAISE_CONFIG_FILE_ERROR = False 
> >> >  73 else: 
> >> >  74 raise ValueError("Unsupported value for environment 
> variable: 'TRAITLETS_APPLICATION_RAISE_CONFIG_FILE_ERROR' is set to '%s' 
> which is none of  {'0', '1', 'false', 'true', ''}."% _envvar ) 
> >> >  75 
> >> >  76 
> >> >  77 @decorator 
> >> >  78 def catch_config_error(method, app, *args, **kwargs): 
> >> >  79 """Method decorator for catching invalid config 
> (Trait/ArgumentErrors) during init. 
> >> >  80 
> >> >  81 On a TraitError (generally caused by bad config), this 
> will print the trait's 
> >> >  82 message, and exit the app. 
> >> >  83 
> >> >  84 For use on init methods, to prevent invoking excepthook 
> on invalid input. 
> >> >  85 """ 

Re: [sage-support] Sage Crash report

[Dima Pasechnik]

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 there a PPA I need to add?
>

my understanding is that MInt 19 by default follows Ubunu 18.04 (which
indeed has Sage 8.1).
We'd recommend you to build Sage (say, the latest stable version, 9.0)
from source instead.
While latest Ubuntu does have Sage 9.0, I don't know how to get it
installed on your Mint, from PPA or otherwise.
Perhaps you can ask on a Mint forum.

HTH
Dima


> Best,
> Lance
>
> On Saturday, April 4, 2020 at 9:49:09 PM UTC-5, Dima Pasechnik wrote:
>>
>> 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?
>>
>> >
>> > ***
>> >
>> > IPython post-mortem report
>> >
>> > {'commit_hash': u'b467d487e',
>> >  'commit_source': 'installation',
>> >  'default_encoding': 'UTF-8',
>> >  'ipython_path': '/usr/lib/python2.7/dist-packages/IPython',
>> >  'ipython_version': '5.5.0',
>> >  'os_name': 'posix',
>> >  'platform': 'Linux-5.3.0-40-generic-x86_64-with-LinuxMint-19.3-tricia',
>> >  'sys_executable': '/usr/bin/python',
>> >  'sys_platform': 'linux2',
>> >  'sys_version': '2.7.17 (default, Nov  7 2019, 10:07:09) \n[GCC 7.4.0]'}
>> >
>> > ***
>> >
>> >
>> >
>> > ***
>> >
>> > Crash traceback:
>> >
>> > ---
>> > ---
>> > ImportError  Python 2.7.17: /usr/bin/python
>> >Sat Apr  4 18:39:09 2020
>> > A problem occurred executing Python code.  Here is the sequence of function
>> > calls leading up to the error, with the most recent (innermost) call last.
>> > /usr/share/sagemath/bin/sage-ipython in ()
>> >   1 #!/usr/bin/env python
>> >   2 # -*- coding: utf-8 -*-
>> >   3 """
>> >   4 Sage IPython startup script.
>> >   5 """
>> >   6
>> >   7 from sage.repl.interpreter import SageTerminalApp
>> >   8
>> >   9 app = SageTerminalApp.instance()
>> > ---> 10 app.initialize()
>> > global app.initialize = > > of >
>> >  11 app.start()
>> >
>> >  in 
>> > initialize(self=, argv=None)
>> >
>> > /usr/lib/python2.7/dist-packages/traitlets/config/application.pyc in 
>> > catch_config_error(method=, 
>> > app=, *args=(None,), 
>> > **kwargs={})
>> >  72 TRAITLETS_APPLICATION_RAISE_CONFIG_FILE_ERROR = False
>> >  73 else:
>> >  74 raise ValueError("Unsupported value for environment variable: 
>> > 'TRAITLETS_APPLICATION_RAISE_CONFIG_FILE_ERROR' is set to '%s' which is 
>> > none of  {'0', '1', 'false', 'true', ''}."% _envvar )
>> >  75
>> >  76
>> >  77 @decorator
>> >  78 def catch_config_error(method, app, *args, **kwargs):
>> >  79 """Method decorator for catching invalid config 
>> > (Trait/ArgumentErrors) during init.
>> >  80
>> >  81 On a TraitError (generally caused by bad config), this will 
>> > print the trait's
>> >  82 message, and exit the app.
>> >  83
>> >  84 For use on init methods, to prevent invoking excepthook on 
>> > invalid input.
>> >  85 """
>> >  86 try:
>> > ---> 87 return method(app, *args, **kwargs)
>> > method = 
>> > app = > > 0x7f76836e7150>
>> > args = (None,)
>> > kwargs = {}
>> >  88 except (TraitError, ArgumentError) as e:
>> >  89 app.print_help()
>> >  90 app.log.fatal("Bad config encountered during 
>> > initialization:")
>> >  91 app.log.fatal(str(e))
>> >  92 app.log.debug("Config at the time: %s", app.config)
>> >  93 app.exit(1)
>> >  94
>> >  95
>> >  96 class ApplicationError(Exception):
>> >  97 pass
>> >  98
>> >  99
>> > 100 class LevelFormatter(logging.Formatter):
>> > 101 """Formatter with additional `highlevel` record
>> > 102
>> >
>> > /usr/lib/python2.7/dist-packages/IPython/terminal/ipapp.pyc in 
>> > initialize(self=, argv=None)
>> > 301
>> > 302 return super(TerminalIPythonApp, 
>> > self).parse_command_line(argv)
>> > 303
>> > 304 @catch_config_error
>> > 305 def initialize(self, argv=None):
>> > 306 """Do actions after construct, but before starting the 
>> > app."""
>> > 307 

Re: [sage-support] Sage Crash report

[hbetx9]

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 Saturday, April 4, 2020 at 9:49:09 PM UTC-5, Dima Pasechnik wrote:
>
> 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? 
>
> > 
> > 
> *** 
> > 
> > IPython post-mortem report 
> > 
> > {'commit_hash': u'b467d487e', 
> >  'commit_source': 'installation', 
> >  'default_encoding': 'UTF-8', 
> >  'ipython_path': '/usr/lib/python2.7/dist-packages/IPython', 
> >  'ipython_version': '5.5.0', 
> >  'os_name': 'posix', 
> >  'platform': 'Linux-5.3.0-40-generic-x86_64-with-LinuxMint-19.3-tricia', 
> >  'sys_executable': '/usr/bin/python', 
> >  'sys_platform': 'linux2', 
> >  'sys_version': '2.7.17 (default, Nov  7 2019, 10:07:09) \n[GCC 7.4.0]'} 
> > 
> > 
> *** 
> > 
> > 
> > 
> > 
> *** 
> > 
> > Crash traceback: 
> > 
> > 
> --- 
> > 
> --- 
> > ImportError  Python 2.7.17: 
> /usr/bin/python 
> >Sat Apr  4 18:39:09 
> 2020 
> > A problem occurred executing Python code.  Here is the sequence of 
> function 
> > calls leading up to the error, with the most recent (innermost) call 
> last. 
> > /usr/share/sagemath/bin/sage-ipython in () 
> >   1 #!/usr/bin/env python 
> >   2 # -*- coding: utf-8 -*- 
> >   3 """ 
> >   4 Sage IPython startup script. 
> >   5 """ 
> >   6 
> >   7 from sage.repl.interpreter import SageTerminalApp 
> >   8 
> >   9 app = SageTerminalApp.instance() 
> > ---> 10 app.initialize() 
> > global app.initialize =  of > 
> >  11 app.start() 
> > 
> >  in 
> initialize(self=, argv=None) 
> > 
> > /usr/lib/python2.7/dist-packages/traitlets/config/application.pyc in 
> catch_config_error(method=, 
> app=, *args=(None,), 
> **kwargs={}) 
> >  72 TRAITLETS_APPLICATION_RAISE_CONFIG_FILE_ERROR = False 
> >  73 else: 
> >  74 raise ValueError("Unsupported value for environment 
> variable: 'TRAITLETS_APPLICATION_RAISE_CONFIG_FILE_ERROR' is set to '%s' 
> which is none of  {'0', '1', 'false', 'true', ''}."% _envvar ) 
> >  75 
> >  76 
> >  77 @decorator 
> >  78 def catch_config_error(method, app, *args, **kwargs): 
> >  79 """Method decorator for catching invalid config 
> (Trait/ArgumentErrors) during init. 
> >  80 
> >  81 On a TraitError (generally caused by bad config), this will 
> print the trait's 
> >  82 message, and exit the app. 
> >  83 
> >  84 For use on init methods, to prevent invoking excepthook on 
> invalid input. 
> >  85 """ 
> >  86 try: 
> > ---> 87 return method(app, *args, **kwargs) 
> > method =  
> > app =  0x7f76836e7150> 
> > args = (None,) 
> > kwargs = {} 
> >  88 except (TraitError, ArgumentError) as e: 
> >  89 app.print_help() 
> >  90 app.log.fatal("Bad config encountered during 
> initialization:") 
> >  91 app.log.fatal(str(e)) 
> >  92 app.log.debug("Config at the time: %s", app.config) 
> >  93 app.exit(1) 
> >  94 
> >  95 
> >  96 class ApplicationError(Exception): 
> >  97 pass 
> >  98 
> >  99 
> > 100 class LevelFormatter(logging.Formatter): 
> > 101 """Formatter with additional `highlevel` record 
> > 102 
> > 
> > /usr/lib/python2.7/dist-packages/IPython/terminal/ipapp.pyc in 
> initialize(self=, argv=None) 
> > 301 
> > 302 return super(TerminalIPythonApp, 
> self).parse_command_line(argv) 
> > 303 
> > 304 @catch_config_error 
> > 305 def initialize(self, argv=None): 
> > 306 """Do actions after construct, but before starting the 
> app.""" 
> > 307 super(TerminalIPythonApp, self).initialize(argv) 
> > 308 if self.subapp is not None: 
> > 309 # don't bother initializing further, starting subapp 
> > 310 return 
> > 311 # print self.extra_args 
> > 312 if self.extra_args and not self.something_to_run: 
> > 313 self.file_to_run = self.extra_args[0] 
> > 314 self.init_path() 

Re: [sage-support] Sage Crash report

[Dima Pasechnik]

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?

>
> ***
>
> IPython post-mortem report
>
> {'commit_hash': u'b467d487e',
>  'commit_source': 'installation',
>  'default_encoding': 'UTF-8',
>  'ipython_path': '/usr/lib/python2.7/dist-packages/IPython',
>  'ipython_version': '5.5.0',
>  'os_name': 'posix',
>  'platform': 'Linux-5.3.0-40-generic-x86_64-with-LinuxMint-19.3-tricia',
>  'sys_executable': '/usr/bin/python',
>  'sys_platform': 'linux2',
>  'sys_version': '2.7.17 (default, Nov  7 2019, 10:07:09) \n[GCC 7.4.0]'}
>
> ***
>
>
>
> ***
>
> Crash traceback:
>
> ---
> ---
> ImportError  Python 2.7.17: /usr/bin/python
>Sat Apr  4 18:39:09 2020
> A problem occurred executing Python code.  Here is the sequence of function
> calls leading up to the error, with the most recent (innermost) call last.
> /usr/share/sagemath/bin/sage-ipython in ()
>   1 #!/usr/bin/env python
>   2 # -*- coding: utf-8 -*-
>   3 """
>   4 Sage IPython startup script.
>   5 """
>   6
>   7 from sage.repl.interpreter import SageTerminalApp
>   8
>   9 app = SageTerminalApp.instance()
> ---> 10 app.initialize()
> global app.initialize =  >
>  11 app.start()
>
>  in initialize(self= object>, argv=None)
>
> /usr/lib/python2.7/dist-packages/traitlets/config/application.pyc in 
> catch_config_error(method=, 
> app=, *args=(None,), 
> **kwargs={})
>  72 TRAITLETS_APPLICATION_RAISE_CONFIG_FILE_ERROR = False
>  73 else:
>  74 raise ValueError("Unsupported value for environment variable: 
> 'TRAITLETS_APPLICATION_RAISE_CONFIG_FILE_ERROR' is set to '%s' which is none 
> of  {'0', '1', 'false', 'true', ''}."% _envvar )
>  75
>  76
>  77 @decorator
>  78 def catch_config_error(method, app, *args, **kwargs):
>  79 """Method decorator for catching invalid config 
> (Trait/ArgumentErrors) during init.
>  80
>  81 On a TraitError (generally caused by bad config), this will print 
> the trait's
>  82 message, and exit the app.
>  83
>  84 For use on init methods, to prevent invoking excepthook on 
> invalid input.
>  85 """
>  86 try:
> ---> 87 return method(app, *args, **kwargs)
> method = 
> app = 
> args = (None,)
> kwargs = {}
>  88 except (TraitError, ArgumentError) as e:
>  89 app.print_help()
>  90 app.log.fatal("Bad config encountered during initialization:")
>  91 app.log.fatal(str(e))
>  92 app.log.debug("Config at the time: %s", app.config)
>  93 app.exit(1)
>  94
>  95
>  96 class ApplicationError(Exception):
>  97 pass
>  98
>  99
> 100 class LevelFormatter(logging.Formatter):
> 101 """Formatter with additional `highlevel` record
> 102
>
> /usr/lib/python2.7/dist-packages/IPython/terminal/ipapp.pyc in 
> initialize(self=, argv=None)
> 301
> 302 return super(TerminalIPythonApp, 
> self).parse_command_line(argv)
> 303
> 304 @catch_config_error
> 305 def initialize(self, argv=None):
> 306 """Do actions after construct, but before starting the app."""
> 307 super(TerminalIPythonApp, self).initialize(argv)
> 308 if self.subapp is not None:
> 309 # don't bother initializing further, starting subapp
> 310 return
> 311 # print self.extra_args
> 312 if self.extra_args and not self.something_to_run:
> 313 self.file_to_run = self.extra_args[0]
> 314 self.init_path()
> 315 # create the shell
> --> 316 self.init_shell()
> self.init_shell =  >
> 317 # and draw the banner
> 318 self.init_banner()
> 319 # Now a variety of things that happen after the banner is 
> printed.
> 320 self.init_gui_pylab()
> 321 self.init_extensions()
> 322 self.init_code()
> 323
> 324 def init_shell(self):
> 325 """initialize the InteractiveShell instance"""
> 326 # Create an InteractiveShell instance.
> 327 # shell.display_banner should always be False for the terminal
> 328 # based app, because we call shell.show_banner() by hand below
> 329   

Re: [sage-support] Sage Crash Report

[Dima Pasechnik]

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 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 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  wrote:
>>
>>>
>>>
>>> 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, often used on HPC clusters.
>>>
>>> HPC clusters usually give users space for their home directories on
>>> networked file systems, and for "scratch" partitions too.
>>>
>>>
 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 file, it still has this as the last error:

 configure: error: in
 `/scratch/user/kbari/sage-8.9/local/var/tmp/sage/build/sqlite-3270100/src':
 configure: error: C compiler cannot create executables

 Best,
 Kash

 On Tue, Mar 24, 2020 at 7:53 AM Dima Pasechnik 
 wrote:

> 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 when running make again:
> >
> > Error building Sage.
> >
> > The following package(s) may have failed to build (not necessarily
> > during this run of 'make all-start'):
> >
> > * package: sqlite-3270100
> >   log file: /scratch/user/kbari/sage-8.9/logs/pkgs/sqlite-3270100.log
> >   build directory:
> /scratch/user/kbari/sage-8.9/local/var/tmp/sage/build/sqlite-3270100
> >
> > 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: *** [all-start] Error 1
> >
>
> this is a familiar problem, due to skew clocks on your system, I
> suppose.
> Is /scratch/ a local filesystem? If not, you'd better try building on
> a local filesystem.
> (the problem is that sq
> In the upcoming release one should be able to use  sqlite from the
> system,
> thanks to https://trac.sagemath.org/ticket/29002
>
> One way around this should be to change the line
>
>sdh_configure
>
> near the bottom of  build/pkgs/sqlite/spkg-install
>
> to be
>
>sdh_configure --disable-maintainer-mode
>
> and try again running make again.
>
> (This change should make sqlite's ./configure less sensitive to skew
> clock)
>
> HTH,
> Dima
>
>
>
> > It seems CentOS doesn't like when I install Sage! Thank you all once
> again for all your helpful comments!
> >
> > On Wed, Mar 18, 2020 at 11:33 PM Dima Pasechnik 
> wrote:
> >>
> >> 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 installed, it should be a
> >> different issue.
> >>
> >> >
> >> > I currently have sage 8.9 installed on my personal laptop, so I
> figured I would stick with the same version that I know my code runs on.
> >> >
> >> > On Wed, Mar 18, 2020 at 9:56 PM Dima Pasechnik 
> wrote:
> >> >>
> >> >> 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 
> wrote:
> >> >> >
> >> >> > I am trying to install Sage version 8.9 on 

Re: [sage-support] Sage Crash Report

[Dima Pasechnik]

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 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  wrote:
>
>>
>>
>> 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, often used on HPC clusters.
>>
>> HPC clusters usually give users space for their home directories on
>> networked file systems, and for "scratch" partitions too.
>>
>>
>>> 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 file, it still has this as the last error:
>>>
>>> configure: error: in
>>> `/scratch/user/kbari/sage-8.9/local/var/tmp/sage/build/sqlite-3270100/src':
>>> configure: error: C compiler cannot create executables
>>>
>>> Best,
>>> Kash
>>>
>>> On Tue, Mar 24, 2020 at 7:53 AM Dima Pasechnik 
>>> wrote:
>>>
 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 when running make again:
 >
 > Error building Sage.
 >
 > The following package(s) may have failed to build (not necessarily
 > during this run of 'make all-start'):
 >
 > * package: sqlite-3270100
 >   log file: /scratch/user/kbari/sage-8.9/logs/pkgs/sqlite-3270100.log
 >   build directory:
 /scratch/user/kbari/sage-8.9/local/var/tmp/sage/build/sqlite-3270100
 >
 > 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: *** [all-start] Error 1
 >

 this is a familiar problem, due to skew clocks on your system, I
 suppose.
 Is /scratch/ a local filesystem? If not, you'd better try building on
 a local filesystem.
 (the problem is that sq
 In the upcoming release one should be able to use  sqlite from the
 system,
 thanks to https://trac.sagemath.org/ticket/29002

 One way around this should be to change the line

sdh_configure

 near the bottom of  build/pkgs/sqlite/spkg-install

 to be

sdh_configure --disable-maintainer-mode

 and try again running make again.

 (This change should make sqlite's ./configure less sensitive to skew
 clock)

 HTH,
 Dima



 > It seems CentOS doesn't like when I install Sage! Thank you all once
 again for all your helpful comments!
 >
 > On Wed, Mar 18, 2020 at 11:33 PM Dima Pasechnik 
 wrote:
 >>
 >> 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 installed, it should be a
 >> different issue.
 >>
 >> >
 >> > I currently have sage 8.9 installed on my personal laptop, so I
 figured I would stick with the same version that I know my code runs on.
 >> >
 >> > On Wed, Mar 18, 2020 at 9:56 PM Dima Pasechnik 
 wrote:
 >> >>
 >> >> 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 
 wrote:
 >> >> >
 >> >> > 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 and Debian and did not work for me and I was unsure if they would
 work on CentOS 7. I was able to 

Re: [sage-support] Sage Crash Report

[Kashif Bari]

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  wrote:

>
>
> 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, often used on HPC clusters.
>
> HPC clusters usually give users space for their home directories on
> networked file systems, and for "scratch" partitions too.
>
>
>> 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 file, it still has this as the last error:
>>
>> configure: error: in
>> `/scratch/user/kbari/sage-8.9/local/var/tmp/sage/build/sqlite-3270100/src':
>> configure: error: C compiler cannot create executables
>>
>> Best,
>> Kash
>>
>> On Tue, Mar 24, 2020 at 7:53 AM Dima Pasechnik  wrote:
>>
>>> 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 when running make again:
>>> >
>>> > Error building Sage.
>>> >
>>> > The following package(s) may have failed to build (not necessarily
>>> > during this run of 'make all-start'):
>>> >
>>> > * package: sqlite-3270100
>>> >   log file: /scratch/user/kbari/sage-8.9/logs/pkgs/sqlite-3270100.log
>>> >   build directory:
>>> /scratch/user/kbari/sage-8.9/local/var/tmp/sage/build/sqlite-3270100
>>> >
>>> > 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: *** [all-start] Error 1
>>> >
>>>
>>> this is a familiar problem, due to skew clocks on your system, I suppose.
>>> Is /scratch/ a local filesystem? If not, you'd better try building on
>>> a local filesystem.
>>> (the problem is that sq
>>> In the upcoming release one should be able to use  sqlite from the
>>> system,
>>> thanks to https://trac.sagemath.org/ticket/29002
>>>
>>> One way around this should be to change the line
>>>
>>>sdh_configure
>>>
>>> near the bottom of  build/pkgs/sqlite/spkg-install
>>>
>>> to be
>>>
>>>sdh_configure --disable-maintainer-mode
>>>
>>> and try again running make again.
>>>
>>> (This change should make sqlite's ./configure less sensitive to skew
>>> clock)
>>>
>>> HTH,
>>> Dima
>>>
>>>
>>>
>>> > It seems CentOS doesn't like when I install Sage! Thank you all once
>>> again for all your helpful comments!
>>> >
>>> > On Wed, Mar 18, 2020 at 11:33 PM Dima Pasechnik 
>>> wrote:
>>> >>
>>> >> 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 installed, it should be a
>>> >> different issue.
>>> >>
>>> >> >
>>> >> > I currently have sage 8.9 installed on my personal laptop, so I
>>> figured I would stick with the same version that I know my code runs on.
>>> >> >
>>> >> > On Wed, Mar 18, 2020 at 9:56 PM Dima Pasechnik 
>>> wrote:
>>> >> >>
>>> >> >> 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 
>>> wrote:
>>> >> >> >
>>> >> >> > 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 and Debian and did not work for me and I was unsure if they would
>>> work on CentOS 7. I was able to run ./configure without any issues and then
>>> when i did make, I received the following log file (attached) and error:
>>> >> >> >
>>> >> >> > Error building Sage.
>>> >> >> >
>>> >> >> > The following package(s) may have failed to build (not
>>> necessarily
>>> >> >> > during this run of 

Re: [sage-support] Sage Crash Report

[Dima Pasechnik]

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, often used on HPC clusters.

HPC clusters usually give users space for their home directories on
networked file systems, and for "scratch" partitions too.


> 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 file, it still has this as the last error:
>
> configure: error: in
> `/scratch/user/kbari/sage-8.9/local/var/tmp/sage/build/sqlite-3270100/src':
> configure: error: C compiler cannot create executables
>
> Best,
> Kash
>
> On Tue, Mar 24, 2020 at 7:53 AM Dima Pasechnik  wrote:
>
>> 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 when running make again:
>> >
>> > Error building Sage.
>> >
>> > The following package(s) may have failed to build (not necessarily
>> > during this run of 'make all-start'):
>> >
>> > * package: sqlite-3270100
>> >   log file: /scratch/user/kbari/sage-8.9/logs/pkgs/sqlite-3270100.log
>> >   build directory:
>> /scratch/user/kbari/sage-8.9/local/var/tmp/sage/build/sqlite-3270100
>> >
>> > 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: *** [all-start] Error 1
>> >
>>
>> this is a familiar problem, due to skew clocks on your system, I suppose.
>> Is /scratch/ a local filesystem? If not, you'd better try building on
>> a local filesystem.
>> (the problem is that sq
>> In the upcoming release one should be able to use  sqlite from the system,
>> thanks to https://trac.sagemath.org/ticket/29002
>>
>> One way around this should be to change the line
>>
>>sdh_configure
>>
>> near the bottom of  build/pkgs/sqlite/spkg-install
>>
>> to be
>>
>>sdh_configure --disable-maintainer-mode
>>
>> and try again running make again.
>>
>> (This change should make sqlite's ./configure less sensitive to skew
>> clock)
>>
>> HTH,
>> Dima
>>
>>
>>
>> > It seems CentOS doesn't like when I install Sage! Thank you all once
>> again for all your helpful comments!
>> >
>> > On Wed, Mar 18, 2020 at 11:33 PM Dima Pasechnik 
>> wrote:
>> >>
>> >> 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 installed, it should be a
>> >> different issue.
>> >>
>> >> >
>> >> > I currently have sage 8.9 installed on my personal laptop, so I
>> figured I would stick with the same version that I know my code runs on.
>> >> >
>> >> > On Wed, Mar 18, 2020 at 9:56 PM Dima Pasechnik 
>> wrote:
>> >> >>
>> >> >> 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 
>> wrote:
>> >> >> >
>> >> >> > 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 and Debian and did not work for me and I was unsure if they would
>> work on CentOS 7. I was able to run ./configure without any issues and then
>> when i did make, I received the following log file (attached) and error:
>> >> >> >
>> >> >> > Error building Sage.
>> >> >> >
>> >> >> > The following package(s) may have failed to build (not necessarily
>> >> >> > during this run of 'make all-start'):
>> >> >> >
>> >> >> > * package: mpfr-4.0.1.p0
>> >> >> >   log file:
>> /scratch/user/kbari/sage-8.9/logs/pkgs/mpfr-4.0.1.p0.log
>> >> >> >   build directory:
>> /scratch/user/kbari/sage-8.9/local/var/tmp/sage/build/mpfr-4.0.1.p0
>> >> >> >
>> >> >> > The build directory may contain configuration files and other
>> potentially
>> >> >> > helpful information. WARNING: if you now run 'make' again, the
>> build
>> >> >> > directory will, 

Re: [sage-support] Sage Crash Report

[Kashif Bari]

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 file, it still has this as the last error:

configure: error: in
`/scratch/user/kbari/sage-8.9/local/var/tmp/sage/build/sqlite-3270100/src':
configure: error: C compiler cannot create executables

Best,
Kash

On Tue, Mar 24, 2020 at 7:53 AM Dima Pasechnik  wrote:

> 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 when running make again:
> >
> > Error building Sage.
> >
> > The following package(s) may have failed to build (not necessarily
> > during this run of 'make all-start'):
> >
> > * package: sqlite-3270100
> >   log file: /scratch/user/kbari/sage-8.9/logs/pkgs/sqlite-3270100.log
> >   build directory:
> /scratch/user/kbari/sage-8.9/local/var/tmp/sage/build/sqlite-3270100
> >
> > 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: *** [all-start] Error 1
> >
>
> this is a familiar problem, due to skew clocks on your system, I suppose.
> Is /scratch/ a local filesystem? If not, you'd better try building on
> a local filesystem.
> (the problem is that sq
> In the upcoming release one should be able to use  sqlite from the system,
> thanks to https://trac.sagemath.org/ticket/29002
>
> One way around this should be to change the line
>
>sdh_configure
>
> near the bottom of  build/pkgs/sqlite/spkg-install
>
> to be
>
>sdh_configure --disable-maintainer-mode
>
> and try again running make again.
>
> (This change should make sqlite's ./configure less sensitive to skew clock)
>
> HTH,
> Dima
>
>
>
> > It seems CentOS doesn't like when I install Sage! Thank you all once
> again for all your helpful comments!
> >
> > On Wed, Mar 18, 2020 at 11:33 PM Dima Pasechnik 
> wrote:
> >>
> >> 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 installed, it should be a
> >> different issue.
> >>
> >> >
> >> > I currently have sage 8.9 installed on my personal laptop, so I
> figured I would stick with the same version that I know my code runs on.
> >> >
> >> > On Wed, Mar 18, 2020 at 9:56 PM Dima Pasechnik 
> wrote:
> >> >>
> >> >> 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 
> wrote:
> >> >> >
> >> >> > 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 and Debian and did not work for me and I was unsure if they would
> work on CentOS 7. I was able to run ./configure without any issues and then
> when i did make, I received the following log file (attached) and error:
> >> >> >
> >> >> > Error building Sage.
> >> >> >
> >> >> > The following package(s) may have failed to build (not necessarily
> >> >> > during this run of 'make all-start'):
> >> >> >
> >> >> > * package: mpfr-4.0.1.p0
> >> >> >   log file:
> /scratch/user/kbari/sage-8.9/logs/pkgs/mpfr-4.0.1.p0.log
> >> >> >   build directory:
> /scratch/user/kbari/sage-8.9/local/var/tmp/sage/build/mpfr-4.0.1.p0
> >> >> >
> >> >> > 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[1]: *** [all-start] Error 1
> >> >> > make[1]: Leaving directory `/scratch/user/kbari/sage-8.9'
> >> >> > make: *** [all] Error 2
> >> >> >
> >> >> >
> >> >> >  I have tried to contact the help and support for the cluster, but
> they do not know much about Sage. Any help would be greatly appreciated!
> Thank you for your time!
> >> >> >
> >> 

Re: [sage-support] Sage Crash Report

[Dima Pasechnik]

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 when running make again:
>
> Error building Sage.
>
> The following package(s) may have failed to build (not necessarily
> during this run of 'make all-start'):
>
> * package: sqlite-3270100
>   log file: /scratch/user/kbari/sage-8.9/logs/pkgs/sqlite-3270100.log
>   build directory: 
> /scratch/user/kbari/sage-8.9/local/var/tmp/sage/build/sqlite-3270100
>
> 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: *** [all-start] Error 1
>

this is a familiar problem, due to skew clocks on your system, I suppose.
Is /scratch/ a local filesystem? If not, you'd better try building on
a local filesystem.
(the problem is that sq
In the upcoming release one should be able to use  sqlite from the system,
thanks to https://trac.sagemath.org/ticket/29002

One way around this should be to change the line

   sdh_configure

near the bottom of  build/pkgs/sqlite/spkg-install

to be

   sdh_configure --disable-maintainer-mode

and try again running make again.

(This change should make sqlite's ./configure less sensitive to skew clock)

HTH,
Dima



> It seems CentOS doesn't like when I install Sage! Thank you all once again 
> for all your helpful comments!
>
> On Wed, Mar 18, 2020 at 11:33 PM Dima Pasechnik  wrote:
>>
>> 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 installed, it should be a
>> different issue.
>>
>> >
>> > I currently have sage 8.9 installed on my personal laptop, so I figured I 
>> > would stick with the same version that I know my code runs on.
>> >
>> > On Wed, Mar 18, 2020 at 9:56 PM Dima Pasechnik  wrote:
>> >>
>> >> 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  wrote:
>> >> >
>> >> > 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 and Debian and did not work for me and I was unsure if they 
>> >> > would work on CentOS 7. I was able to run ./configure without any 
>> >> > issues and then when i did make, I received the following log file 
>> >> > (attached) and error:
>> >> >
>> >> > Error building Sage.
>> >> >
>> >> > The following package(s) may have failed to build (not necessarily
>> >> > during this run of 'make all-start'):
>> >> >
>> >> > * package: mpfr-4.0.1.p0
>> >> >   log file: /scratch/user/kbari/sage-8.9/logs/pkgs/mpfr-4.0.1.p0.log
>> >> >   build directory: 
>> >> > /scratch/user/kbari/sage-8.9/local/var/tmp/sage/build/mpfr-4.0.1.p0
>> >> >
>> >> > 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[1]: *** [all-start] Error 1
>> >> > make[1]: Leaving directory `/scratch/user/kbari/sage-8.9'
>> >> > make: *** [all] Error 2
>> >> >
>> >> >
>> >> >  I have tried to contact the help and support for the cluster, but they 
>> >> > do not know much about Sage. Any help would be greatly appreciated! 
>> >> > Thank you for your time!
>> >> >
>> >> > --
>> >> > 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 
>> >> > https://groups.google.com/d/msgid/sage-support/9d94553b-f5b0-435b-93c5-7724c3422cc3%40googlegroups.com.
>> >>
>> >> --
>> >> 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 

Re: [sage-support] Sage Crash Report

[Kashif Bari]

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 package(s) may have failed to build (not necessarily
during this run of 'make all-start'):

* package: sqlite-3270100
  log file: /scratch/user/kbari/sage-8.9/logs/pkgs/sqlite-3270100.log
  build directory:
/scratch/user/kbari/sage-8.9/local/var/tmp/sage/build/sqlite-3270100

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: *** [all-start] Error 1

It seems CentOS doesn't like when I install Sage! Thank you all once again
for all your helpful comments!

On Wed, Mar 18, 2020 at 11:33 PM Dima Pasechnik  wrote:

> 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 installed, it should be a
> different issue.
>
> >
> > I currently have sage 8.9 installed on my personal laptop, so I figured
> I would stick with the same version that I know my code runs on.
> >
> > On Wed, Mar 18, 2020 at 9:56 PM Dima Pasechnik 
> wrote:
> >>
> >> 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  wrote:
> >> >
> >> > 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 and Debian and did not work for me and I was unsure if they would
> work on CentOS 7. I was able to run ./configure without any issues and then
> when i did make, I received the following log file (attached) and error:
> >> >
> >> > Error building Sage.
> >> >
> >> > The following package(s) may have failed to build (not necessarily
> >> > during this run of 'make all-start'):
> >> >
> >> > * package: mpfr-4.0.1.p0
> >> >   log file: /scratch/user/kbari/sage-8.9/logs/pkgs/mpfr-4.0.1.p0.log
> >> >   build directory:
> /scratch/user/kbari/sage-8.9/local/var/tmp/sage/build/mpfr-4.0.1.p0
> >> >
> >> > 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[1]: *** [all-start] Error 1
> >> > make[1]: Leaving directory `/scratch/user/kbari/sage-8.9'
> >> > make: *** [all] Error 2
> >> >
> >> >
> >> >  I have tried to contact the help and support for the cluster, but
> they do not know much about Sage. Any help would be greatly appreciated!
> Thank you for your time!
> >> >
> >> > --
> >> > 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
> https://groups.google.com/d/msgid/sage-support/9d94553b-f5b0-435b-93c5-7724c3422cc3%40googlegroups.com
> .
> >>
> >> --
> >> 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
> https://groups.google.com/d/msgid/sage-support/CAAWYfq0p1Z5t8KZmWvPqdqstOS77eaLveTs5w8qsOXp6EwK67w%40mail.gmail.com
> .
> >
> > --
> > 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
> https://groups.google.com/d/msgid/sage-support/CAJoD6MJFKbvovOSj_zLpBohUPtaPFYP%3Dpx8XKza5Lhb%2ByAiqFA%40mail.gmail.com
> .
>
> --
> 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 

Re: [sage-support] Sage Crash Report

[Dima Pasechnik]

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 installed, it should be a
different issue.

>
> I currently have sage 8.9 installed on my personal laptop, so I figured I 
> would stick with the same version that I know my code runs on.
>
> On Wed, Mar 18, 2020 at 9:56 PM Dima Pasechnik  wrote:
>>
>> 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  wrote:
>> >
>> > 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 and Debian and did not work for me and I was unsure if they would 
>> > work on CentOS 7. I was able to run ./configure without any issues and 
>> > then when i did make, I received the following log file (attached) and 
>> > error:
>> >
>> > Error building Sage.
>> >
>> > The following package(s) may have failed to build (not necessarily
>> > during this run of 'make all-start'):
>> >
>> > * package: mpfr-4.0.1.p0
>> >   log file: /scratch/user/kbari/sage-8.9/logs/pkgs/mpfr-4.0.1.p0.log
>> >   build directory: 
>> > /scratch/user/kbari/sage-8.9/local/var/tmp/sage/build/mpfr-4.0.1.p0
>> >
>> > 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[1]: *** [all-start] Error 1
>> > make[1]: Leaving directory `/scratch/user/kbari/sage-8.9'
>> > make: *** [all] Error 2
>> >
>> >
>> >  I have tried to contact the help and support for the cluster, but they do 
>> > not know much about Sage. Any help would be greatly appreciated! Thank you 
>> > for your time!
>> >
>> > --
>> > 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 
>> > https://groups.google.com/d/msgid/sage-support/9d94553b-f5b0-435b-93c5-7724c3422cc3%40googlegroups.com.
>>
>> --
>> 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 
>> https://groups.google.com/d/msgid/sage-support/CAAWYfq0p1Z5t8KZmWvPqdqstOS77eaLveTs5w8qsOXp6EwK67w%40mail.gmail.com.
>
> --
> 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 
> https://groups.google.com/d/msgid/sage-support/CAJoD6MJFKbvovOSj_zLpBohUPtaPFYP%3Dpx8XKza5Lhb%2ByAiqFA%40mail.gmail.com.

-- 
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 
https://groups.google.com/d/msgid/sage-support/CAAWYfq1iCUYRzukvrD95DKgg%3DtJhLoDHcDEmZiddwG%2BGADCDgg%40mail.gmail.com.

Re: [sage-support] Sage Crash Report

[Kashif Bari]

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 version that I know my code runs on.

On Wed, Mar 18, 2020 at 9:56 PM Dima Pasechnik  wrote:

> 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  wrote:
> >
> > 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
> and Debian and did not work for me and I was unsure if they would work on
> CentOS 7. I was able to run ./configure without any issues and then when i
> did make, I received the following log file (attached) and error:
> >
> > Error building Sage.
> >
> > The following package(s) may have failed to build (not necessarily
> > during this run of 'make all-start'):
> >
> > * package: mpfr-4.0.1.p0
> >   log file: /scratch/user/kbari/sage-8.9/logs/pkgs/mpfr-4.0.1.p0.log
> >   build directory:
> /scratch/user/kbari/sage-8.9/local/var/tmp/sage/build/mpfr-4.0.1.p0
> >
> > 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[1]: *** [all-start] Error 1
> > make[1]: Leaving directory `/scratch/user/kbari/sage-8.9'
> > make: *** [all] Error 2
> >
> >
> >  I have tried to contact the help and support for the cluster, but they
> do not know much about Sage. Any help would be greatly appreciated! Thank
> you for your time!
> >
> > --
> > 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
> https://groups.google.com/d/msgid/sage-support/9d94553b-f5b0-435b-93c5-7724c3422cc3%40googlegroups.com
> .
>
> --
> 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
> https://groups.google.com/d/msgid/sage-support/CAAWYfq0p1Z5t8KZmWvPqdqstOS77eaLveTs5w8qsOXp6EwK67w%40mail.gmail.com
> .
>

-- 
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 
https://groups.google.com/d/msgid/sage-support/CAJoD6MJFKbvovOSj_zLpBohUPtaPFYP%3Dpx8XKza5Lhb%2ByAiqFA%40mail.gmail.com.

Re: [sage-support] Sage Crash Report

[Dima Pasechnik]

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  wrote:
>
> 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 and 
> Debian and did not work for me and I was unsure if they would work on CentOS 
> 7. I was able to run ./configure without any issues and then when i did make, 
> I received the following log file (attached) and error:
>
> Error building Sage.
>
> The following package(s) may have failed to build (not necessarily
> during this run of 'make all-start'):
>
> * package: mpfr-4.0.1.p0
>   log file: /scratch/user/kbari/sage-8.9/logs/pkgs/mpfr-4.0.1.p0.log
>   build directory: 
> /scratch/user/kbari/sage-8.9/local/var/tmp/sage/build/mpfr-4.0.1.p0
>
> 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[1]: *** [all-start] Error 1
> make[1]: Leaving directory `/scratch/user/kbari/sage-8.9'
> make: *** [all] Error 2
>
>
>  I have tried to contact the help and support for the cluster, but they do 
> not know much about Sage. Any help would be greatly appreciated! Thank you 
> for your time!
>
> --
> 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 
> https://groups.google.com/d/msgid/sage-support/9d94553b-f5b0-435b-93c5-7724c3422cc3%40googlegroups.com.

-- 
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 
https://groups.google.com/d/msgid/sage-support/CAAWYfq0p1Z5t8KZmWvPqdqstOS77eaLveTs5w8qsOXp6EwK67w%40mail.gmail.com.

Re: [sage-support] Sage Crash Report

[kashbari]

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 https://github.com/conda-forge/sage-feedstock#installing-sage
> 
> Isuru
> 
>> On Wed, Mar 18, 2020 at 6:00 PM Kashif Bari  wrote:
>> 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 and 
>> Debian and did not work for me and I was unsure if they would work on CentOS 
>> 7. I was able to run ./configure without any issues and then when i did 
>> make, I received the following log file (attached) and error: 
>> 
>> Error building Sage.
>> 
>> The following package(s) may have failed to build (not necessarily
>> during this run of 'make all-start'):
>> 
>> * package: mpfr-4.0.1.p0
>>   log file: /scratch/user/kbari/sage-8.9/logs/pkgs/mpfr-4.0.1.p0.log
>>   build directory: 
>> /scratch/user/kbari/sage-8.9/local/var/tmp/sage/build/mpfr-4.0.1.p0
>> 
>> 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[1]: *** [all-start] Error 1
>> make[1]: Leaving directory `/scratch/user/kbari/sage-8.9'
>> make: *** [all] Error 2
>> 
>> 
>>  I have tried to contact the help and support for the cluster, but they do 
>> not know much about Sage. Any help would be greatly appreciated! Thank you 
>> for your time!
>> -- 
>> 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 
>> https://groups.google.com/d/msgid/sage-support/9d94553b-f5b0-435b-93c5-7724c3422cc3%40googlegroups.com.
> 
> -- 
> 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 
> https://groups.google.com/d/msgid/sage-support/CA%2B01voPejK9ynCNn_JFUGWcA%3DP4X4wM2bjdpCF8fk%2Bw1Ft-KPw%40mail.gmail.com.

-- 
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 
https://groups.google.com/d/msgid/sage-support/876852E3-54A1-4672-A0D2-5F21DEB5E37C%40gmail.com.

Re: [sage-support] Sage Crash Report

[Isuru Fernando]

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 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 https://github.com/conda-forge/sage-feedstock#installing-sage
>
> Isuru
>
> On Wed, Mar 18, 2020 at 6:00 PM Kashif Bari  wrote:
>
>> 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
>> and Debian and did not work for me and I was unsure if they would work on
>> CentOS 7. I was able to run ./configure without any issues and then when i
>> did make, I received the following log file (attached) and error:
>>
>> Error building Sage.
>>
>> The following package(s) may have failed to build (not necessarily
>> during this run of 'make all-start'):
>>
>> * package: mpfr-4.0.1.p0
>>   log file: /scratch/user/kbari/sage-8.9/logs/pkgs/mpfr-4.0.1.p0.log
>>   build directory:
>> /scratch/user/kbari/sage-8.9/local/var/tmp/sage/build/mpfr-4.0.1.p0
>>
>> 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[1]: *** [all-start] Error 1
>> make[1]: Leaving directory `/scratch/user/kbari/sage-8.9'
>> make: *** [all] Error 2
>>
>>
>>  I have tried to contact the help and support for the cluster, but they
>> do not know much about Sage. Any help would be greatly appreciated! Thank
>> you for your time!
>>
>> --
>> 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
>> https://groups.google.com/d/msgid/sage-support/9d94553b-f5b0-435b-93c5-7724c3422cc3%40googlegroups.com
>> 
>> .
>>
> --
> 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
> https://groups.google.com/d/msgid/sage-support/CA%2B01voPejK9ynCNn_JFUGWcA%3DP4X4wM2bjdpCF8fk%2Bw1Ft-KPw%40mail.gmail.com
> 
> .
>
> --
> 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
> https://groups.google.com/d/msgid/sage-support/5F5071CF-92DB-426A-A758-858CDA89EA00%40gmail.com
> 
> .
>

-- 
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 
https://groups.google.com/d/msgid/sage-support/CA%2B01voMXaTQQgh9idwDxxeJYXHQ4N1x1AAL7Dc9s_hDMQsWzng%40mail.gmail.com.

Re: [sage-support] Sage Crash Report

[kashbari]

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. 
> 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 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 and 
>> Debian and did not work for me and I was unsure if they would work on CentOS 
>> 7. I was able to run ./configure without any issues and then when i did 
>> make, I received the following log file (attached) and error: 
>> 
>> Error building Sage.
>> 
>> The following package(s) may have failed to build (not necessarily
>> during this run of 'make all-start'):
>> 
>> * package: mpfr-4.0.1.p0
>>   log file: /scratch/user/kbari/sage-8.9/logs/pkgs/mpfr-4.0.1.p0.log
>>   build directory: 
>> /scratch/user/kbari/sage-8.9/local/var/tmp/sage/build/mpfr-4.0.1.p0
>> 
>> 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[1]: *** [all-start] Error 1
>> make[1]: Leaving directory `/scratch/user/kbari/sage-8.9'
>> make: *** [all] Error 2
>> 
>> 
>>  I have tried to contact the help and support for the cluster, but they do 
>> not know much about Sage. Any help would be greatly appreciated! Thank you 
>> for your time!
>> -- 
>> 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 
>> https://groups.google.com/d/msgid/sage-support/9d94553b-f5b0-435b-93c5-7724c3422cc3%40googlegroups.com.
> 
> -- 
> 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 
> https://groups.google.com/d/msgid/sage-support/CA%2B01voPejK9ynCNn_JFUGWcA%3DP4X4wM2bjdpCF8fk%2Bw1Ft-KPw%40mail.gmail.com.

-- 
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 
https://groups.google.com/d/msgid/sage-support/5F5071CF-92DB-426A-A758-858CDA89EA00%40gmail.com.

Re: [sage-support] Sage Crash Report

[Isuru Fernando]

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 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
> and Debian and did not work for me and I was unsure if they would work on
> CentOS 7. I was able to run ./configure without any issues and then when i
> did make, I received the following log file (attached) and error:
>
> Error building Sage.
>
> The following package(s) may have failed to build (not necessarily
> during this run of 'make all-start'):
>
> * package: mpfr-4.0.1.p0
>   log file: /scratch/user/kbari/sage-8.9/logs/pkgs/mpfr-4.0.1.p0.log
>   build directory:
> /scratch/user/kbari/sage-8.9/local/var/tmp/sage/build/mpfr-4.0.1.p0
>
> 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[1]: *** [all-start] Error 1
> make[1]: Leaving directory `/scratch/user/kbari/sage-8.9'
> make: *** [all] Error 2
>
>
>  I have tried to contact the help and support for the cluster, but they do
> not know much about Sage. Any help would be greatly appreciated! Thank you
> for your time!
>
> --
> 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
> https://groups.google.com/d/msgid/sage-support/9d94553b-f5b0-435b-93c5-7724c3422cc3%40googlegroups.com
> 
> .
>

-- 
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 
https://groups.google.com/d/msgid/sage-support/CA%2B01voPejK9ynCNn_JFUGWcA%3DP4X4wM2bjdpCF8fk%2Bw1Ft-KPw%40mail.gmail.com.

Re: [sage-support] Sage Crash report

[Dima Pasechnik]

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 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
>   build directory: /usr/local/CA/sage-9.0/local/var/tmp/sage/build/r-3.6.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.
>
> Makefile:31: recipe for target 'all-start' failed
> make[1]: *** [all-start] Error 1
> make[1]: Leaving directory '/usr/local/CA/sage-9.0'
> Makefile:13: recipe for target 'all' failed
>
> I then tried to run sage, getting the following error log.
>
> ***
>
> IPython post-mortem report
>
> {'commit_hash': u'033ab93c7',
>  'commit_source': 'installation',
>  'default_encoding': 'UTF-8',
>  'ipython_path': 
> '/usr/local/CA/sage-8.8/local/lib/python2.7/site-packages/IPython',
>  'ipython_version': '5.8.0',
>  'os_name': 'posix',
>  'platform': 'Linux-5.0.0-37-generic-x86_64-with-debian-buster-sid',
>  'sys_executable': '/usr/local/CA/sage-8.8/local/bin/python2',
>  'sys_platform': 'linux2',
>  'sys_version': '2.7.15 (default, Sep  4 2019, 11:48:34) \n[GCC 4.8.5 
> 20150623 (Red Hat 4.8.5-39)]'}
>
> ***
>
>
>
> ***
>
> Crash traceback:
>
> ---
> ---
> ImportError Python 2.7.15: /usr/local/CA/sage-8.8/local/bin/python2
>Wed Jan  8 16:34:13 2020
> A problem occurred executing Python code.  Here is the sequence of function
> calls leading up to the error, with the most recent (innermost) call last.
> /usr/local/CA/sage-8.8/src/bin/sage-ipython in ()
>   1 #!/usr/bin/env sage-python23
>   2 # -*- coding: utf-8 -*-
>   3 """
>   4 Sage IPython startup script.
>   5 """
>   6
>   7 # Display startup banner. Do this before anything else to give the 
> user
>   8 # early feedback that Sage is starting.
>   9 from sage.misc.banner import banner
>  10 banner()
>  11
>  12 from sage.repl.interpreter import SageTerminalApp
>  13
>  14 app = SageTerminalApp.instance()
> ---> 15 app.initialize()
> global app.initialize =  >
>  16 app.start()
>
>  in initialize(self= object>, argv=None)
>
> /usr/local/CA/sage-8.8/local/lib/python2.7/site-packages/traitlets/config/application.pyc
>  in catch_config_error(method=, 
> app=, *args=(None,), 
> **kwargs={})
>  72 TRAITLETS_APPLICATION_RAISE_CONFIG_FILE_ERROR = False
>  73 else:
>  74 raise ValueError("Unsupported value for environment variable: 
> 'TRAITLETS_APPLICATION_RAISE_CONFIG_FILE_ERROR' is set to '%s' which is none 
> of  {'0', '1', 'false', 'true', ''}."% _envvar )
>  75
>  76
>  77 @decorator
>  78 def catch_config_error(method, app, *args, **kwargs):
>  79 """Method decorator for catching invalid config 
> (Trait/ArgumentErrors) during init.
>  80
>  81 On a TraitError (generally caused by bad config), this will print 
> the trait's
>  82 message, and exit the app.
>  83
>  84 For use on init methods, to prevent invoking excepthook on 
> invalid input.
>  85 """
>  86 try:
> ---> 87 return method(app, *args, **kwargs)
> method = 
> app = 
> args = (None,)
> kwargs = {}
>  88 except (TraitError, ArgumentError) as e:
>  89 app.print_help()
>  90 app.log.fatal("Bad config encountered during initialization:")
>  91 app.log.fatal(str(e))
>  92 app.log.debug("Config at the time: %s", app.config)
>  93 app.exit(1)
>  94
>  95
>  96 class ApplicationError(Exception):
>  97 pass
>  98
>  99
> 100 class LevelFormatter(logging.Formatter):
> 101 """Formatter with additional `highlevel` record
> 102
>
> /usr/local/CA/sage-8.8/local/lib/python2.7/site-packages/IPython/terminal/ipapp.pyc
>  in initialize(self=, argv=None)
> 301
> 302 return super(TerminalIPythonApp, 
> self).parse_command_line(argv)
> 303
> 304 @catch_config_error
> 305 def initialize(self, 

Re: [sage-support] Sage Crash Report

[Dima Pasechnik]

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 to start a sage build which was working few days
> earlier:
>
> ImportError: libntl.so.43: cannot open shared object file: No such file
> or directory
>
> By looking at the recent updates made by the package manager
> ( grep -i ntl /var/log/pacman.log ) I found out that the system version
> of ntl had been updated recently. Actually I do not use ntl outside of
> sage and guess it was installed as a dependency of some program I do not
> use anymore.


Sage is by default trying to use system's NTL. So, yes, if you happen to
update it then you would need to re-run ./configure and make

So I removed the system ntl and rebuilt sage (make
> distclean && make) with the hope that sage would then install its own
> correct version of ntl. It solved the problem. Maybe only rebuilding was
> needed?
>
> About the packaged version of sage I do not know, for I am not using it.
>
> Best,
>
> Jean-Florent.
>
> Le 03/01/2020 à 02:01, Artemis Heller a écrit :
> > 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 problem, but somehow pacman still
> installs
> > in the system python which is 3.8.1 for me.
> >
> > Let me know if you'd need any more info from my part!
> >
> > Best
> >
>
> --
> 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
> https://groups.google.com/d/msgid/sage-support/48413c80-ee1c-1638-2bdc-f16cd24ffa85%40uca.fr
> .
>

-- 
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 
https://groups.google.com/d/msgid/sage-support/CAAWYfq1wPdfTJXgv7Q_%3D8TmUXdMZSXK830PaqqFD-P_o2ih%3DXg%40mail.gmail.com.

Re: [sage-support] Sage Crash Report

[Dima Pasechnik]

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 8.9 from pacman with a pyenv of 3.7.4 in 
> case python 3.8 is the problem, but somehow pacman still installs in the 
> system python which is 3.8.1 for me.
>
> Let me know if you'd need any more info from my part!
>
> Best
>
> --
> 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 
> https://groups.google.com/d/msgid/sage-support/CAA3%2Bp72qzOVgYuCp1_eryRWxSOaqQooP62yiCeUyg_NPqdUhQQ%40mail.gmail.com.

-- 
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 
https://groups.google.com/d/msgid/sage-support/CAAWYfq2VorOH8m%3ShcZ%2BvYc7Yo026GmvmKdbRL%2BL5O0Heww%40mail.gmail.com.

Re: [sage-support] Sage Crash Report

[Eric Gourgoulhon]

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 18.04, and you're 
> trying a tarball fot 16.04. 
>
> Tarball for 18.04 is not ready yet, I think. 
>


The SageMath 8.9 binaries for Ubuntu 18.04 are now available from the 
download page:
https://www.sagemath.org/download-linux.html

Best wishes,

Eric.

-- 
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 
https://groups.google.com/d/msgid/sage-support/8589d46e-d664-45e4-8585-a5a6bb4ee1b9%40googlegroups.com.

Re: [sage-support] Sage Crash Report

[Dima Pasechnik]

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 source...

>
>
>
>
> ***
>
> IPython post-mortem report
>
> {'commit_hash': u'033ab93c7',
>  'commit_source': 'installation',
>  'default_encoding': 'UTF-8',
>  'ipython_path': 
> '/home/kapcak/Documents/Sage89/sage-8.9-Ubuntu_16.04-x86_64/SageMath/local/lib/python2.7/site-packages/IPython',
>  'ipython_version': '5.8.0',
>  'os_name': 'posix',
>  'platform': 'Linux-5.3.0-18-generic-x86_64-with-debian-buster-sid',
>  'sys_executable': 
> '/home/kapcak/Documents/Sage89/sage-8.9-Ubuntu_16.04-x86_64/SageMath/local/bin/python2',
>  'sys_platform': 'linux2',
>  'sys_version': '2.7.15 (default, Oct  4 2019, 05:22:55) \n[GCC 7.4.0]'}
>
> ***
>
>
>
> ***
>
> Crash traceback:
>
> ---
> ---
> ImportErrorPython 2.7.15: 
> /home/kapcak/Documents/Sage89/sage-8.9-Ubuntu_16.04-x86_64/SageMath/local/bin/python2
>Sat Oct 19 01:57:57 2019
> A problem occurred executing Python code.  Here is the sequence of function
> calls leading up to the error, with the most recent (innermost) call last.
> /home/kapcak/Documents/Sage89/sage-8.9-Ubuntu_16.04-x86_64/SageMath/src/bin/sage-ipython
>  in ()
>   1 #!/usr/bin/env sage-python23
>   2 # -*- coding: utf-8 -*-
>   3 """
>   4 Sage IPython startup script.
>   5 """
>   6
>   7 # Display startup banner. Do this before anything else to give the 
> user
>   8 # early feedback that Sage is starting.
>   9 from sage.misc.banner import banner
>  10 banner()
>  11
>  12 from sage.repl.interpreter import SageTerminalApp
>  13
>  14 app = SageTerminalApp.instance()
> ---> 15 app.initialize()
> global app.initialize =  >
>  16 app.start()
>
> 
>  in initialize(self=, argv=None)
>
> /home/kapcak/Documents/Sage89/sage-8.9-Ubuntu_16.04-x86_64/SageMath/local/lib/python2.7/site-packages/traitlets/config/application.py
>  in catch_config_error(method=, 
> app=, *args=(None,), 
> **kwargs={})
>  72 TRAITLETS_APPLICATION_RAISE_CONFIG_FILE_ERROR = False
>  73 else:
>  74 raise ValueError("Unsupported value for environment variable: 
> 'TRAITLETS_APPLICATION_RAISE_CONFIG_FILE_ERROR' is set to '%s' which is none 
> of  {'0', '1', 'false', 'true', ''}."% _envvar )
>  75
>  76
>  77 @decorator
>  78 def catch_config_error(method, app, *args, **kwargs):
>  79 """Method decorator for catching invalid config 
> (Trait/ArgumentErrors) during init.
>  80
>  81 On a TraitError (generally caused by bad config), this will print 
> the trait's
>  82 message, and exit the app.
>  83
>  84 For use on init methods, to prevent invoking excepthook on 
> invalid input.
>  85 """
>  86 try:
> ---> 87 return method(app, *args, **kwargs)
> method = 
> app = 
> args = (None,)
> kwargs = {}
>  88 except (TraitError, ArgumentError) as e:
>  89 app.print_help()
>  90 app.log.fatal("Bad config encountered during initialization:")
>  91 app.log.fatal(str(e))
>  92 app.log.debug("Config at the time: %s", app.config)
>  93 app.exit(1)
>  94
>  95
>  96 class ApplicationError(Exception):
>  97 pass
>  98
>  99
> 100 class LevelFormatter(logging.Formatter):
> 101 """Formatter with additional `highlevel` record
> 102
>
> /home/kapcak/Documents/Sage89/sage-8.9-Ubuntu_16.04-x86_64/SageMath/local/lib/python2.7/site-packages/IPython/terminal/ipapp.py
>  in initialize(self=, argv=None)
> 301
> 302 return super(TerminalIPythonApp, 
> self).parse_command_line(argv)
> 303
> 304 @catch_config_error
> 305 def initialize(self, argv=None):
> 306 """Do actions after construct, but before starting the app."""
> 307 super(TerminalIPythonApp, self).initialize(argv)
> 308 if self.subapp is not None:
> 309 # don't bother initializing further, starting subapp
> 310 return
> 311 # print self.extra_args
> 312 if self.extra_args and not self.something_to_run:
> 313 self.file_to_run = self.extra_args[0]
> 314 self.init_path()
> 315 # create the shell
> --> 316 self.init_shell()
>

Re: [sage-support] Sage Crash Report

[Dima Pasechnik]

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.

HTH
Dima

> 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:
> ┌┐
> │ SageMath version 8.9, Release Date: 2019-09-29  
> │
> │ Using Python 2.7.15. Type "help()" for help.
> │
> └┘
> and then issued the Oops message.
>
> As I recall I went through the very same sequence with SAGE 8.8 & it's worked 
> just fine...Dave
>
> --
> 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 
> https://groups.google.com/d/msgid/sage-support/CADw54_ZY-wZjmYoUTeTvnjx7OCzP7yrR0d7HyeRRXVYzTFT94g%40mail.gmail.com.

-- 
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 
https://groups.google.com/d/msgid/sage-support/CAAWYfq2zQ5bEwZK3WWfwAUs2DSnW%3DkcCUD1GSXbNYp7%2B8sRj5A%40mail.gmail.com.

Re: [sage-support] sage crash report

[Vincent Delecroix]

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 has already been reported and
apparently fixed

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932367

Good luck
Vincent

Le 02/09/2019 à 20:39, o.castillo.felis...@gmail.com a écrit :

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 all possible help, since this is one of the programs
I use in my daily work.



--
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 
https://groups.google.com/d/msgid/sage-support/9533d412-2819-4b41-928d-6947e754f04d%40gmail.com.

Re: [sage-support] Sage Crash Report

[Dima Pasechnik]

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 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 intitialize:
> carlos@arroway:~$ sage
> ┌┐
> │ SageMath version 8.6, Release Date: 2019-01-15 │
> │ Using Python 2.7.16. Type "help()" for help.   │
> └┘
>
> **
>
> Oops, Sage crashed. We do our best to make it stable, but...
>
> Best Regards,
> Carlos
>
>
> --
> Carlos Mauricio Silva
> Departamento de Física
> Instituto Politécnico Superior "Gral. San Martín"
> Universidad Nacional de Rosario ~ República Argentina
>
> --
> 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 
> https://groups.google.com/d/msgid/sage-support/CALgKwyrf%3D6GJ4x%2BH41HmrhHspf-tk02Zu1MtSj8qo5_TAMWg8g%40mail.gmail.com.

-- 
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 
https://groups.google.com/d/msgid/sage-support/CAAWYfq0%2Bc%2BH8oLGwL71iD0YhKJRzpH3K7RsQPmcUrhaEdH9V9g%40mail.gmail.com.

Re: [sage-support] Sage Crash Report

[Vincent Delecroix]

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
these.

Note that this is documented at

   http://doc.sagemath.org/html/en/installation/linux.html#sec-gnu-linux

Vincent

Le 01/05/2019 à 14:35, Erik Wallace a écrit :

Here is the output:

$ apt list --installed | grep sagemath

sagemath-common/bionic,bionic,now 8.1-7ubuntu1 all [installed]

$ ls -l /usr/lib/python2.7/dist-packages/sage/structure/

total 808
-rw-r--r-- 1 root root   641 Dec  7  2017 all.py
-rw-r--r-- 1 root root  1114 Apr 15 21:51 all.pyc
-rw-r--r-- 1 root root   986 Dec  7  2017 category_object.pxd
-rw-r--r-- 1 root root   376 Dec  7  2017 coerce_actions.pxd
-rw-r--r-- 1 root root   851 Dec  7  2017 coerce_dict.pxd
-rw-r--r-- 1 root root   953 Dec  7  2017 coerce_exceptions.py
-rw-r--r-- 1 root root   868 Apr 15 21:51 coerce_exceptions.pyc
-rw-r--r-- 1 root root   463 Dec  7  2017 coerce_maps.pxd
-rw-r--r-- 1 root root  1086 Dec  7  2017 coerce.pxd
-rw-r--r-- 1 root root   154 Dec  7  2017 debug_options.pxd
-rw-r--r-- 1 root root 19675 Dec  7  2017 dynamic_class.py
-rw-r--r-- 1 root root 18719 Apr 15 21:51 dynamic_class.pyc
-rw-r--r-- 1 root root  7836 Dec  7  2017 element.pxd
-rw-r--r-- 1 root root   265 Dec  7  2017 element_wrapper.pxd
-rw-r--r-- 1 root root  3780 Dec  7  2017 factorization_integer.py
-rw-r--r-- 1 root root  4282 Apr 15 21:51 factorization_integer.pyc
-rw-r--r-- 1 root root 39922 Dec  7  2017 factorization.py
-rw-r--r-- 1 root root 41925 Apr 15 21:51 factorization.pyc
-rw-r--r-- 1 root root 15267 Dec  7  2017 formal_sum.py
-rw-r--r-- 1 root root 16707 Apr 15 21:51 formal_sum.pyc
-rw-r--r-- 1 root root  2035 Dec  7  2017 gens_py.py
-rw-r--r-- 1 root root  1795 Apr 15 21:51 gens_py.pyc
-rw-r--r-- 1 root root 66908 Dec  7  2017 global_options.py
-rw-r--r-- 1 root root 63304 Apr 15 21:51 global_options.pyc
-rw-r--r-- 1 root root  7908 Dec  7  2017 graphics_file.py
-rw-r--r-- 1 root root  9747 Apr 15 21:51 graphics_file.pyc
-rw-r--r-- 1 root root 26183 Dec  7  2017 indexed_generators.py
-rw-r--r-- 1 root root 24447 Apr 15 21:51 indexed_generators.pyc
-rw-r--r-- 1 root root 0 Dec  7  2017 __init__.py
-rw-r--r-- 1 root root   146 Apr 15 21:51 __init__.pyc
-rw-r--r-- 1 root root  2043 Dec  7  2017 list_clone.pxd
-rw-r--r-- 1 root root  6718 Dec  7  2017 list_clone_timings.py
-rw-r--r-- 1 root root  7534 Apr 15 21:51 list_clone_timings.pyc
-rw-r--r-- 1 root root   532 Dec  7  2017 mutability.pxd
-rw-r--r-- 1 root root   646 Dec  7  2017 nonexact.py
-rw-r--r-- 1 root root  1343 Apr 15 21:51 nonexact.pyc
-rw-r--r-- 1 root root   538 Dec  7  2017 parent_base.pxd
-rw-r--r-- 1 root root   743 Dec  7  2017 parent_gens.pxd
-rw-r--r-- 1 root root  1314 Dec  7  2017 parent_old.pxd
-rw-r--r-- 1 root root  4142 Dec  7  2017 parent.pxd
drwxr-xr-x 2 root root  4096 Apr 15 21:51 proof
-rw-r--r-- 1 root root  4892 Dec  7  2017 richcmp.pxd
-rw-r--r-- 1 root root32 Dec  7  2017 sage_object.pxd
-rw-r--r-- 1 root root 26596 Dec  7  2017 sequence.py
-rw-r--r-- 1 root root 27439 Apr 15 21:51 sequence.pyc
-rw-r--r-- 1 root root 17209 Dec  7  2017 set_factories_example.py
-rw-r--r-- 1 root root 20559 Apr 15 21:51 set_factories_example.pyc
-rw-r--r-- 1 root root 41168 Dec  7  2017 set_factories.py
-rw-r--r-- 1 root root 43362 Apr 15 21:51 set_factories.pyc
-rw-r--r-- 1 root root  1751 Dec  7  2017 test_factory.py
-rw-r--r-- 1 root root  1871 Apr 15 21:51 test_factory.pyc
-rw-r--r-- 1 root root 50516 Dec  7  2017 unique_representation.py
-rw-r--r-- 1 root root 51060 Apr 15 21:51 unique_representation.pyc

On Sun, Apr 28, 2019 at 4:46 PM Vincent Delecroix <20100.delecr...@gmail.com>
wrote:


I do not see anything obvious in the crash report that explains the
problem. For each thing below could you copy paste the full output
of what appears in the console.

1. The list of sagemath packages installed

 $ apt list --installed | grep sagemath

2. Files in /usr/lib/python2.7/dist-packages/sage/structure via

 $ ls -l /usr/lib/python2.7/dist-packages/sage/structure/

Le 28/04/2019 à 21:05, Erik Wallace a écrit :

Yes, I downloaded via apt. The supporting python packages were also
downloaded via apt.

On Sat, Apr 27, 2019 at 5:08 PM Vincent Delecroix <

20100.delecr...@gmail.com>

wrote:


Hello,

What did you downloaded exactly? You meant that you installed
Sage from via the package manager (apt)?

Best
Vincent

Le 23/04/2019 à 03:22, Erik Wallace a écrit :

Hello,
  I am submitting this crash report. I downloaded sage from the

Ubuntu

repo. Please let me know, how I can fix this. Thanks.
Sincerely,

Erik



--
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 

Re: [sage-support] Sage Crash Report

[Erik Wallace]

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 -l /usr/lib/python2.7/dist-packages/sage/structure/
>
> total 808
> -rw-r--r-- 1 root root   641 Dec  7  2017 all.py
> -rw-r--r-- 1 root root  1114 Apr 15 21:51 all.pyc
> -rw-r--r-- 1 root root   986 Dec  7  2017 category_object.pxd
> -rw-r--r-- 1 root root   376 Dec  7  2017 coerce_actions.pxd
> -rw-r--r-- 1 root root   851 Dec  7  2017 coerce_dict.pxd
> -rw-r--r-- 1 root root   953 Dec  7  2017 coerce_exceptions.py
> -rw-r--r-- 1 root root   868 Apr 15 21:51 coerce_exceptions.pyc
> -rw-r--r-- 1 root root   463 Dec  7  2017 coerce_maps.pxd
> -rw-r--r-- 1 root root  1086 Dec  7  2017 coerce.pxd
> -rw-r--r-- 1 root root   154 Dec  7  2017 debug_options.pxd
> -rw-r--r-- 1 root root 19675 Dec  7  2017 dynamic_class.py
> -rw-r--r-- 1 root root 18719 Apr 15 21:51 dynamic_class.pyc
> -rw-r--r-- 1 root root  7836 Dec  7  2017 element.pxd
> -rw-r--r-- 1 root root   265 Dec  7  2017 element_wrapper.pxd
> -rw-r--r-- 1 root root  3780 Dec  7  2017 factorization_integer.py
> -rw-r--r-- 1 root root  4282 Apr 15 21:51 factorization_integer.pyc
> -rw-r--r-- 1 root root 39922 Dec  7  2017 factorization.py
> -rw-r--r-- 1 root root 41925 Apr 15 21:51 factorization.pyc
> -rw-r--r-- 1 root root 15267 Dec  7  2017 formal_sum.py
> -rw-r--r-- 1 root root 16707 Apr 15 21:51 formal_sum.pyc
> -rw-r--r-- 1 root root  2035 Dec  7  2017 gens_py.py
> -rw-r--r-- 1 root root  1795 Apr 15 21:51 gens_py.pyc
> -rw-r--r-- 1 root root 66908 Dec  7  2017 global_options.py
> -rw-r--r-- 1 root root 63304 Apr 15 21:51 global_options.pyc
> -rw-r--r-- 1 root root  7908 Dec  7  2017 graphics_file.py
> -rw-r--r-- 1 root root  9747 Apr 15 21:51 graphics_file.pyc
> -rw-r--r-- 1 root root 26183 Dec  7  2017 indexed_generators.py
> -rw-r--r-- 1 root root 24447 Apr 15 21:51 indexed_generators.pyc
> -rw-r--r-- 1 root root 0 Dec  7  2017 __init__.py
> -rw-r--r-- 1 root root   146 Apr 15 21:51 __init__.pyc
> -rw-r--r-- 1 root root  2043 Dec  7  2017 list_clone.pxd
> -rw-r--r-- 1 root root  6718 Dec  7  2017 list_clone_timings.py
> -rw-r--r-- 1 root root  7534 Apr 15 21:51 list_clone_timings.pyc
> -rw-r--r-- 1 root root   532 Dec  7  2017 mutability.pxd
> -rw-r--r-- 1 root root   646 Dec  7  2017 nonexact.py
> -rw-r--r-- 1 root root  1343 Apr 15 21:51 nonexact.pyc
> -rw-r--r-- 1 root root   538 Dec  7  2017 parent_base.pxd
> -rw-r--r-- 1 root root   743 Dec  7  2017 parent_gens.pxd
> -rw-r--r-- 1 root root  1314 Dec  7  2017 parent_old.pxd
> -rw-r--r-- 1 root root  4142 Dec  7  2017 parent.pxd
> drwxr-xr-x 2 root root  4096 Apr 15 21:51 proof
> -rw-r--r-- 1 root root  4892 Dec  7  2017 richcmp.pxd
> -rw-r--r-- 1 root root32 Dec  7  2017 sage_object.pxd
> -rw-r--r-- 1 root root 26596 Dec  7  2017 sequence.py
> -rw-r--r-- 1 root root 27439 Apr 15 21:51 sequence.pyc
> -rw-r--r-- 1 root root 17209 Dec  7  2017 set_factories_example.py
> -rw-r--r-- 1 root root 20559 Apr 15 21:51 set_factories_example.pyc
> -rw-r--r-- 1 root root 41168 Dec  7  2017 set_factories.py
> -rw-r--r-- 1 root root 43362 Apr 15 21:51 set_factories.pyc
> -rw-r--r-- 1 root root  1751 Dec  7  2017 test_factory.py
> -rw-r--r-- 1 root root  1871 Apr 15 21:51 test_factory.pyc
> -rw-r--r-- 1 root root 50516 Dec  7  2017 unique_representation.py
> -rw-r--r-- 1 root root 51060 Apr 15 21:51 unique_representation.pyc
>
> On Sun, Apr 28, 2019 at 4:46 PM Vincent Delecroix <
> 20100.delecr...@gmail.com> wrote:
>
>> I do not see anything obvious in the crash report that explains the
>> problem. For each thing below could you copy paste the full output
>> of what appears in the console.
>>
>> 1. The list of sagemath packages installed
>>
>> $ apt list --installed | grep sagemath
>>
>> 2. Files in /usr/lib/python2.7/dist-packages/sage/structure via
>>
>> $ ls -l /usr/lib/python2.7/dist-packages/sage/structure/
>>
>> Le 28/04/2019 à 21:05, Erik Wallace a écrit :
>> > Yes, I downloaded via apt. The supporting python packages were also
>> > downloaded via apt.
>> >
>> > On Sat, Apr 27, 2019 at 5:08 PM Vincent Delecroix <
>> 20100.delecr...@gmail.com>
>> > wrote:
>> >
>> >> Hello,
>> >>
>> >> What did you downloaded exactly? You meant that you installed
>> >> Sage from via the package manager (apt)?
>> >>
>> >> Best
>> >> Vincent
>> >>
>> >> Le 23/04/2019 à 03:22, Erik Wallace a écrit :
>> >>> Hello,
>> >>>  I am submitting this crash report. I downloaded sage from the
>> Ubuntu
>> >>> repo. Please let me know, how I can fix this. Thanks.
>> >>> Sincerely,
>> >>>
>> >>> Erik
>> >>>
>> >>
>> >> --
>> >> 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
>> >> 

Re: [sage-support] Sage Crash Report

[Clemens]

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.

Thanks,
Clemens

On Saturday, May 11, 2019 at 8:42:51 AM UTC+2, Dima Pasechnik wrote:
>
> 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 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 with the following error: 
> > 
> > ImportError: 
> dlopen(/Users/clemens/SageMath/local/lib/python2.7/site-packages/sage/symbolic/ring.so,
>  
> 2): Symbol not found: 
> __ZNSt3__16vectorIN5GiNaC2exENS_9allocatorIS2_EEE11__vallocateEm 
> >  Referenced from: 
> /Users/clemens/SageMath/local/lib/python2.7/site-packages/sage/symbolic/ring.so
>  
>
> >  Expected in: flat namespace 
> > in 
> /Users/clemens/SageMath/local/lib/python2.7/site-packages/sage/symbolic/ring.so
>  
>
> > 
> > See crash report attached to this mail for more details. 
> > 
> > Thanks and best regards, 
> > Clemens 
> > 
> > -- 
> > 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-s...@googlegroups.com . 
> > To post to this group, send email to sage-s...@googlegroups.com 
> . 
> > Visit this group at https://groups.google.com/group/sage-support. 
> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-support/EE213D24-09A8-42DB-AAE2-22B7FF8F1D63%40gmail.com.
>  
>
> > For more options, visit https://groups.google.com/d/optout. 
>

-- 
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 this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/c73ef10d-08cc-4ccd-81ab-5f367687c008%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-support] Sage Crash Report

[Dima Pasechnik]

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 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 with the following error:
>
> ImportError: 
> dlopen(/Users/clemens/SageMath/local/lib/python2.7/site-packages/sage/symbolic/ring.so,
>  2): Symbol not found: 
> __ZNSt3__16vectorIN5GiNaC2exENS_9allocatorIS2_EEE11__vallocateEm
>  Referenced from: 
> /Users/clemens/SageMath/local/lib/python2.7/site-packages/sage/symbolic/ring.so
>  Expected in: flat namespace
> in 
> /Users/clemens/SageMath/local/lib/python2.7/site-packages/sage/symbolic/ring.so
>
> See crash report attached to this mail for more details.
>
> Thanks and best regards,
> Clemens
>
> --
> 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 this group, send email to sage-support@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-support.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-support/EE213D24-09A8-42DB-AAE2-22B7FF8F1D63%40gmail.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
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 this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/CAAWYfq1GUsUQvK8oUW5xP8R0FoYsJEV%2B2qpCb%2B91NCE0tKsjFA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-support] Sage Crash Report

[Erik Wallace]

Here is the output:

$ apt list --installed | grep sagemath

sagemath-common/bionic,bionic,now 8.1-7ubuntu1 all [installed]

$ ls -l /usr/lib/python2.7/dist-packages/sage/structure/

total 808
-rw-r--r-- 1 root root   641 Dec  7  2017 all.py
-rw-r--r-- 1 root root  1114 Apr 15 21:51 all.pyc
-rw-r--r-- 1 root root   986 Dec  7  2017 category_object.pxd
-rw-r--r-- 1 root root   376 Dec  7  2017 coerce_actions.pxd
-rw-r--r-- 1 root root   851 Dec  7  2017 coerce_dict.pxd
-rw-r--r-- 1 root root   953 Dec  7  2017 coerce_exceptions.py
-rw-r--r-- 1 root root   868 Apr 15 21:51 coerce_exceptions.pyc
-rw-r--r-- 1 root root   463 Dec  7  2017 coerce_maps.pxd
-rw-r--r-- 1 root root  1086 Dec  7  2017 coerce.pxd
-rw-r--r-- 1 root root   154 Dec  7  2017 debug_options.pxd
-rw-r--r-- 1 root root 19675 Dec  7  2017 dynamic_class.py
-rw-r--r-- 1 root root 18719 Apr 15 21:51 dynamic_class.pyc
-rw-r--r-- 1 root root  7836 Dec  7  2017 element.pxd
-rw-r--r-- 1 root root   265 Dec  7  2017 element_wrapper.pxd
-rw-r--r-- 1 root root  3780 Dec  7  2017 factorization_integer.py
-rw-r--r-- 1 root root  4282 Apr 15 21:51 factorization_integer.pyc
-rw-r--r-- 1 root root 39922 Dec  7  2017 factorization.py
-rw-r--r-- 1 root root 41925 Apr 15 21:51 factorization.pyc
-rw-r--r-- 1 root root 15267 Dec  7  2017 formal_sum.py
-rw-r--r-- 1 root root 16707 Apr 15 21:51 formal_sum.pyc
-rw-r--r-- 1 root root  2035 Dec  7  2017 gens_py.py
-rw-r--r-- 1 root root  1795 Apr 15 21:51 gens_py.pyc
-rw-r--r-- 1 root root 66908 Dec  7  2017 global_options.py
-rw-r--r-- 1 root root 63304 Apr 15 21:51 global_options.pyc
-rw-r--r-- 1 root root  7908 Dec  7  2017 graphics_file.py
-rw-r--r-- 1 root root  9747 Apr 15 21:51 graphics_file.pyc
-rw-r--r-- 1 root root 26183 Dec  7  2017 indexed_generators.py
-rw-r--r-- 1 root root 24447 Apr 15 21:51 indexed_generators.pyc
-rw-r--r-- 1 root root 0 Dec  7  2017 __init__.py
-rw-r--r-- 1 root root   146 Apr 15 21:51 __init__.pyc
-rw-r--r-- 1 root root  2043 Dec  7  2017 list_clone.pxd
-rw-r--r-- 1 root root  6718 Dec  7  2017 list_clone_timings.py
-rw-r--r-- 1 root root  7534 Apr 15 21:51 list_clone_timings.pyc
-rw-r--r-- 1 root root   532 Dec  7  2017 mutability.pxd
-rw-r--r-- 1 root root   646 Dec  7  2017 nonexact.py
-rw-r--r-- 1 root root  1343 Apr 15 21:51 nonexact.pyc
-rw-r--r-- 1 root root   538 Dec  7  2017 parent_base.pxd
-rw-r--r-- 1 root root   743 Dec  7  2017 parent_gens.pxd
-rw-r--r-- 1 root root  1314 Dec  7  2017 parent_old.pxd
-rw-r--r-- 1 root root  4142 Dec  7  2017 parent.pxd
drwxr-xr-x 2 root root  4096 Apr 15 21:51 proof
-rw-r--r-- 1 root root  4892 Dec  7  2017 richcmp.pxd
-rw-r--r-- 1 root root32 Dec  7  2017 sage_object.pxd
-rw-r--r-- 1 root root 26596 Dec  7  2017 sequence.py
-rw-r--r-- 1 root root 27439 Apr 15 21:51 sequence.pyc
-rw-r--r-- 1 root root 17209 Dec  7  2017 set_factories_example.py
-rw-r--r-- 1 root root 20559 Apr 15 21:51 set_factories_example.pyc
-rw-r--r-- 1 root root 41168 Dec  7  2017 set_factories.py
-rw-r--r-- 1 root root 43362 Apr 15 21:51 set_factories.pyc
-rw-r--r-- 1 root root  1751 Dec  7  2017 test_factory.py
-rw-r--r-- 1 root root  1871 Apr 15 21:51 test_factory.pyc
-rw-r--r-- 1 root root 50516 Dec  7  2017 unique_representation.py
-rw-r--r-- 1 root root 51060 Apr 15 21:51 unique_representation.pyc

On Sun, Apr 28, 2019 at 4:46 PM Vincent Delecroix <20100.delecr...@gmail.com>
wrote:

> I do not see anything obvious in the crash report that explains the
> problem. For each thing below could you copy paste the full output
> of what appears in the console.
>
> 1. The list of sagemath packages installed
>
> $ apt list --installed | grep sagemath
>
> 2. Files in /usr/lib/python2.7/dist-packages/sage/structure via
>
> $ ls -l /usr/lib/python2.7/dist-packages/sage/structure/
>
> Le 28/04/2019 à 21:05, Erik Wallace a écrit :
> > Yes, I downloaded via apt. The supporting python packages were also
> > downloaded via apt.
> >
> > On Sat, Apr 27, 2019 at 5:08 PM Vincent Delecroix <
> 20100.delecr...@gmail.com>
> > wrote:
> >
> >> Hello,
> >>
> >> What did you downloaded exactly? You meant that you installed
> >> Sage from via the package manager (apt)?
> >>
> >> Best
> >> Vincent
> >>
> >> Le 23/04/2019 à 03:22, Erik Wallace a écrit :
> >>> Hello,
> >>>  I am submitting this crash report. I downloaded sage from the
> Ubuntu
> >>> repo. Please let me know, how I can fix this. Thanks.
> >>> Sincerely,
> >>>
> >>> Erik
> >>>
> >>
> >> --
> >> 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 this group, send email to sage-support@googlegroups.com.
> >> Visit this group at https://groups.google.com/group/sage-support.
> >> For more options, visit https://groups.google.com/d/optout.
> >>
> >
>
> --
> You received this message because you are subscribed to 

Re: [sage-support] Sage Crash Report

[Vincent Delecroix]

I do not see anything obvious in the crash report that explains the
problem. For each thing below could you copy paste the full output
of what appears in the console.

1. The list of sagemath packages installed

   $ apt list --installed | grep sagemath

2. Files in /usr/lib/python2.7/dist-packages/sage/structure via

   $ ls -l /usr/lib/python2.7/dist-packages/sage/structure/

Le 28/04/2019 à 21:05, Erik Wallace a écrit :

Yes, I downloaded via apt. The supporting python packages were also
downloaded via apt.

On Sat, Apr 27, 2019 at 5:08 PM Vincent Delecroix <20100.delecr...@gmail.com>
wrote:


Hello,

What did you downloaded exactly? You meant that you installed
Sage from via the package manager (apt)?

Best
Vincent

Le 23/04/2019 à 03:22, Erik Wallace a écrit :

Hello,
 I am submitting this crash report. I downloaded sage from the Ubuntu
repo. Please let me know, how I can fix this. Thanks.
Sincerely,

Erik



--
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 this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.





--
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 this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-support] Sage Crash Report

[Erik Wallace]

Yes, I downloaded via apt. The supporting python packages were also
downloaded via apt.

On Sat, Apr 27, 2019 at 5:08 PM Vincent Delecroix <20100.delecr...@gmail.com>
wrote:

> Hello,
>
> What did you downloaded exactly? You meant that you installed
> Sage from via the package manager (apt)?
>
> Best
> Vincent
>
> Le 23/04/2019 à 03:22, Erik Wallace a écrit :
> > Hello,
> > I am submitting this crash report. I downloaded sage from the Ubuntu
> > repo. Please let me know, how I can fix this. Thanks.
> > Sincerely,
> >
> > Erik
> >
>
> --
> 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 this group, send email to sage-support@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-support.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-support] Sage Crash Report

[Vincent Delecroix]

Hello,

What did you downloaded exactly? You meant that you installed
Sage from via the package manager (apt)?

Best
Vincent

Le 23/04/2019 à 03:22, Erik Wallace a écrit :

Hello,
I am submitting this crash report. I downloaded sage from the Ubuntu
repo. Please let me know, how I can fix this. Thanks.
Sincerely,

Erik



--
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 this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-support] Sage Crash Report

[Kolen Cheung]

Thanks. This is it. I’m glad we discussed about the channel priority (if 
you noticed my original attachment sage-environment.yml, conda-forge is 
last.)

I’m curious why this ABI incompatibility are allowed when satisfying the 
dependencies. I don’t know if the conda forge formula is written 
incorrectly or if this is a deficiency of conda. My original hope is to 
prioritize the intel channel so I can get libraries such as numpy and scipy 
from intel which is built using MKL instead of openblas. The bigger picture 
is to use sage together with the existing stack of libraries I already am 
using (where most are from intel then defaults).

For others’ reference, this is the minimal example to install sage in conda:

name: sage
channels:
  # this must be the first
  - conda-forge
  - intel
  - defaults
dependencies:
  # or just sage if you don't care versions
  - sage=8.3=py36_3

Save it as env-sage.yml, then run

conda env create -f ~/Dropbox/env-sage.yml
. activate 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 it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-support] Sage Crash Report

[Isuru Fernando]

Ah, that package was marked broken. conda-forge and defaults channels are
not ABI compatible, (it'll be in a month or so once the conda-forge rebuild
is done)
You should prioritize conda-forge over defaults and see what happens. Let
me know if it doesn't work and I'll send you the env file for a new
environment.

Isuru

On Sun, Nov 18, 2018 at 4:20 PM Kolen Cheung 
wrote:

> Interesting, it failed.
>
> sage ❯❯❯ conda env create -f env.yml
> Solving environment: failed
>
> ResolvePackageNotFound:
>   - sagenb==1.0.3=py_0
>
> Searching it on https://anaconda.org/conda-forge/sagenb/files shows it
> doesn’t exist. Has it been removed?
>
> Another question, I noticed that you prioritize conda-forge over defaults,
> why?
>
> Thanks.
> ​
>
> --
> 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 this group, send email to sage-support@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-support.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-support] Sage Crash Report

[Kolen Cheung]

Interesting, it failed.

sage ❯❯❯ conda env create -f env.yml
Solving environment: failed

ResolvePackageNotFound: 
  - sagenb==1.0.3=py_0

Searching it on https://anaconda.org/conda-forge/sagenb/files shows it 
doesn’t exist. Has it been removed?

Another question, I noticed that you prioritize conda-forge over defaults, 
why?

Thanks.
​

-- 
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 this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-support] Sage Crash Report

[Dima Pasechnik]

I guess the place to report such issues is here:
https://github.com/conda-forge/sage-feedstock
On Sun, Nov 18, 2018 at 10:58 AM Kolen Cheung  wrote:
>
> I actually tried a whole bunch of combinations. Build with and without the 
> intel channel, with python 2 or 3, on 3 different systems (macOS, ArchLinux, 
> and SUSE), all through conda. They all have some problems (that upon `sage` 
> there's an error, but this is the only one I reported so they can in 
> principle be all not working for a different reason.
>
> But may be a more general question, is the conda-forge formula really works? 
> If so are there a reproducible build that is tested to be working? If so, can 
> the environment be shared (like the environment.yml I generated above.)
>
> Among the supported installation methods, conda is preferred, because it is 
> reproducible and extensible and isolated. And conda is designed to handle 
> exactly the situation like Sage, that has a lot of non-python dependencies, 
> and conda has a lot of compiler stacks as well.
>
> Who's maintaining the conda-forge formula? May be they can take a look at 
> this?
>
> Regards,
> Kolen
> On Nov 18, 2018, 1:56 AM -0800, Dima Pasechnik , wrote:
>
> Oh, wait, these are all Python3 libraries, correct? This looks fishy
> to me. As well,
> Sage's libgd does not link ICU libraries (all these libicu*),
> fontconfig and webp, all these must be conda-forge
> modifications.
> So that's not something we could realistically fix without conda people.
>
> The usual suggestion - build Sage from source...
>
> On Sun, Nov 18, 2018 at 1:41 AM Kolen Cheung  
> wrote:
>
>
> sage ~ ❯❯❯ ls -alh 
> /home/sage/.conda/envs/sage/lib/python3.6/site-packages/sage/matrix/../../../../libgd.so.3
> lrwxrwxrwx 1 sage sage 14 Nov 17 17:34 
> /home/sage/.conda/envs/sage/lib/python3.6/site-packages/sage/matrix/../../../../libgd.so.3
>  -> libgd.so.3.0.5
> sage ~ ❯❯❯ ldd 
> /home/sage/.conda/envs/sage/lib/python3.6/site-packages/sage/matrix/../../../../libgd.so.3
> linux-vdso.so.1 (0x7ffd5f589000)
> libm.so.6 => /usr/lib/libm.so.6 (0x7f0a078fe000)
> libpng16.so.16 => 
> /home/sage/.conda/envs/sage/lib/python3.6/site-packages/sage/matrix/../../../.././libpng16.so.16
>  (0x7f0a076c3000)
> libz.so.1 => 
> /home/sage/.conda/envs/sage/lib/python3.6/site-packages/sage/matrix/../../../.././libz.so.1
>  (0x7f0a074a8000)
> libfontconfig.so.1 => 
> /home/sage/.conda/envs/sage/lib/python3.6/site-packages/sage/matrix/../../../.././libfontconfig.so.1
>  (0x7f0a07263000)
> libfreetype.so.6 => 
> /home/sage/.conda/envs/sage/lib/python3.6/site-packages/sage/matrix/../../../.././libfreetype.so.6
>  (0x7f0a06f87000)
> libjpeg.so.9 => 
> /home/sage/.conda/envs/sage/lib/python3.6/site-packages/sage/matrix/../../../.././libjpeg.so.9
>  (0x7f0a06d49000)
> libtiff.so.5 => 
> /home/sage/.conda/envs/sage/lib/python3.6/site-packages/sage/matrix/../../../.././libtiff.so.5
>  (0x7f0a06acf000)
> libwebp.so.6 => 
> /home/sage/.conda/envs/sage/lib/python3.6/site-packages/sage/matrix/../../../.././libwebp.so.6
>  (0x7f0a06831000)
> libpthread.so.0 => /usr/lib/libpthread.so.0 (0x7f0a0681)
> libc.so.6 => /usr/lib/libc.so.6 (0x7f0a0664c000)
> /usr/lib64/ld-linux-x86-64.so.2 (0x7f0a07d04000)
> libxml2.so.2 => 
> /home/sage/.conda/envs/sage/lib/python3.6/site-packages/sage/matrix/../../../../././libxml2.so.2
>  (0x7f0a062e5000)
> libdl.so.2 => /usr/lib/libdl.so.2 (0x7f0a062de000)
> libicui18n.so.58 => 
> /home/sage/.conda/envs/sage/lib/python3.6/site-packages/sage/matrix/../../../../././libicui18n.so.58
>  (0x7f0a05e69000)
> libicuuc.so.58 => 
> /home/sage/.conda/envs/sage/lib/python3.6/site-packages/sage/matrix/../../../../././libicuuc.so.58
>  (0x7f0a05abb000)
> libicudata.so.58 => 
> /home/sage/.conda/envs/sage/lib/python3.6/site-packages/sage/matrix/../../../../././libicudata.so.58
>  (0x7f0a03fbb000)
> liblzma.so.5 => 
> /home/sage/.conda/envs/sage/lib/python3.6/site-packages/sage/matrix/../../../../././liblzma.so.5
>  (0x7f0a03d8d000)
> librt.so.1 => /usr/lib/librt.so.1 (0x7f0a03d83000)
> libstdc++.so.6 => 
> /home/sage/.conda/envs/sage/lib/python3.6/site-packages/sage/matrix/../../../.././././libstdc++.so.6
>  (0x7f0a03c4)
> libgcc_s.so.1 => 
> /home/sage/.conda/envs/sage/lib/python3.6/site-packages/sage/matrix/../../../.././././libgcc_s.so.1
>  (0x7f0a03c2b000)
>
> --
> 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 this group, send email to sage-support@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-support.
> For more options, visit https://groups.google.com/d/optout.
>
>
> --
> You received this message because you are subscribed to the Google Groups 
> "sage-support" group.
> To unsubscribe from this group and 

Re: [sage-support] Sage Crash Report

[Dima Pasechnik]

Oh, wait, these are all Python3 libraries, correct? This looks fishy
to me. As well,
Sage's libgd does not link ICU libraries (all these libicu*),
fontconfig and webp, all these must be conda-forge
modifications.
So that's not something we could realistically fix  without conda people.

The usual suggestion - build Sage from source...

On Sun, Nov 18, 2018 at 1:41 AM Kolen Cheung  wrote:
>
> sage ~ ❯❯❯ ls -alh 
> /home/sage/.conda/envs/sage/lib/python3.6/site-packages/sage/matrix/../../../../libgd.so.3
> lrwxrwxrwx 1 sage sage 14 Nov 17 17:34 
> /home/sage/.conda/envs/sage/lib/python3.6/site-packages/sage/matrix/../../../../libgd.so.3
>  -> libgd.so.3.0.5
> sage ~ ❯❯❯ ldd 
> /home/sage/.conda/envs/sage/lib/python3.6/site-packages/sage/matrix/../../../../libgd.so.3
> linux-vdso.so.1 (0x7ffd5f589000)
> libm.so.6 => /usr/lib/libm.so.6 (0x7f0a078fe000)
> libpng16.so.16 => 
> /home/sage/.conda/envs/sage/lib/python3.6/site-packages/sage/matrix/../../../.././libpng16.so.16
>  (0x7f0a076c3000)
> libz.so.1 => 
> /home/sage/.conda/envs/sage/lib/python3.6/site-packages/sage/matrix/../../../.././libz.so.1
>  (0x7f0a074a8000)
> libfontconfig.so.1 => 
> /home/sage/.conda/envs/sage/lib/python3.6/site-packages/sage/matrix/../../../.././libfontconfig.so.1
>  (0x7f0a07263000)
> libfreetype.so.6 => 
> /home/sage/.conda/envs/sage/lib/python3.6/site-packages/sage/matrix/../../../.././libfreetype.so.6
>  (0x7f0a06f87000)
> libjpeg.so.9 => 
> /home/sage/.conda/envs/sage/lib/python3.6/site-packages/sage/matrix/../../../.././libjpeg.so.9
>  (0x7f0a06d49000)
> libtiff.so.5 => 
> /home/sage/.conda/envs/sage/lib/python3.6/site-packages/sage/matrix/../../../.././libtiff.so.5
>  (0x7f0a06acf000)
> libwebp.so.6 => 
> /home/sage/.conda/envs/sage/lib/python3.6/site-packages/sage/matrix/../../../.././libwebp.so.6
>  (0x7f0a06831000)
> libpthread.so.0 => /usr/lib/libpthread.so.0 (0x7f0a0681)
> libc.so.6 => /usr/lib/libc.so.6 (0x7f0a0664c000)
> /usr/lib64/ld-linux-x86-64.so.2 (0x7f0a07d04000)
> libxml2.so.2 => 
> /home/sage/.conda/envs/sage/lib/python3.6/site-packages/sage/matrix/../../../../././libxml2.so.2
>  (0x7f0a062e5000)
> libdl.so.2 => /usr/lib/libdl.so.2 (0x7f0a062de000)
> libicui18n.so.58 => 
> /home/sage/.conda/envs/sage/lib/python3.6/site-packages/sage/matrix/../../../../././libicui18n.so.58
>  (0x7f0a05e69000)
> libicuuc.so.58 => 
> /home/sage/.conda/envs/sage/lib/python3.6/site-packages/sage/matrix/../../../../././libicuuc.so.58
>  (0x7f0a05abb000)
> libicudata.so.58 => 
> /home/sage/.conda/envs/sage/lib/python3.6/site-packages/sage/matrix/../../../../././libicudata.so.58
>  (0x7f0a03fbb000)
> liblzma.so.5 => 
> /home/sage/.conda/envs/sage/lib/python3.6/site-packages/sage/matrix/../../../../././liblzma.so.5
>  (0x7f0a03d8d000)
> librt.so.1 => /usr/lib/librt.so.1 (0x7f0a03d83000)
> libstdc++.so.6 => 
> /home/sage/.conda/envs/sage/lib/python3.6/site-packages/sage/matrix/../../../.././././libstdc++.so.6
>  (0x7f0a03c4)
> libgcc_s.so.1 => 
> /home/sage/.conda/envs/sage/lib/python3.6/site-packages/sage/matrix/../../../.././././libgcc_s.so.1
>  (0x7f0a03c2b000)
>
> --
> 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 this group, send email to sage-support@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-support.
> For more options, visit https://groups.google.com/d/optout.

-- 
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 this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-support] Sage Crash Report

[Kolen Cheung]

sage ~ ❯❯❯ ls -alh 
/home/sage/.conda/envs/sage/lib/python3.6/site-packages/sage/matrix/../../../../libgd.so.3
lrwxrwxrwx 1 sage sage 14 Nov 17 17:34 
/home/sage/.conda/envs/sage/lib/python3.6/site-packages/sage/matrix/../../../../libgd.so.3
 -> libgd.so.3.0.5
sage ~ ❯❯❯ ldd 
/home/sage/.conda/envs/sage/lib/python3.6/site-packages/sage/matrix/../../../../libgd.so.3
linux-vdso.so.1 (0x7ffd5f589000)
libm.so.6 => /usr/lib/libm.so.6 (0x7f0a078fe000)
libpng16.so.16 => 
/home/sage/.conda/envs/sage/lib/python3.6/site-packages/sage/matrix/../../../.././libpng16.so.16
 (0x7f0a076c3000)
libz.so.1 => 
/home/sage/.conda/envs/sage/lib/python3.6/site-packages/sage/matrix/../../../.././libz.so.1
 (0x7f0a074a8000)
libfontconfig.so.1 => 
/home/sage/.conda/envs/sage/lib/python3.6/site-packages/sage/matrix/../../../.././libfontconfig.so.1
 (0x7f0a07263000)
libfreetype.so.6 => 
/home/sage/.conda/envs/sage/lib/python3.6/site-packages/sage/matrix/../../../.././libfreetype.so.6
 (0x7f0a06f87000)
libjpeg.so.9 => 
/home/sage/.conda/envs/sage/lib/python3.6/site-packages/sage/matrix/../../../.././libjpeg.so.9
 (0x7f0a06d49000)
libtiff.so.5 => 
/home/sage/.conda/envs/sage/lib/python3.6/site-packages/sage/matrix/../../../.././libtiff.so.5
 (0x7f0a06acf000)
libwebp.so.6 => 
/home/sage/.conda/envs/sage/lib/python3.6/site-packages/sage/matrix/../../../.././libwebp.so.6
 (0x7f0a06831000)
libpthread.so.0 => /usr/lib/libpthread.so.0 (0x7f0a0681)
libc.so.6 => /usr/lib/libc.so.6 (0x7f0a0664c000)
/usr/lib64/ld-linux-x86-64.so.2 (0x7f0a07d04000)
libxml2.so.2 => 
/home/sage/.conda/envs/sage/lib/python3.6/site-packages/sage/matrix/../../../../././libxml2.so.2
 (0x7f0a062e5000)
libdl.so.2 => /usr/lib/libdl.so.2 (0x7f0a062de000)
libicui18n.so.58 => 
/home/sage/.conda/envs/sage/lib/python3.6/site-packages/sage/matrix/../../../../././libicui18n.so.58
 (0x7f0a05e69000)
libicuuc.so.58 => 
/home/sage/.conda/envs/sage/lib/python3.6/site-packages/sage/matrix/../../../../././libicuuc.so.58
 (0x7f0a05abb000)
libicudata.so.58 => 
/home/sage/.conda/envs/sage/lib/python3.6/site-packages/sage/matrix/../../../../././libicudata.so.58
 (0x7f0a03fbb000)
liblzma.so.5 => 
/home/sage/.conda/envs/sage/lib/python3.6/site-packages/sage/matrix/../../../../././liblzma.so.5
 (0x7f0a03d8d000)
librt.so.1 => /usr/lib/librt.so.1 (0x7f0a03d83000)
libstdc++.so.6 => 
/home/sage/.conda/envs/sage/lib/python3.6/site-packages/sage/matrix/../../../.././././libstdc++.so.6
 (0x7f0a03c4)
libgcc_s.so.1 => 
/home/sage/.conda/envs/sage/lib/python3.6/site-packages/sage/matrix/../../../.././././libgcc_s.so.1
 (0x7f0a03c2b000)

​

-- 
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 this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-support] Sage Crash Report

[Dima Pasechnik]

On Sun, Nov 18, 2018 at 12:11 AM Kolen Cheung  wrote:
>
> I tried. the problem is libiconv is already there. conda install that shows 
> it's fulfilled.

Probably a linking problem...
What's the output of

ldd 
/home/sage/.conda/envs/sage/lib/python3.6/site-packages/sage/matrix/../../../../libgd.so.3



>
> you can try to conda crete from the yml file to replicate the exact conda 
> environment to reproduce this problem.
>
> Regards,
> Kolen
> On Nov 17, 2018, 3:30 PM -0800, Dima Pasechnik , wrote:
>
> It looks like Sage installed via conda-forge, and
>
>
> ImportError: 
> /home/sage/.conda/envs/sage/lib/python3.6/site-packages/sage/matrix/../../../../libgd.so.3:
> undefined symbol: libiconv
>
> seems to indicate that libiconv is missing in the environment. I don't
> know much about conda, but it seems that you need to run something
> like
>
> conda install -c conda-forge libiconv
>
> and try running sage again...
>
>
>
> On Sat, Nov 17, 2018 at 11:22 PM Kolen Cheung  
> wrote:
>
>
>
> --
> 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 this group, send email to sage-support@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-support.
> For more options, visit https://groups.google.com/d/optout.
>
>
> --
> 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 this group, send email to sage-support@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-support.
> For more options, visit https://groups.google.com/d/optout.
>
> --
> 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 this group, send email to sage-support@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-support.
> For more options, visit https://groups.google.com/d/optout.

-- 
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 this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-support] Sage Crash Report

[Kolen Cheung]

I tried. the problem is libiconv is already there. conda install that shows 
it's fulfilled.

you can try to conda crete from the yml file to replicate the exact conda 
environment to reproduce this problem.

Regards,
Kolen
On Nov 17, 2018, 3:30 PM -0800, Dima Pasechnik , wrote:
> It looks like Sage installed via conda-forge, and
>
>
> ImportError: 
> /home/sage/.conda/envs/sage/lib/python3.6/site-packages/sage/matrix/../../../../libgd.so.3:
> undefined symbol: libiconv
>
> seems to indicate that libiconv is missing in the environment. I don't
> know much about conda, but it seems that you need to run something
> like
>
> conda install -c conda-forge libiconv
>
> and try running sage again...
>
>
>
> On Sat, Nov 17, 2018 at 11:22 PM Kolen Cheung  
> wrote:
> >
> >
> > --
> > 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 this group, send email to sage-support@googlegroups.com.
> > Visit this group at https://groups.google.com/group/sage-support.
> > For more options, visit https://groups.google.com/d/optout.
>
> --
> 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 this group, send email to sage-support@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-support.
> For more options, visit https://groups.google.com/d/optout.

-- 
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 this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-support] Sage Crash Report

[Dima Pasechnik]

It looks like Sage installed via conda-forge, and


ImportError: 
/home/sage/.conda/envs/sage/lib/python3.6/site-packages/sage/matrix/../../../../libgd.so.3:
undefined symbol: libiconv

seems to indicate that libiconv is missing in the environment. I don't
know much about conda, but it seems that you need to run something
like

conda install -c conda-forge libiconv

and try running sage again...



On Sat, Nov 17, 2018 at 11:22 PM Kolen Cheung  wrote:
>
>
> --
> 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 this group, send email to sage-support@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-support.
> For more options, visit https://groups.google.com/d/optout.

-- 
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 this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-support] Sage Crash Report

[Jeroen Demeyer]

On 2018-03-10 12:29, Alasdair McAndrew wrote:

As created just now.  Enjoy!


How did you get that SageMath installation on your computer? Was it a 
binary install, a source install, an upgrade from an earlier version?


In any case, I would suggest to simply reinstall 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 it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-support] Sage Crash Report

[Vegard Lima]

Hi,

On Thu, Oct 26, 2017 at 10:27 PM, Dima Pasechnik  wrote:
> On Thursday, October 26, 2017 at 4:55:19 PM UTC+1, Renan Birck Pinheiro
> wrote:
>> gfortran is installed but sage still doesn't work. I do have
>> libgfortran.so.4 rather than libgfortran.so.3 that sage wants.
>>
>
> then your only ways out are either to build Sage from source, or to somehow
> install  libgfortran.so.3

there is also the option of using sage 7.6 that comes with fedora 26:

Just do:
$ dnf install sagemath python2-psutil Singular-devel

and it should work.


Cheers,
-- 
Vegard

-- 
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 this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-support] Sage Crash Report

[Dima Pasechnik]

Hi,

On Thursday, October 26, 2017 at 4:55:19 PM UTC+1, Renan Birck Pinheiro 
wrote:
>
> Hello,
>
> gfortran is installed but sage still doesn't work. I do 
> have libgfortran.so.4 rather than libgfortran.so.3 that sage wants.
>
>
then your only ways out are either to build Sage from source, or to somehow 
install  libgfortran.so.3


Thanks,
>
> 2017-10-25 11:12 GMT-02:00 Jeroen Demeyer  >:
>
>> This is a known problem which will be fixed for Sage 8.1
>>
>> For now, you have to install gfortran from your Fedora distribution.
>>
>> -- 
>> 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...@googlegroups.com .
>> To post to this group, send email to sage-s...@googlegroups.com 
>> .
>> Visit this group at https://groups.google.com/group/sage-support.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> Renan Birck Pinheiro - Blog  - LinkedIn 
>  - GitHub 
> 
> +55 47 997112201 +55 48 991618277 - skype: birck.renan
>  
>
>

-- 
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 this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-support] Sage Crash Report

[Renan Birck Pinheiro]

Hello,

gfortran is installed but sage still doesn't work. I do
have libgfortran.so.4 rather than libgfortran.so.3 that sage wants.

Thanks,

2017-10-25 11:12 GMT-02:00 Jeroen Demeyer :

> This is a known problem which will be fixed for Sage 8.1
>
> For now, you have to install gfortran from your Fedora distribution.
>
> --
> 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 this group, send email to sage-support@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-support.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Renan Birck Pinheiro - Blog  - LinkedIn
 - GitHub

+55 47 997112201 +55 48 991618277 - skype: birck.renan

-- 
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 this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-support] Sage Crash Report

[Jeroen Demeyer]

On 2017-10-26 10:50, Dima Pasechnik wrote:

from your log:

ImportError: libgfortran.so.3: cannot open shared object file: No such file or 
directory

installing libfortran3  will fix the problem.



Or waiting for Sage 8.1 since that problem has been fixed in the mean time.

--
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 this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-support] Sage Crash Report

[Jeroen Demeyer]

This is a known problem which will be fixed for Sage 8.1

For now, you have to install gfortran from your Fedora distribution.

--
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 this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-support] Sage Crash Report

[Jeroen Demeyer]

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 when 
you got this error.


Too many people think that a "Crash Report" is sufficient information.

--
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 this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-support] Sage Crash Report

[Jan Groenewald]

Hi Alvaro,

On 22 October 2017 at 19:42, Alvaro Ezequiel 
wrote:

>
>
> A crash report was automatically generated with the following information:
>   - A verbatim copy of the crash traceback.
>   - A copy of your input history during this session.
>   - Data on your current Sage configuration.
>
> It was left in the file named:
> '/home/alvaro/.sage/ipython-5.0.0/Sage_crash_report.txt'
> If you can email this file to the developers, the information in it will
> help
> them in understanding and correcting the problem.
>

If you can email this file to the developers, the information in it will
help
them in understanding and correcting the problem.

Regards,
Jan


>


-- 
  .~.
  /V\ Jan Groenewald
 /( )\www.aims.ac.za
 ^^-^^

-- 
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 this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

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

[yan liang]

The problem has sloved correctly. Thank you very much.

Jan Groenewald於 2017年9月11日星期一 UTC+8下午5時44分45秒寫道：
>
> Hi
>
> On 11 September 2017 at 11:18, yan liang  > wrote:
>
>> I download the file and run ./sage then it crash.
>>
>> I am using Ubuntu 16.04 and download the correct file.
>>
>> Hope you may help me solve the problem Thanks.
>>
>
> From 
>
> ImportError: libgfortran.so.3: cannot open shared object file: No such file 
> or directory
>
> It looks like you need to install gfortran
>
> Regards,
>
> Jan
>
>
>
> -- 
>   .~. 
>   /V\ Jan Groenewald
>  /( )\www.aims.ac.za
>  ^^-^^ 
>

-- 
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 this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

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

[Jan Groenewald]

Hi

On 11 September 2017 at 11:18, yan liang  wrote:

> I download the file and run ./sage then it crash.
>
> I am using Ubuntu 16.04 and download the correct file.
>
> Hope you may help me solve the problem Thanks.
>

From

ImportError: libgfortran.so.3: cannot open shared object file: No such
file or directory

It looks like you need to install gfortran

Regards,

Jan



-- 
  .~.
  /V\ Jan Groenewald
 /( )\www.aims.ac.za
 ^^-^^

-- 
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 this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-support] Sage Crash Report

[Harald Schilly]

On Monday, March 27, 2017 at 5:08:39 AM UTC+2, slelievre wrote:
>
> Volker, William,
>
> Any chance a redirect from the now-404
>
> https://github.com/sagemath/docker
>
> to the current
>
> https://github.com/sagemath/docker-images
>
> might be set up?
>

No, but the existing "docker-images" could be renamed to just "docker". 
Then it would redirect and move the repo's extras, see
https://help.github.com/articles/renaming-a-repository/

-- harald

-- 
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 this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-support] Sage Crash Report

[slelievre]

Volker, William,

Any chance a redirect from the now-404

https://github.com/sagemath/docker

to the current

https://github.com/sagemath/docker-images

might be set up?

Samuel

Fri 2017-02-17 19:33:01 UTC+1, Volker Braun:

> Deleted. You as sagemath org admin should have been able
> to do the same, I think... 
>
> On Fri, Feb 17, 2017 at 7:01 PM, William Stein wrote:
>
>> On Thu, Feb 16, 2017 at 10:15 PM, asutosh hota wrote:
>>
>>> I am currently 6.7 docker version
>>
>> That's ridiculous -- Sage is currently at version 7.5.
>>
>> Volker, please delete or update this ancient repo you posted
>> two years ago:  https://github.com/sagemath/docker
>>
>> It's what people find when they search sage/docker, and it's
>> ancient. Or at least add Erik Bray and I...
>>
>> Erik's Docker images for sage are here and are somewhat
>> more up to date:
>>
>>   https://github.com/sagemath/docker-images
>>
>> My Docker images for SageMathCloud really do include the
>> latest Sage (and latex, etc.) and are always very up to date:
>>
>>https://github.com/sagemathinc/smc/tree/master/src/dev/docker

-- 
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 this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.