Re: [sage-support] Sage Crash report

2020-04-08 Thread 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] Apparently Sage lost Python

2020-04-08 Thread slelievre
Have you tried running


THING="~/Applications/SageMath/"

xattr -rd com.apple.quarantine $THING

-- 
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/aba1daec-0585-4518-bb37-07b99f83f966%40googlegroups.com.


Re: [sage-support] Sage Crash report

2020-04-08 Thread 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

2020-04-08 Thread 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] Apparently Sage lost Python

2020-04-08 Thread Anita Rojas
This worked! Thanks
Now I have troubles calling gap. I used to do

sage:  libgap.eval('LoadPackage("kbmag")')

but now I got


fail


On Wed, Apr 8, 2020 at 1:25 PM slelievre  wrote:

> Have you tried running
>
>
> THING="~/Applications/SageMath/"
>
> xattr -rd com.apple.quarantine $THING
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "sage-support" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/sage-support/NletjrinNhM/unsubscribe.
> To unsubscribe from this group and all its topics, 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/aba1daec-0585-4518-bb37-07b99f83f966%40googlegroups.com
> 
> .
>


-- 
Anita M. Rojas
Departamento de Matemáticas
Facultad de Ciencias
Universidad de Chile

https://sites.google.com/a/u.uchile.cl/mat-ciencias-prof-anita-rojas/

-- 
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/CAFV-Ve3adEbg%3D0w6voWif%2ByAB7qjfRh5w%3DLy_%2Bv%2B46-E90N6aw%40mail.gmail.com.


Re: [sage-support] Sage Crash report

2020-04-08 Thread 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

2020-04-08 Thread 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() 
>>> >> > 
>>> >> >  

[sage-support] Building on Catalina

2020-04-08 Thread David Einstein
I am trying to build on OSX Catalina, and everything seems to go well until 
it builds sagelib, and I get a libpng not found.

Everything built nicely a few weeks ago.  I am tempted to blame the upgrade 
to catalina, but I also upgraded hombrew and XCode.

Any ideas?

Here is the final output from the terminal.

if [ -z "$SAGE_INSTALL_FETCH_ONLY" ]; then \

cd /Users/davideinstein/projects/sage/src && source bin/sage-env && source 
/Users/davideinstein/projects/sage/build/bin/sage-build-env-config && \

sage-logger -p 'time make sage' 
'/Users/davideinstein/projects/sage/logs/pkgs/sagelib-9.1.beta9.log'; \

fi

[sagelib-9.1.beta9] cd . && export\

[sagelib-9.1.beta9] SAGE_ROOT=/doesnotexist 
  \

[sagelib-9.1.beta9] SAGE_SRC=/doesnotexist  
  \

[sagelib-9.1.beta9] SAGE_SRC_ROOT=/doesnotexist 
  \

[sagelib-9.1.beta9] SAGE_DOC_SRC=/doesnotexist  
  \

[sagelib-9.1.beta9] SAGE_BUILD_DIR=/doesnotexist
  \

[sagelib-9.1.beta9] 
SAGE_PKGS=/Users/davideinstein/projects/sage/build/pkgs\

[sagelib-9.1.beta9] && sage-python -u setup.py --no-user-cfg build install

[sagelib-9.1.beta9] /Users/davideinstein/projects/sage/src/bin/sage-env: 
line 130: cd: /doesnotexist: No such file or directory

[sagelib-9.1.beta9] Warning: overwriting SAGE_ROOT environment variable:

[sagelib-9.1.beta9] Old SAGE_ROOT=/doesnotexist

[sagelib-9.1.beta9] New SAGE_ROOT=

[sagelib-9.1.beta9] 


[sagelib-9.1.beta9] Traceback (most recent call last):

[sagelib-9.1.beta9]   File "setup.py", line 72, in 

[sagelib-9.1.beta9] from module_list import ext_modules, library_order

[sagelib-9.1.beta9]   File 
"/Users/davideinstein/projects/sage/src/module_list.py", line 36, in 


[sagelib-9.1.beta9] png_pc = pkgconfig.parse('libpng')

[sagelib-9.1.beta9]   File 
"/Users/davideinstein/projects/sage/local/lib/python3.7/site-packages/pkgconfig/pkgconfig.py",
 
line 248, in parse

[sagelib-9.1.beta9] _raise_if_not_exists(package)

[sagelib-9.1.beta9]   File 
"/Users/davideinstein/projects/sage/local/lib/python3.7/site-packages/pkgconfig/pkgconfig.py",
 
line 103, in _raise_if_not_exists

[sagelib-9.1.beta9] raise PackageNotFoundError(package)

[sagelib-9.1.beta9] pkgconfig.pkgconfig.PackageNotFoundError: libpng not 
found

[sagelib-9.1.beta9] 


[sagelib-9.1.beta9] Error building the Sage library

[sagelib-9.1.beta9] 


[sagelib-9.1.beta9] Please email sage-devel 
(http://groups.google.com/group/sage-devel)

[sagelib-9.1.beta9] explaining the problem and including the relevant part 
of the log file

[sagelib-9.1.beta9]   
/Users/davideinstein/projects/sage/logs/pkgs/sagelib-9.1.beta9.log

[sagelib-9.1.beta9] Describe your computer, operating system, etc.

[sagelib-9.1.beta9] 


[sagelib-9.1.beta9] make[4]: *** [sage] Error 1

[sagelib-9.1.beta9] 

[sagelib-9.1.beta9] real 0m0.612s

[sagelib-9.1.beta9] user 0m0.193s

[sagelib-9.1.beta9] sys 0m0.133s

make[3]: *** [sagelib] Error 2

make[2]: *** [all-start] Error 2


real 212m28.552s

user 151m29.195s

sys 26m1.334s

***

Error building Sage.


The following package(s) may have failed to build (not necessarily

during this run of 'make all-start'):


* package: sagelib-9.1.beta9

  last build time: Apr 8 21:23

  log file:
/Users/davideinstein/projects/sage/logs/pkgs/sagelib-9.1.beta9.log


It is safe to delete any log files and build directories, but they

contain information that is helpful for debugging build problems.

WARNING: If you now run 'make' again, the build directory of the

same version of the package will, by default, be deleted. Set the

environment variable SAGE_KEEP_BUILT_SPKGS=yes to prevent this.


make[1]: *** [all-start] Error 1

make: *** [all] Error 2

-- 
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/d8e46d82-f201-4cbd-94ad-5bceccdc678c%40googlegroups.com.


Re: [sage-support] Sage Crash report

2020-04-08 Thread 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] Apparently Sage lost Python

2020-04-08 Thread Samuel Lelièvre
Forgot one step. Run this:

sage -i gap_packages
After that, the steps indicated earlier should 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/CAEcArF18yaZKbDR-W23%2BSn21mZUSf9uB8MWc6sm1c0Wr7EOcDA%40mail.gmail.com.


Re: [sage-support] Apparently Sage lost Python

2020-04-08 Thread slelievre
Wed 2020-04-08 19:02:33 UTC, Anita Rojas:
>
> Now I have trouble calling GAP. I used to do
>
> sage: libgap.eval('LoadPackage("kbmag")')
>
> but now I got 
>
> fail

The following says the `kbmag` GAP package cannot be loaded.

sage: libgap.eval('LoadPackage("kbmag")')
fail

It fails to load because it is not installed in Sage's GAP.

Thankfully, installing packages has become a pleasant task
thanks to Michael Torpey's `PackageManager` GAP package.

Load the `PackageManager` GAP package, whose job
is to help you install further packages:

sage: libgap.eval('LoadPackage("PackageManager")')
true

and let it install `kbmag` with this command:

sage: libgap.eval('InstallPackage("kbmag")')
true

Now loading `kbmag` works:

sage: libgap.eval('LoadPackage("kbmag")')
true

The `kbmag` package is now loaded, ready to
try and make rewriting systems confluent.

Further reading:

- kbmag GAP package
  Knuth-Bendix on Monoids and Automatic Groups
  by Derek Holt
  home: https://gap-packages.github.io/kbmag/
  repo: https://github.com/gap-packages/kbmag
  docs: https://gap-packages.github.io/kbmag/doc/chap0.html

- PackageManager GAP package --- GAP Package Manager
  Easily download and install GAP packages
  by Michael Torpey
  home: https://gap-packages.github.io/PackageManager/
  repo: https://github.com/gap-packages/PackageManager
  docs: https://gap-packages.github.io/PackageManager/doc/chap0.html

-- 
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/a8bb010a-00c7-4801-b656-355ff54d1aca%40googlegroups.com.


Re: [sage-support] Apparently Sage lost Python

2020-04-08 Thread Anita Rojas
Thanks a lot. But I also got:

sage: libgap.eval('LoadPackage("PackageManager")')

fail

 Should I add (or install) some gap package inside SageMath folder?

Sorry

On Wed, Apr 8, 2020 at 5:43 PM slelievre  wrote:

> Wed 2020-04-08 19:02:33 UTC, Anita Rojas:
> >
> > Now I have trouble calling GAP. I used to do
> >
> > sage: libgap.eval('LoadPackage("kbmag")')
> >
> > but now I got
> >
> > fail
>
> The following says the `kbmag` GAP package cannot be loaded.
>
> sage: libgap.eval('LoadPackage("kbmag")')
> fail
>
> It fails to load because it is not installed in Sage's GAP.
>
> Thankfully, installing packages has become a pleasant task
> thanks to Michael Torpey's `PackageManager` GAP package.
>
> Load the `PackageManager` GAP package, whose job
> is to help you install further packages:
>
> sage: libgap.eval('LoadPackage("PackageManager")')
> true
>
> and let it install `kbmag` with this command:
>
> sage: libgap.eval('InstallPackage("kbmag")')
> true
>
> Now loading `kbmag` works:
>
> sage: libgap.eval('LoadPackage("kbmag")')
> true
>
> The `kbmag` package is now loaded, ready to
> try and make rewriting systems confluent.
>
> Further reading:
>
> - kbmag GAP package
>   Knuth-Bendix on Monoids and Automatic Groups
>   by Derek Holt
>   home: https://gap-packages.github.io/kbmag/
>   repo: https://github.com/gap-packages/kbmag
>   docs: https://gap-packages.github.io/kbmag/doc/chap0.html
>
> - PackageManager GAP package --- GAP Package Manager
>   Easily download and install GAP packages
>   by Michael Torpey
>   home: https://gap-packages.github.io/PackageManager/
>   repo: https://github.com/gap-packages/PackageManager
>   docs: https://gap-packages.github.io/PackageManager/doc/chap0.html
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "sage-support" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/sage-support/NletjrinNhM/unsubscribe.
> To unsubscribe from this group and all its topics, 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/a8bb010a-00c7-4801-b656-355ff54d1aca%40googlegroups.com
> 
> .
>


-- 
Anita M. Rojas
Departamento de Matemáticas
Facultad de Ciencias
Universidad de Chile

https://sites.google.com/a/u.uchile.cl/mat-ciencias-prof-anita-rojas/

-- 
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/CAFV-Ve0PxK9idizLHNY-%3Dc8rD-12rKJaadH7eycOFYkQ%2BrdmiQ%40mail.gmail.com.


Re: [sage-support] Building on Catalina

2020-04-08 Thread John H Palmieri
When I have had problems with libpng, it has helped to do "brew install 
pkg-config". If you happened to start building Sage and then upgraded 
Homebrew and/or Xcode in the middle of that, or if you've installed any new 
Homebrew packages,  you should probably start over with "make distclean" 
followed by "make".


On Wednesday, April 8, 2020 at 7:58:38 PM UTC-7, David Einstein wrote:
>
> Here is the config.log.
>
> On Wednesday, April 8, 2020 at 10:32:51 PM UTC-4, Dima Pasechnik wrote:
>>
>> Hi David, 
>> It might help if you posted the top-level config.log, thanks. 
>>
>> Dima 
>>
>> On Thu, Apr 9, 2020 at 9:58 AM David Einstein  wrote: 
>> > 
>> > I am trying to build on OSX Catalina, and everything seems to go well 
>> until it builds sagelib, and I get a libpng not found. 
>> > 
>> > Everything built nicely a few weeks ago.  I am tempted to blame the 
>> upgrade to catalina, but I also upgraded hombrew and XCode. 
>> > 
>> > Any ideas? 
>> > 
>> > Here is the final output from the terminal. 
>> > 
>> > if [ -z "$SAGE_INSTALL_FETCH_ONLY" ]; then \ 
>> > 
>> > cd /Users/davideinstein/projects/sage/src && source bin/sage-env && 
>> source /Users/davideinstein/projects/sage/build/bin/sage-build-env-config 
>> && \ 
>> > 
>> > sage-logger -p 'time make sage' 
>> '/Users/davideinstein/projects/sage/logs/pkgs/sagelib-9.1.beta9.log'; \ 
>> > 
>> > fi 
>> > 
>> > [sagelib-9.1.beta9] cd . && export\ 
>> > 
>> > [sagelib-9.1.beta9] SAGE_ROOT=/doesnotexist 
>>   \ 
>> > 
>> > [sagelib-9.1.beta9] SAGE_SRC=/doesnotexist 
>>\ 
>> > 
>> > [sagelib-9.1.beta9] SAGE_SRC_ROOT=/doesnotexist 
>>   \ 
>> > 
>> > [sagelib-9.1.beta9] SAGE_DOC_SRC=/doesnotexist 
>>\ 
>> > 
>> > [sagelib-9.1.beta9] SAGE_BUILD_DIR=/doesnotexist   
>>\ 
>> > 
>> > [sagelib-9.1.beta9] 
>> SAGE_PKGS=/Users/davideinstein/projects/sage/build/pkgs\ 
>> > 
>> > [sagelib-9.1.beta9] && sage-python -u setup.py --no-user-cfg build 
>> install 
>> > 
>> > [sagelib-9.1.beta9] 
>> /Users/davideinstein/projects/sage/src/bin/sage-env: line 130: cd: 
>> /doesnotexist: No such file or directory 
>> > 
>> > [sagelib-9.1.beta9] Warning: overwriting SAGE_ROOT environment 
>> variable: 
>> > 
>> > [sagelib-9.1.beta9] Old SAGE_ROOT=/doesnotexist 
>> > 
>> > [sagelib-9.1.beta9] New SAGE_ROOT= 
>> > 
>> > [sagelib-9.1.beta9] 
>>  
>> > 
>> > [sagelib-9.1.beta9] Traceback (most recent call last): 
>> > 
>> > [sagelib-9.1.beta9]   File "setup.py", line 72, in  
>> > 
>> > [sagelib-9.1.beta9] from module_list import ext_modules, 
>> library_order 
>> > 
>> > [sagelib-9.1.beta9]   File 
>> "/Users/davideinstein/projects/sage/src/module_list.py", line 36, in 
>>  
>> > 
>> > [sagelib-9.1.beta9] png_pc = pkgconfig.parse('libpng') 
>> > 
>> > [sagelib-9.1.beta9]   File 
>> "/Users/davideinstein/projects/sage/local/lib/python3.7/site-packages/pkgconfig/pkgconfig.py",
>>  
>> line 248, in parse 
>> > 
>> > [sagelib-9.1.beta9] _raise_if_not_exists(package) 
>> > 
>> > [sagelib-9.1.beta9]   File 
>> "/Users/davideinstein/projects/sage/local/lib/python3.7/site-packages/pkgconfig/pkgconfig.py",
>>  
>> line 103, in _raise_if_not_exists 
>> > 
>> > [sagelib-9.1.beta9] raise PackageNotFoundError(package) 
>> > 
>> > [sagelib-9.1.beta9] pkgconfig.pkgconfig.PackageNotFoundError: libpng 
>> not found 
>> > 
>> > [sagelib-9.1.beta9] 
>>  
>> > 
>> > [sagelib-9.1.beta9] Error building the Sage library 
>> > 
>> > [sagelib-9.1.beta9] 
>>  
>> > 
>> > [sagelib-9.1.beta9] Please email sage-devel (
>> http://groups.google.com/group/sage-devel) 
>> > 
>> > [sagelib-9.1.beta9] explaining the problem and including the relevant 
>> part of the log file 
>> > 
>> > [sagelib-9.1.beta9]   
>> /Users/davideinstein/projects/sage/logs/pkgs/sagelib-9.1.beta9.log 
>> > 
>> > [sagelib-9.1.beta9] Describe your computer, operating system, etc. 
>> > 
>> > [sagelib-9.1.beta9] 
>>  
>> > 
>> > [sagelib-9.1.beta9] make[4]: *** [sage] Error 1 
>> > 
>> > [sagelib-9.1.beta9] 
>> > 
>> > [sagelib-9.1.beta9] real 0m0.612s 
>> > 
>> > [sagelib-9.1.beta9] user 0m0.193s 
>> > 
>> > [sagelib-9.1.beta9] sys 0m0.133s 
>> > 
>> > make[3]: *** [sagelib] Error 2 
>> > 
>> > make[2]: *** [all-start] Error 2 
>> > 
>> > 
>> > real 212m28.552s 
>> > 
>> > user 151m29.195s 
>> > 
>> > sys 26m1.334s 
>> > 
>> > *** 
>> > 
>> > Error building Sage. 
>> > 
>> > 
>> > The following package(s) may have failed to build (not necessarily 
>> > 
>> > during this run of 

Re: [sage-support] Building on Catalina

2020-04-08 Thread Dima Pasechnik
Could you post the outputs of

   pkg-config --modversion libpng
   set | grep PKG

run at the terminal, and run at the Sage shell prompt (./sage -sh) ?
I really don't understand this error, as at configure time libpng is
found via pkg-config
Thanks
Dima

On Thu, Apr 9, 2020 at 10:58 AM David Einstein  wrote:
>
> Here is the config.log.
>
> On Wednesday, April 8, 2020 at 10:32:51 PM UTC-4, Dima Pasechnik wrote:
>>
>> Hi David,
>> It might help if you posted the top-level config.log, thanks.
>>
>> Dima
>>
>> On Thu, Apr 9, 2020 at 9:58 AM David Einstein  wrote:
>> >
>> > I am trying to build on OSX Catalina, and everything seems to go well 
>> > until it builds sagelib, and I get a libpng not found.
>> >
>> > Everything built nicely a few weeks ago.  I am tempted to blame the 
>> > upgrade to catalina, but I also upgraded hombrew and XCode.
>> >
>> > Any ideas?
>> >
>> > Here is the final output from the terminal.
>> >
>> > if [ -z "$SAGE_INSTALL_FETCH_ONLY" ]; then \
>> >
>> > cd /Users/davideinstein/projects/sage/src && source bin/sage-env && source 
>> > /Users/davideinstein/projects/sage/build/bin/sage-build-env-config && \
>> >
>> > sage-logger -p 'time make sage' 
>> > '/Users/davideinstein/projects/sage/logs/pkgs/sagelib-9.1.beta9.log'; \
>> >
>> > fi
>> >
>> > [sagelib-9.1.beta9] cd . && export\
>> >
>> > [sagelib-9.1.beta9] SAGE_ROOT=/doesnotexist
>> >\
>> >
>> > [sagelib-9.1.beta9] SAGE_SRC=/doesnotexist 
>> >\
>> >
>> > [sagelib-9.1.beta9] SAGE_SRC_ROOT=/doesnotexist
>> >\
>> >
>> > [sagelib-9.1.beta9] SAGE_DOC_SRC=/doesnotexist 
>> >\
>> >
>> > [sagelib-9.1.beta9] SAGE_BUILD_DIR=/doesnotexist   
>> >\
>> >
>> > [sagelib-9.1.beta9] 
>> > SAGE_PKGS=/Users/davideinstein/projects/sage/build/pkgs\
>> >
>> > [sagelib-9.1.beta9] && sage-python -u setup.py --no-user-cfg build install
>> >
>> > [sagelib-9.1.beta9] /Users/davideinstein/projects/sage/src/bin/sage-env: 
>> > line 130: cd: /doesnotexist: No such file or directory
>> >
>> > [sagelib-9.1.beta9] Warning: overwriting SAGE_ROOT environment variable:
>> >
>> > [sagelib-9.1.beta9] Old SAGE_ROOT=/doesnotexist
>> >
>> > [sagelib-9.1.beta9] New SAGE_ROOT=
>> >
>> > [sagelib-9.1.beta9] 
>> > 
>> >
>> > [sagelib-9.1.beta9] Traceback (most recent call last):
>> >
>> > [sagelib-9.1.beta9]   File "setup.py", line 72, in 
>> >
>> > [sagelib-9.1.beta9] from module_list import ext_modules, library_order
>> >
>> > [sagelib-9.1.beta9]   File 
>> > "/Users/davideinstein/projects/sage/src/module_list.py", line 36, in 
>> > 
>> >
>> > [sagelib-9.1.beta9] png_pc = pkgconfig.parse('libpng')
>> >
>> > [sagelib-9.1.beta9]   File 
>> > "/Users/davideinstein/projects/sage/local/lib/python3.7/site-packages/pkgconfig/pkgconfig.py",
>> >  line 248, in parse
>> >
>> > [sagelib-9.1.beta9] _raise_if_not_exists(package)
>> >
>> > [sagelib-9.1.beta9]   File 
>> > "/Users/davideinstein/projects/sage/local/lib/python3.7/site-packages/pkgconfig/pkgconfig.py",
>> >  line 103, in _raise_if_not_exists
>> >
>> > [sagelib-9.1.beta9] raise PackageNotFoundError(package)
>> >
>> > [sagelib-9.1.beta9] pkgconfig.pkgconfig.PackageNotFoundError: libpng not 
>> > found
>> >
>> > [sagelib-9.1.beta9] 
>> > 
>> >
>> > [sagelib-9.1.beta9] Error building the Sage library
>> >
>> > [sagelib-9.1.beta9] 
>> > 
>> >
>> > [sagelib-9.1.beta9] Please email sage-devel 
>> > (http://groups.google.com/group/sage-devel)
>> >
>> > [sagelib-9.1.beta9] explaining the problem and including the relevant part 
>> > of the log file
>> >
>> > [sagelib-9.1.beta9]   
>> > /Users/davideinstein/projects/sage/logs/pkgs/sagelib-9.1.beta9.log
>> >
>> > [sagelib-9.1.beta9] Describe your computer, operating system, etc.
>> >
>> > [sagelib-9.1.beta9] 
>> > 
>> >
>> > [sagelib-9.1.beta9] make[4]: *** [sage] Error 1
>> >
>> > [sagelib-9.1.beta9]
>> >
>> > [sagelib-9.1.beta9] real 0m0.612s
>> >
>> > [sagelib-9.1.beta9] user 0m0.193s
>> >
>> > [sagelib-9.1.beta9] sys 0m0.133s
>> >
>> > make[3]: *** [sagelib] Error 2
>> >
>> > make[2]: *** [all-start] Error 2
>> >
>> >
>> > real 212m28.552s
>> >
>> > user 151m29.195s
>> >
>> > sys 26m1.334s
>> >
>> > ***
>> >
>> > Error building Sage.
>> >
>> >
>> > The following package(s) may have failed to build (not necessarily
>> >
>> > during this run of 'make all-start'):
>> >
>> >
>> > * package: sagelib-9.1.beta9
>> >
>> >   last build time: Apr 8 21:23
>> >
>> >   log file:
>> > 

Re: [sage-support] Sage Crash report

2020-04-08 Thread 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

2020-04-08 Thread 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] Building on Catalina

2020-04-08 Thread Dima Pasechnik
Hi David,
It might help if you posted the top-level config.log, thanks.

Dima

On Thu, Apr 9, 2020 at 9:58 AM David Einstein  wrote:
>
> I am trying to build on OSX Catalina, and everything seems to go well until 
> it builds sagelib, and I get a libpng not found.
>
> Everything built nicely a few weeks ago.  I am tempted to blame the upgrade 
> to catalina, but I also upgraded hombrew and XCode.
>
> Any ideas?
>
> Here is the final output from the terminal.
>
> if [ -z "$SAGE_INSTALL_FETCH_ONLY" ]; then \
>
> cd /Users/davideinstein/projects/sage/src && source bin/sage-env && source 
> /Users/davideinstein/projects/sage/build/bin/sage-build-env-config && \
>
> sage-logger -p 'time make sage' 
> '/Users/davideinstein/projects/sage/logs/pkgs/sagelib-9.1.beta9.log'; \
>
> fi
>
> [sagelib-9.1.beta9] cd . && export\
>
> [sagelib-9.1.beta9] SAGE_ROOT=/doesnotexist   
> \
>
> [sagelib-9.1.beta9] SAGE_SRC=/doesnotexist
> \
>
> [sagelib-9.1.beta9] SAGE_SRC_ROOT=/doesnotexist   
> \
>
> [sagelib-9.1.beta9] SAGE_DOC_SRC=/doesnotexist
> \
>
> [sagelib-9.1.beta9] SAGE_BUILD_DIR=/doesnotexist  
> \
>
> [sagelib-9.1.beta9] 
> SAGE_PKGS=/Users/davideinstein/projects/sage/build/pkgs\
>
> [sagelib-9.1.beta9] && sage-python -u setup.py --no-user-cfg build install
>
> [sagelib-9.1.beta9] /Users/davideinstein/projects/sage/src/bin/sage-env: line 
> 130: cd: /doesnotexist: No such file or directory
>
> [sagelib-9.1.beta9] Warning: overwriting SAGE_ROOT environment variable:
>
> [sagelib-9.1.beta9] Old SAGE_ROOT=/doesnotexist
>
> [sagelib-9.1.beta9] New SAGE_ROOT=
>
> [sagelib-9.1.beta9] 
> 
>
> [sagelib-9.1.beta9] Traceback (most recent call last):
>
> [sagelib-9.1.beta9]   File "setup.py", line 72, in 
>
> [sagelib-9.1.beta9] from module_list import ext_modules, library_order
>
> [sagelib-9.1.beta9]   File 
> "/Users/davideinstein/projects/sage/src/module_list.py", line 36, in 
>
> [sagelib-9.1.beta9] png_pc = pkgconfig.parse('libpng')
>
> [sagelib-9.1.beta9]   File 
> "/Users/davideinstein/projects/sage/local/lib/python3.7/site-packages/pkgconfig/pkgconfig.py",
>  line 248, in parse
>
> [sagelib-9.1.beta9] _raise_if_not_exists(package)
>
> [sagelib-9.1.beta9]   File 
> "/Users/davideinstein/projects/sage/local/lib/python3.7/site-packages/pkgconfig/pkgconfig.py",
>  line 103, in _raise_if_not_exists
>
> [sagelib-9.1.beta9] raise PackageNotFoundError(package)
>
> [sagelib-9.1.beta9] pkgconfig.pkgconfig.PackageNotFoundError: libpng not found
>
> [sagelib-9.1.beta9] 
> 
>
> [sagelib-9.1.beta9] Error building the Sage library
>
> [sagelib-9.1.beta9] 
> 
>
> [sagelib-9.1.beta9] Please email sage-devel 
> (http://groups.google.com/group/sage-devel)
>
> [sagelib-9.1.beta9] explaining the problem and including the relevant part of 
> the log file
>
> [sagelib-9.1.beta9]   
> /Users/davideinstein/projects/sage/logs/pkgs/sagelib-9.1.beta9.log
>
> [sagelib-9.1.beta9] Describe your computer, operating system, etc.
>
> [sagelib-9.1.beta9] 
> 
>
> [sagelib-9.1.beta9] make[4]: *** [sage] Error 1
>
> [sagelib-9.1.beta9]
>
> [sagelib-9.1.beta9] real 0m0.612s
>
> [sagelib-9.1.beta9] user 0m0.193s
>
> [sagelib-9.1.beta9] sys 0m0.133s
>
> make[3]: *** [sagelib] Error 2
>
> make[2]: *** [all-start] Error 2
>
>
> real 212m28.552s
>
> user 151m29.195s
>
> sys 26m1.334s
>
> ***
>
> Error building Sage.
>
>
> The following package(s) may have failed to build (not necessarily
>
> during this run of 'make all-start'):
>
>
> * package: sagelib-9.1.beta9
>
>   last build time: Apr 8 21:23
>
>   log file:
> /Users/davideinstein/projects/sage/logs/pkgs/sagelib-9.1.beta9.log
>
>
> It is safe to delete any log files and build directories, but they
>
> contain information that is helpful for debugging build problems.
>
> WARNING: If you now run 'make' again, the build directory of the
>
> same version of the package will, by default, be deleted. Set the
>
> environment variable SAGE_KEEP_BUILT_SPKGS=yes to prevent this.
>
>
> make[1]: *** [all-start] Error 1
>
> make: *** [all] Error 2
>
> --
> 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/d8e46d82-f201-4cbd-94ad-5bceccdc678c%40googlegroups.com.

-- 
You 

Re: [sage-support] Sage Crash report

2020-04-08 Thread 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

2020-04-08 Thread 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.