Re: [sage-devel] Re: Errors from MacOS build with Python3

2019-05-30 Thread John H Palmieri 


On Thursday, May 30, 2019 at 3:43:55 PM UTC-7, Brian Ball wrote:
>
> Thanks,
>
> Yes, I ran 
>
> make configure
>  ./configure --with-python=3 
> make build
>

You should run "make" rather than "make build" to get the documentation, 
too. Without it, some doctests will fail, in addition to just not having 
the documentation. (Or "make ptest-python3" ...)

 

>
> Many warnings - no errors
>
> There is no file logs/dochtml.log
> there is a logs/docutils.0.14.log (attached)
> It says:
> Successfully installed docutils-0.14
>
> I'll run make ptest-python3 as you suggest.
>
> Thanks again
>
> Brian
>
>
>
> On Thu, May 30, 2019 at 3:19 PM John H Palmieri  > wrote:
>
>>
>>
>> On Thursday, May 30, 2019 at 2:15:12 PM UTC-7, Brian Ball wrote:
>>>
>>> I built sage 8.7 with python 3.6.
>>>
>>
>> What do you mean by "built"? Did you run "make"? If so, did it complete 
>> without error? (I would find that surprising, since "make" should build the 
>> documentation.)
>>
>> What does the file logs/dochtml.log say?
>>
>>  
>>
>>>
>>> I then ran 
>>> ./sage --testall
>>> And many of the tests fail
>>>
>>
>> Many tests will fail with Python 3, since Python 3 builds of Sage are 
>> still in the experimental stage. See 
>> https://trac.sagemath.org/ticket/26212 for the current progress.
>>
>> Running "make ptest-python3" should run all tests which are known (on 
>> other platforms) to pass with a Python 3 build.
>>  
>>
>>>
>>> Attached is a zip file with all the logs - I hope it isn't too much 
>>> information.
>>>
>>> Also when I enter "manual()" in sage I get the following error
>>>
>>>
>>> OSError: The document 'reference' does not exist.  Please build it
>>>
>>> with 'sage -docbuild reference html --mathjax' and try again.
>>>
>>>
>>> I've done the sage -docbuild command several times - to no avail
>>>
>>>
>>> tutorial() also gets an error message:
>>>
>>>
>>> OSError: The document 'tutorial' does not exist.  Please build it
>>>
>>> with 'sage -docbuild tutorial html --mathjax' and try again.
>>>
>>>
>>> Thanks
>>>
>>>
>>> Brian Ball
>>>
>>>
>>>
>>>
>>>
>>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "sage-devel" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to sage-...@googlegroups.com .
>> To post to this group, send email to sage-...@googlegroups.com 
>> .
>> Visit this group at https://groups.google.com/group/sage-devel.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/sage-devel/0b4c7f39-a58b-4f32-9623-c9f7d4e09186%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/4e09e37a-7839-4f1d-8213-6f3547946484%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Errors from MacOS build with Python3

2019-05-30 Thread John H Palmieri 


On Thursday, May 30, 2019 at 2:15:12 PM UTC-7, Brian Ball wrote:
>
> I built sage 8.7 with python 3.6.
>

What do you mean by "built"? Did you run "make"? If so, did it complete 
without error? (I would find that surprising, since "make" should build the 
documentation.)

What does the file logs/dochtml.log say?

 

>
> I then ran 
> ./sage --testall
> And many of the tests fail
>

Many tests will fail with Python 3, since Python 3 builds of Sage are still 
in the experimental stage. See https://trac.sagemath.org/ticket/26212 for 
the current progress.

Running "make ptest-python3" should run all tests which are known (on other 
platforms) to pass with a Python 3 build.
 

>
> Attached is a zip file with all the logs - I hope it isn't too much 
> information.
>
> Also when I enter "manual()" in sage I get the following error
>
>
> OSError: The document 'reference' does not exist.  Please build it
>
> with 'sage -docbuild reference html --mathjax' and try again.
>
>
> I've done the sage -docbuild command several times - to no avail
>
>
> tutorial() also gets an error message:
>
>
> OSError: The document 'tutorial' does not exist.  Please build it
>
> with 'sage -docbuild tutorial html --mathjax' and try again.
>
>
> Thanks
>
>
> Brian Ball
>
>
>
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/0b4c7f39-a58b-4f32-9623-c9f7d4e09186%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Are Sage library files supposed to pass when using "sage -tp --file-iterations=N FILES"?

2019-05-30 Thread John H Palmieri 
If I run

./sage -tp --file-iterations=2 src/sage/algebras/

then I get many doctest failures. Is this expected? Is something broken 
when using the "--file-iterations" flag?

--
sage -t src/sage/algebras/free_algebra.py  # 1 doctest failed
sage -t src/sage/algebras/lie_algebras/morphism.py  # 1 doctest failed
sage -t src/sage/algebras/lie_algebras/structure_coefficients.py  # 3 
doctests failed
sage -t src/sage/algebras/lie_algebras/lie_algebra_element.pyx  # 1 doctest 
failed
sage -t src/sage/algebras/lie_algebras/lie_algebra.py  # 1 doctest failed
sage -t src/sage/algebras/cluster_algebra.py  # 5 doctests failed
sage -t src/sage/algebras/lie_algebras/free_lie_algebra.py  # 1 doctest 
failed
sage -t src/sage/algebras/tensor_algebra.py  # 2 doctests failed
--

Examples:

File "src/sage/algebras/free_algebra.py", line 498, in 
sage.algebras.free_algebra.FreeAlgebra_generic._repr_
Failed example:
F  # indirect doctest
Expected:
Free Algebra on 3 generators (x0, x1, x2) over Rational Field
Got:
QQ<>


File "src/sage/algebras/lie_algebras/morphism.py", line 42, in 
sage.algebras.lie_algebras.morphism.LieAlgebraHomomorphism_im_gens
Failed example:
H = L.Hall()
Expected:
doctest:warning...:
FutureWarning: The Hall basis has not been fully proven correct, but 
currently no bugs are known
See http://trac.sagemath.org/16823 for details.
Got:



File "src/sage/algebras/lie_algebras/structure_coefficients.py", line 357, 
in 
sage.algebras.lie_algebras.structure_coefficients.LieAlgebraWithStructureCoefficients.from_vector
Failed example:
L.from_vector([1, 2, -2])
Expected:
x + 2*y - 2*z
Got:
-2*z + 2*y + x

-- 
John

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/985c227d-3911-4f39-a4a7-9dd53415ee35%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: sagenb failed to build on 8.8.beta3

2019-05-30 Thread Dima Pasechnik 
OK, in your log of libgd I see

** Configuration summary for libgd ..:


   Support for PNG library:  no
...

whereas it must have been yes.

And the output of

$ otool -L local/lib/libgd.3.dylib

confirms that libpng was not linked to libgd. This is the cause of the error.
We should fix it. I've opened https://trac.sagemath.org/ticket/27901

Could you please post the log for libpng
logs/pkgs/libpng*.log ?

You have not mentioned the exact version of Sage you are trying to build.
What is it? 8.7? A recent beta?
(please post the config.log from the Sage's main directory)

Thanks.

On Thu, May 30, 2019 at 10:34 PM Dima Pasechnik  wrote:
>
> hmm, this looks OK too.
> What is the output of
>
> otool -L local/lib/libgd.3.dylib
>
> Thanks.
>
> On Thu, May 30, 2019 at 10:15 PM Colby Kelln  wrote:
> >
> > $ otool -L 
> > local/lib/python2.7/site-packages/sage/matrix/matrix_mod2_dense.so
> >
> > local/lib/python2.7/site-packages/sage/matrix/matrix_mod2_dense.so:
> >
> > /Users/Colby/Documents/Math/ICERM2019/sage_stuff/local/lib/libgmp.23.dylib 
> > (compatibility version 24.0.0, current version 24.3.0)
> >
> > /Users/Colby/Documents/Math/ICERM2019/sage_stuff/local/lib/libm4ri-0.0.20140914.dylib
> >  (compatibility version 0.0.0, current version 0.0.0)
> >
> > /Users/Colby/Documents/Math/ICERM2019/sage_stuff/local/lib/libgd.3.dylib 
> > (compatibility version 4.0.0, current version 4.0.0)
> >
> > /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 
> > 1252.250.1)
> >
> > /Users/Colby/Documents/Math/ICERM2019/sage_stuff/local/lib/libpari-gmp.dylib
> >  (compatibility version 2.11.0, current version 2.11.1)
> >
> >
> > On Thursday, May 30, 2019 at 3:47:46 PM UTC-4, Dima Pasechnik wrote:
> >>
> >> Thanks, this looks in order. Could you please post the output of
> >>
> >> otool -L local/lib/python2.7/site-packages/sage/matrix/matrix_mod2_dense.so
> >>
> >> I suspect it is linked to a "wrong" libgd.
> >>
> >>
> >> On Thu, May 30, 2019 at 6:51 PM Colby Kelln  wrote:
> >> >
> >> > I'm nearly certain this is the file you asked for; if not, let me know. 
> >> > I appreciate your help.
> >> >
> >> > On Thursday, May 30, 2019 at 4:44:18 AM UTC-4, Dima Pasechnik wrote:
> >> >>
> >> >> Thanks. sagenb is a package that depends on sage, and sage should 
> >> >> better be in working order at the moment it is built.
> >> >>
> >> >> the error message in the log indicates that perhaps libgd, another 
> >> >> package, has not been built correctly.
> >> >> Could you post log of it, logs/pkgs/libgd*.log ?
> >> >>
> >> >> thanks.
> >> >>
> >> >> On Thu, 30 May 2019 05:39 Colby Kelln,  wrote:
> >> >>>
> >> >>> The error message reads:
> >> >>>
> >> >>> Error installing package sagenb-1.1.2
> >> >>>
> >> >>>
> >> >>> So I've attached the sagenb-1.1.2 log file.
> >> >>> If it's relevant, the output also reads:
> >> >>>
> >> >>> RuntimeError: resolving lazy import dumps during startup
> >> >>>
> >> >>>
> >> >>> These errors occur just when building sage. I also attempted to run 
> >> >>> sage to see if that gave more info and I attached the crash report. 
> >> >>> Thanks, again.
> >> >>>
> >> >>>
> >> >>> On Wednesday, May 29, 2019 at 3:43:35 AM UTC-4, Dima Pasechnik wrote:
> >> 
> >>  On Wed, May 29, 2019 at 2:12 AM Colby Kelln  wrote:
> >>  >
> >>  > Hi,
> >>  >
> >>  > I'm receiving a similar error message. What exactly did you do to 
> >>  > fix the problem?
> >> 
> >>  it depends - try starting sage, and post the error message (and
> >>  probably the relevant logs, too) here.
> >> 
> >>  I wonder whether changing the way sagenb dependencies are dealt with
> >>  might make this error handling more robust.
> >> 
> >>  >
> >>  > Thanks
> >>  >
> >>  > On Sunday, April 21, 2019 at 10:30:49 AM UTC-4, vdelecroix wrote:
> >>  >>
> >>  >> Indeed, sage did not start... After fixing it, sagenb installs.
> >>  >>
> >>  >> The error message is really confusing.
> >>  >>
> >>  >> Le 21/04/2019 à 16:25, Dima Pasechnik a écrit :
> >>  >> > this error is an indication of an earlier build error. Try 
> >>  >> > starting sage.
> >>  >> >
> >>  >> > On Sun, 21 Apr 2019 15:13 Vincent Delecroix, 
> >>  >> > <20100.d...@gmail.com>
> >>  >> > wrote:
> >>  >> >
> >>  >> >> Ignore the second e-mail: the error occurred again compiling
> >>  >> >> from scratch.
> >>  >> >>
> >>  >> >> Le 21/04/2019 à 14:24, Vincent Delecroix a écrit :
> >>  >> >>> It appears to be a problem with my setup.
> >>  >> >>>
> >>  >> >>> I had some Python libraries in my $HOME/.sage/local
> >>  >> >>> that made interference with the sage installation.
> >>  >> >>>
> >>  >> >>> Vincent
> >>  >> >>>
> >>  >> >>> Le 21/04/2019 à 13:22, Vincent Delecroix a écrit :
> >>  >>  Dear all,
> >>  >> 
> >>  >>  Starting from scratch, I failed to build sagenb. More 
> >>

Re: [sage-devel] Re: sagenb failed to build on 8.8.beta3

2019-05-30 Thread Colby Kelln 
 

$ otool -L local/lib/libgd.3.dylib 

local/lib/libgd.3.dylib:

/Users/Colby/Documents/Math/ICERM2019/sage_stuff/local/lib/libgd.3.dylib 
(compatibility version 4.0.0, current version 4.0.0)

/usr/lib/libiconv.2.dylib (compatibility version 7.0.0, current version 
7.0.0)

/usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.11)

/Users/Colby/Documents/Math/ICERM2019/sage_stuff/local/lib/libfreetype.6.dylib 
(compatibility version 23.0.0, current version 23.1.0)

/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 
1252.250.1)

On Thursday, May 30, 2019 at 5:34:46 PM UTC-4, Dima Pasechnik wrote:
>
> hmm, this looks OK too. 
> What is the output of 
>
> otool -L local/lib/libgd.3.dylib 
>
> Thanks. 
>
> On Thu, May 30, 2019 at 10:15 PM Colby Kelln  > wrote: 
> > 
> > $ otool -L 
> local/lib/python2.7/site-packages/sage/matrix/matrix_mod2_dense.so 
> > 
> > local/lib/python2.7/site-packages/sage/matrix/matrix_mod2_dense.so: 
> > 
> > 
> /Users/Colby/Documents/Math/ICERM2019/sage_stuff/local/lib/libgmp.23.dylib 
> (compatibility version 24.0.0, current version 24.3.0) 
> > 
> > 
> /Users/Colby/Documents/Math/ICERM2019/sage_stuff/local/lib/libm4ri-0.0.20140914.dylib
>  
> (compatibility version 0.0.0, current version 0.0.0) 
> > 
> > /Users/Colby/Documents/Math/ICERM2019/sage_stuff/local/lib/libgd.3.dylib 
> (compatibility version 4.0.0, current version 4.0.0) 
> > 
> > /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 
> 1252.250.1) 
> > 
> > 
> /Users/Colby/Documents/Math/ICERM2019/sage_stuff/local/lib/libpari-gmp.dylib 
> (compatibility version 2.11.0, current version 2.11.1) 
> > 
> > 
> > On Thursday, May 30, 2019 at 3:47:46 PM UTC-4, Dima Pasechnik wrote: 
> >> 
> >> Thanks, this looks in order. Could you please post the output of 
> >> 
> >> otool -L 
> local/lib/python2.7/site-packages/sage/matrix/matrix_mod2_dense.so 
> >> 
> >> I suspect it is linked to a "wrong" libgd. 
> >> 
> >> 
> >> On Thu, May 30, 2019 at 6:51 PM Colby Kelln  wrote: 
> >> > 
> >> > I'm nearly certain this is the file you asked for; if not, let me 
> know. I appreciate your help. 
> >> > 
> >> > On Thursday, May 30, 2019 at 4:44:18 AM UTC-4, Dima Pasechnik wrote: 
> >> >> 
> >> >> Thanks. sagenb is a package that depends on sage, and sage should 
> better be in working order at the moment it is built. 
> >> >> 
> >> >> the error message in the log indicates that perhaps libgd, another 
> package, has not been built correctly. 
> >> >> Could you post log of it, logs/pkgs/libgd*.log ? 
> >> >> 
> >> >> thanks. 
> >> >> 
> >> >> On Thu, 30 May 2019 05:39 Colby Kelln,  wrote: 
> >> >>> 
> >> >>> The error message reads: 
> >> >>> 
> >> >>> Error installing package sagenb-1.1.2 
> >> >>> 
> >> >>> 
> >> >>> So I've attached the sagenb-1.1.2 log file. 
> >> >>> If it's relevant, the output also reads: 
> >> >>> 
> >> >>> RuntimeError: resolving lazy import dumps during startup 
> >> >>> 
> >> >>> 
> >> >>> These errors occur just when building sage. I also attempted to run 
> sage to see if that gave more info and I attached the crash report. Thanks, 
> again. 
> >> >>> 
> >> >>> 
> >> >>> On Wednesday, May 29, 2019 at 3:43:35 AM UTC-4, Dima Pasechnik 
> wrote: 
> >>  
> >>  On Wed, May 29, 2019 at 2:12 AM Colby Kelln  
> wrote: 
> >>  > 
> >>  > Hi, 
> >>  > 
> >>  > I'm receiving a similar error message. What exactly did you do 
> to fix the problem? 
> >>  
> >>  it depends - try starting sage, and post the error message (and 
> >>  probably the relevant logs, too) here. 
> >>  
> >>  I wonder whether changing the way sagenb dependencies are dealt 
> with 
> >>  might make this error handling more robust. 
> >>  
> >>  > 
> >>  > Thanks 
> >>  > 
> >>  > On Sunday, April 21, 2019 at 10:30:49 AM UTC-4, vdelecroix 
> wrote: 
> >>  >> 
> >>  >> Indeed, sage did not start... After fixing it, sagenb installs. 
> >>  >> 
> >>  >> The error message is really confusing. 
> >>  >> 
> >>  >> Le 21/04/2019 à 16:25, Dima Pasechnik a écrit : 
> >>  >> > this error is an indication of an earlier build error. Try 
> starting sage. 
> >>  >> > 
> >>  >> > On Sun, 21 Apr 2019 15:13 Vincent Delecroix, <
> 20100.d...@gmail.com> 
> >>  >> > wrote: 
> >>  >> > 
> >>  >> >> Ignore the second e-mail: the error occurred again compiling 
> >>  >> >> from scratch. 
> >>  >> >> 
> >>  >> >> Le 21/04/2019 à 14:24, Vincent Delecroix a écrit : 
> >>  >> >>> It appears to be a problem with my setup. 
> >>  >> >>> 
> >>  >> >>> I had some Python libraries in my $HOME/.sage/local 
> >>  >> >>> that made interference with the sage installation. 
> >>  >> >>> 
> >>  >> >>> Vincent 
> >>  >> >>> 
> >>  >> >>> Le 21/04/2019 à 13:22, Vincent Delecroix a écrit : 
> >>  >>  Dear all, 
> >>  >>  
> >>  >>  Starting from

Re: [sage-devel] Re: sagenb failed to build on 8.8.beta3

2019-05-30 Thread Dima Pasechnik 
hmm, this looks OK too.
What is the output of

otool -L local/lib/libgd.3.dylib

Thanks.

On Thu, May 30, 2019 at 10:15 PM Colby Kelln  wrote:
>
> $ otool -L local/lib/python2.7/site-packages/sage/matrix/matrix_mod2_dense.so
>
> local/lib/python2.7/site-packages/sage/matrix/matrix_mod2_dense.so:
>
> /Users/Colby/Documents/Math/ICERM2019/sage_stuff/local/lib/libgmp.23.dylib 
> (compatibility version 24.0.0, current version 24.3.0)
>
> /Users/Colby/Documents/Math/ICERM2019/sage_stuff/local/lib/libm4ri-0.0.20140914.dylib
>  (compatibility version 0.0.0, current version 0.0.0)
>
> /Users/Colby/Documents/Math/ICERM2019/sage_stuff/local/lib/libgd.3.dylib 
> (compatibility version 4.0.0, current version 4.0.0)
>
> /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 
> 1252.250.1)
>
> /Users/Colby/Documents/Math/ICERM2019/sage_stuff/local/lib/libpari-gmp.dylib 
> (compatibility version 2.11.0, current version 2.11.1)
>
>
> On Thursday, May 30, 2019 at 3:47:46 PM UTC-4, Dima Pasechnik wrote:
>>
>> Thanks, this looks in order. Could you please post the output of
>>
>> otool -L local/lib/python2.7/site-packages/sage/matrix/matrix_mod2_dense.so
>>
>> I suspect it is linked to a "wrong" libgd.
>>
>>
>> On Thu, May 30, 2019 at 6:51 PM Colby Kelln  wrote:
>> >
>> > I'm nearly certain this is the file you asked for; if not, let me know. I 
>> > appreciate your help.
>> >
>> > On Thursday, May 30, 2019 at 4:44:18 AM UTC-4, Dima Pasechnik wrote:
>> >>
>> >> Thanks. sagenb is a package that depends on sage, and sage should better 
>> >> be in working order at the moment it is built.
>> >>
>> >> the error message in the log indicates that perhaps libgd, another 
>> >> package, has not been built correctly.
>> >> Could you post log of it, logs/pkgs/libgd*.log ?
>> >>
>> >> thanks.
>> >>
>> >> On Thu, 30 May 2019 05:39 Colby Kelln,  wrote:
>> >>>
>> >>> The error message reads:
>> >>>
>> >>> Error installing package sagenb-1.1.2
>> >>>
>> >>>
>> >>> So I've attached the sagenb-1.1.2 log file.
>> >>> If it's relevant, the output also reads:
>> >>>
>> >>> RuntimeError: resolving lazy import dumps during startup
>> >>>
>> >>>
>> >>> These errors occur just when building sage. I also attempted to run sage 
>> >>> to see if that gave more info and I attached the crash report. Thanks, 
>> >>> again.
>> >>>
>> >>>
>> >>> On Wednesday, May 29, 2019 at 3:43:35 AM UTC-4, Dima Pasechnik wrote:
>> 
>>  On Wed, May 29, 2019 at 2:12 AM Colby Kelln  wrote:
>>  >
>>  > Hi,
>>  >
>>  > I'm receiving a similar error message. What exactly did you do to fix 
>>  > the problem?
>> 
>>  it depends - try starting sage, and post the error message (and
>>  probably the relevant logs, too) here.
>> 
>>  I wonder whether changing the way sagenb dependencies are dealt with
>>  might make this error handling more robust.
>> 
>>  >
>>  > Thanks
>>  >
>>  > On Sunday, April 21, 2019 at 10:30:49 AM UTC-4, vdelecroix wrote:
>>  >>
>>  >> Indeed, sage did not start... After fixing it, sagenb installs.
>>  >>
>>  >> The error message is really confusing.
>>  >>
>>  >> Le 21/04/2019 à 16:25, Dima Pasechnik a écrit :
>>  >> > this error is an indication of an earlier build error. Try 
>>  >> > starting sage.
>>  >> >
>>  >> > On Sun, 21 Apr 2019 15:13 Vincent Delecroix, <20100.d...@gmail.com>
>>  >> > wrote:
>>  >> >
>>  >> >> Ignore the second e-mail: the error occurred again compiling
>>  >> >> from scratch.
>>  >> >>
>>  >> >> Le 21/04/2019 à 14:24, Vincent Delecroix a écrit :
>>  >> >>> It appears to be a problem with my setup.
>>  >> >>>
>>  >> >>> I had some Python libraries in my $HOME/.sage/local
>>  >> >>> that made interference with the sage installation.
>>  >> >>>
>>  >> >>> Vincent
>>  >> >>>
>>  >> >>> Le 21/04/2019 à 13:22, Vincent Delecroix a écrit :
>>  >>  Dear all,
>>  >> 
>>  >>  Starting from scratch, I failed to build sagenb. More precisely,
>>  >>  it failed building its documentation with
>>  >> 
>>  >>  Running Sphinx v1.8.5
>>  >>  making output directory...
>>  >>  building [mo]: targets for 0 po files that are out of date
>>  >>  building [html]: targets for 19 source files that are out of 
>>  >>  date
>>  >>  updating environment: 19 added, 0 changed, 0 removed
>>  >>  reading sources... [  5%] index
>>  >>  reading sources... [ 10%] misc/introspect
>>  >>  reading sources... [ 15%] misc/misc
>>  >> 
>>  >>  Exception occurred:
>>  >>  File "sage/misc/lazy_import.pyx", line 218, in
>>  >>  sage.misc.lazy_import.LazyImport._get_object
>>  >>  (build/cythonized/sage/misc/lazy_import.c:2495)
>>  >>    raise RuntimeError(f"resolving lazy import {self._name} 
>>  >>  during
>>

Re: [sage-devel] Re: sagenb failed to build on 8.8.beta3

2019-05-30 Thread Colby Kelln 
 

$ otool -L 
local/lib/python2.7/site-packages/sage/matrix/matrix_mod2_dense.so

local/lib/python2.7/site-packages/sage/matrix/matrix_mod2_dense.so:

/Users/Colby/Documents/Math/ICERM2019/sage_stuff/local/lib/libgmp.23.dylib 
(compatibility version 24.0.0, current version 24.3.0)

/Users/Colby/Documents/Math/ICERM2019/sage_stuff/local/lib/libm4ri-0.0.20140914.dylib
 
(compatibility version 0.0.0, current version 0.0.0)

/Users/Colby/Documents/Math/ICERM2019/sage_stuff/local/lib/libgd.3.dylib 
(compatibility version 4.0.0, current version 4.0.0)

/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 
1252.250.1)

/Users/Colby/Documents/Math/ICERM2019/sage_stuff/local/lib/libpari-gmp.dylib 
(compatibility version 2.11.0, current version 2.11.1)

On Thursday, May 30, 2019 at 3:47:46 PM UTC-4, Dima Pasechnik wrote:
>
> Thanks, this looks in order. Could you please post the output of 
>
> otool -L 
> local/lib/python2.7/site-packages/sage/matrix/matrix_mod2_dense.so 
>
> I suspect it is linked to a "wrong" libgd. 
>
>
> On Thu, May 30, 2019 at 6:51 PM Colby Kelln  > wrote: 
> > 
> > I'm nearly certain this is the file you asked for; if not, let me know. 
> I appreciate your help. 
> > 
> > On Thursday, May 30, 2019 at 4:44:18 AM UTC-4, Dima Pasechnik wrote: 
> >> 
> >> Thanks. sagenb is a package that depends on sage, and sage should 
> better be in working order at the moment it is built. 
> >> 
> >> the error message in the log indicates that perhaps libgd, another 
> package, has not been built correctly. 
> >> Could you post log of it, logs/pkgs/libgd*.log ? 
> >> 
> >> thanks. 
> >> 
> >> On Thu, 30 May 2019 05:39 Colby Kelln,  wrote: 
> >>> 
> >>> The error message reads: 
> >>> 
> >>> Error installing package sagenb-1.1.2 
> >>> 
> >>> 
> >>> So I've attached the sagenb-1.1.2 log file. 
> >>> If it's relevant, the output also reads: 
> >>> 
> >>> RuntimeError: resolving lazy import dumps during startup 
> >>> 
> >>> 
> >>> These errors occur just when building sage. I also attempted to run 
> sage to see if that gave more info and I attached the crash report. Thanks, 
> again. 
> >>> 
> >>> 
> >>> On Wednesday, May 29, 2019 at 3:43:35 AM UTC-4, Dima Pasechnik wrote: 
>  
>  On Wed, May 29, 2019 at 2:12 AM Colby Kelln  
> wrote: 
>  > 
>  > Hi, 
>  > 
>  > I'm receiving a similar error message. What exactly did you do to 
> fix the problem? 
>  
>  it depends - try starting sage, and post the error message (and 
>  probably the relevant logs, too) here. 
>  
>  I wonder whether changing the way sagenb dependencies are dealt with 
>  might make this error handling more robust. 
>  
>  > 
>  > Thanks 
>  > 
>  > On Sunday, April 21, 2019 at 10:30:49 AM UTC-4, vdelecroix wrote: 
>  >> 
>  >> Indeed, sage did not start... After fixing it, sagenb installs. 
>  >> 
>  >> The error message is really confusing. 
>  >> 
>  >> Le 21/04/2019 à 16:25, Dima Pasechnik a écrit : 
>  >> > this error is an indication of an earlier build error. Try 
> starting sage. 
>  >> > 
>  >> > On Sun, 21 Apr 2019 15:13 Vincent Delecroix, <
> 20100.d...@gmail.com> 
>  >> > wrote: 
>  >> > 
>  >> >> Ignore the second e-mail: the error occurred again compiling 
>  >> >> from scratch. 
>  >> >> 
>  >> >> Le 21/04/2019 à 14:24, Vincent Delecroix a écrit : 
>  >> >>> It appears to be a problem with my setup. 
>  >> >>> 
>  >> >>> I had some Python libraries in my $HOME/.sage/local 
>  >> >>> that made interference with the sage installation. 
>  >> >>> 
>  >> >>> Vincent 
>  >> >>> 
>  >> >>> Le 21/04/2019 à 13:22, Vincent Delecroix a écrit : 
>  >>  Dear all, 
>  >>  
>  >>  Starting from scratch, I failed to build sagenb. More 
> precisely, 
>  >>  it failed building its documentation with 
>  >>  
>  >>  Running Sphinx v1.8.5 
>  >>  making output directory... 
>  >>  building [mo]: targets for 0 po files that are out of date 
>  >>  building [html]: targets for 19 source files that are out of 
> date 
>  >>  updating environment: 19 added, 0 changed, 0 removed 
>  >>  reading sources... [  5%] index 
>  >>  reading sources... [ 10%] misc/introspect 
>  >>  reading sources... [ 15%] misc/misc 
>  >>  
>  >>  Exception occurred: 
>  >>  File "sage/misc/lazy_import.pyx", line 218, in 
>  >>  sage.misc.lazy_import.LazyImport._get_object 
>  >>  (build/cythonized/sage/misc/lazy_import.c:2495) 
>  >>    raise RuntimeError(f"resolving lazy import {self._name} 
> during 
>  >>  startup") 
>  >>  RuntimeError: resolving lazy import dumps during startup 
>  >>  
>  >>  See also the more complete log in attachment. 
>  >>  
>  >>  Vincent 
>  >> >> 
>  >>

Re: [sage-devel] error building sage for Scientific Linux 7.6

2019-05-30 Thread Dima Pasechnik 
On Thu, May 30, 2019 at 8:51 PM Charles Campbell  wrote:
>
> Been trying to build sage 8.7 under Scientific Linux (a redhat derivative); 
> actually, I've tried to do so on and off for several years with no success 
> ever.  I've installed openblas.x86_64 already.
>
> From make:
>
> The following package(s) may have failed to build (not necessarily
> during this run of 'make all-start'):
>
> * package: openblas-0.3.5.p0
>   log file: /home/cecbkup/SW/SAGE/sage-8.7/logs/pkgs/openblas-0.3.5.p0.log
>   build directory: 
> /home/cecbkup/SW/SAGE/sage-8.7/local/var/tmp/sage/build/openblas-0.3.5.p0
>
> * package: pari_seadata_small-20090618.p0
>   log file: 
> /home/cecbkup/SW/SAGE/sage-8.7/logs/pkgs/pari_seadata_small-20090618.p0.log
>   build directory: 
> /home/cecbkup/SW/SAGE/sage-8.7/local/var/tmp/sage/build/pari_seadata_small-20090618.p0
>
> I have no idea where pari... comes from;

pari comes from Sage as well; there is a package called pari, of which
pari_seadata_small
is a part. So it's perfectly normal that directory
'/home/cecbkup/SW/SAGE/sage-8.7/local/./share/pari' already exists.

Do you have `cp` aliased to something (perhaps at the system level)
that produces this weird error in your log?

 >Copying package files from temporary location
/home/cecbkup/SW/SAGE/sage-8.7/local/var/tmp/sage/build/pari_seadata_small-20090618.p0/inst
to > /home/cecbkup/SW/SAGE/sage-8.7/local
> cp: cannot create directory 
> '/home/cecbkup/SW/SAGE/sage-8.7/local/./share/pari': File exists




> yum -y list shows
>
> opari2.x86_64   1.1.2-3.el7epel
> paris-traceroute.x86_64 0.92-6.el7 epel
>
> Neither of which are "pari", although perhaps "opari..." is close.
>
> Regards,
> Charles Campbell
>
> --
> You received this message because you are subscribed to the Google Groups 
> "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to sage-devel+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-devel.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/f087424b-b8a3-4f86-854c-fd2372695f81%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAAWYfq0N1m6Df5t_Jqh5D%3Dfijq-m_eVAM%2BpONWXkrex5GtC9QA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] error building sage for Scientific Linux 7.6

2019-05-30 Thread Charles Campbell 
Been trying to build sage 8.7 under Scientific Linux (a redhat derivative); 
actually, I've tried to do so on and off for several years with no success 
ever.  I've installed openblas.x86_64 already.

>From make:

The following package(s) may have failed to build (not necessarily
during this run of 'make all-start'):

* package: openblas-0.3.5.p0
  log file: /home/cecbkup/SW/SAGE/sage-8.7/logs/pkgs/openblas-0.3.5.p0.log
  build directory: 
/home/cecbkup/SW/SAGE/sage-8.7/local/var/tmp/sage/build/openblas-0.3.5.p0

* package: pari_seadata_small-20090618.p0
  log file: 
/home/cecbkup/SW/SAGE/sage-8.7/logs/pkgs/pari_seadata_small-20090618.p0.log
  build directory: 
/home/cecbkup/SW/SAGE/sage-8.7/local/var/tmp/sage/build/pari_seadata_small-20090618.p0

I have no idea where pari... comes from; yum -y list shows

opari2.x86_64   1.1.2-3.el7
epel 
paris-traceroute.x86_64 0.92-6.el7 epel 

Neither of which are "pari", although perhaps "opari..." is close.

Regards,
Charles Campbell

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/f087424b-b8a3-4f86-854c-fd2372695f81%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Found local metadata for pari_seadata_small-20090618.p0
Using cached file 
/home/cecbkup/SW/SAGE/sage-8.7/upstream/pari_seadata_small-20090618.tar.bz2
pari_seadata_small-20090618.p0

Setting up build directory for pari_seadata_small-20090618.p0
Finished extraction
No patch files found in ../patches

Host system:
Linux sphinx.campbellfamily.biz 3.10.0-957.el7.x86_64 #1 SMP Tue Oct 30 
14:13:26 CDT 2018 x86_64 x86_64 x86_64 GNU/Linux

C compiler: gcc
C compiler version:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-redhat-linux/4.8.5/lto-wrapper
Target: x86_64-redhat-linux
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man 
--infodir=/usr/share/info --with-bugurl=http://bugzilla.redhat.com/bugzilla 
--enable-bootstrap --enable-shared --enable-threads=posix 
--enable-checking=release --with-system-zlib --enable-__cxa_atexit 
--disable-libunwind-exceptions --enable-gnu-unique-object 
--enable-linker-build-id --with-linker-hash-style=gnu 
--enable-languages=c,c++,objc,obj-c++,java,fortran,ada,go,lto --enable-plugin 
--enable-initfini-array --disable-libgcj 
--with-isl=/builddir/build/BUILD/gcc-4.8.5-20150702/obj-x86_64-redhat-linux/isl-install
 
--with-cloog=/builddir/build/BUILD/gcc-4.8.5-20150702/obj-x86_64-redhat-linux/cloog-install
 --enable-gnu-indirect-function --with-tune=generic --with-arch_32=x86-64 
--build=x86_64-redhat-linux
Thread model: posix
gcc version 4.8.5 20150623 (Red Hat 4.8.5-36) (GCC) 

Package 'pari_seadata_small' is currently not installed
No legacy uninstaller found for 'pari_seadata_small'; nothing to do
src/seadata -> 
/home/cecbkup/SW/SAGE/sage-8.7/local/var/tmp/sage/build/pari_seadata_small-20090618.p0/inst/home/cecbkup/SW/SAGE/sage-8.7/local/share/pari

real0m0.014s
user0m0.003s
sys 0m0.010s
Copying package files from temporary location 
/home/cecbkup/SW/SAGE/sage-8.7/local/var/tmp/sage/build/pari_seadata_small-20090618.p0/inst
 to /home/cecbkup/SW/SAGE/sage-8.7/local
cp: cannot create directory 
'/home/cecbkup/SW/SAGE/sage-8.7/local/./share/pari': File exists

Error copying files for pari_seadata_small-20090618.p0.

Please email sage-devel (http://groups.google.com/group/sage-devel)
explaining the problem and including the log file
  /home/cecbkup/SW/SAGE/sage-8.7/logs/pkgs/pari_seadata_small-20090618.p0.log
Describe your computer, operating system, etc.

Re: [sage-devel] Re: sagenb failed to build on 8.8.beta3

2019-05-30 Thread Dima Pasechnik 
Thanks, this looks in order. Could you please post the output of

otool -L local/lib/python2.7/site-packages/sage/matrix/matrix_mod2_dense.so

I suspect it is linked to a "wrong" libgd.


On Thu, May 30, 2019 at 6:51 PM Colby Kelln  wrote:
>
> I'm nearly certain this is the file you asked for; if not, let me know. I 
> appreciate your help.
>
> On Thursday, May 30, 2019 at 4:44:18 AM UTC-4, Dima Pasechnik wrote:
>>
>> Thanks. sagenb is a package that depends on sage, and sage should better be 
>> in working order at the moment it is built.
>>
>> the error message in the log indicates that perhaps libgd, another package, 
>> has not been built correctly.
>> Could you post log of it, logs/pkgs/libgd*.log ?
>>
>> thanks.
>>
>> On Thu, 30 May 2019 05:39 Colby Kelln,  wrote:
>>>
>>> The error message reads:
>>>
>>> Error installing package sagenb-1.1.2
>>>
>>>
>>> So I've attached the sagenb-1.1.2 log file.
>>> If it's relevant, the output also reads:
>>>
>>> RuntimeError: resolving lazy import dumps during startup
>>>
>>>
>>> These errors occur just when building sage. I also attempted to run sage to 
>>> see if that gave more info and I attached the crash report. Thanks, again.
>>>
>>>
>>> On Wednesday, May 29, 2019 at 3:43:35 AM UTC-4, Dima Pasechnik wrote:

 On Wed, May 29, 2019 at 2:12 AM Colby Kelln  wrote:
 >
 > Hi,
 >
 > I'm receiving a similar error message. What exactly did you do to fix 
 > the problem?

 it depends - try starting sage, and post the error message (and
 probably the relevant logs, too) here.

 I wonder whether changing the way sagenb dependencies are dealt with
 might make this error handling more robust.

 >
 > Thanks
 >
 > On Sunday, April 21, 2019 at 10:30:49 AM UTC-4, vdelecroix wrote:
 >>
 >> Indeed, sage did not start... After fixing it, sagenb installs.
 >>
 >> The error message is really confusing.
 >>
 >> Le 21/04/2019 à 16:25, Dima Pasechnik a écrit :
 >> > this error is an indication of an earlier build error. Try starting 
 >> > sage.
 >> >
 >> > On Sun, 21 Apr 2019 15:13 Vincent Delecroix, <20100.d...@gmail.com>
 >> > wrote:
 >> >
 >> >> Ignore the second e-mail: the error occurred again compiling
 >> >> from scratch.
 >> >>
 >> >> Le 21/04/2019 à 14:24, Vincent Delecroix a écrit :
 >> >>> It appears to be a problem with my setup.
 >> >>>
 >> >>> I had some Python libraries in my $HOME/.sage/local
 >> >>> that made interference with the sage installation.
 >> >>>
 >> >>> Vincent
 >> >>>
 >> >>> Le 21/04/2019 à 13:22, Vincent Delecroix a écrit :
 >>  Dear all,
 >> 
 >>  Starting from scratch, I failed to build sagenb. More precisely,
 >>  it failed building its documentation with
 >> 
 >>  Running Sphinx v1.8.5
 >>  making output directory...
 >>  building [mo]: targets for 0 po files that are out of date
 >>  building [html]: targets for 19 source files that are out of date
 >>  updating environment: 19 added, 0 changed, 0 removed
 >>  reading sources... [  5%] index
 >>  reading sources... [ 10%] misc/introspect
 >>  reading sources... [ 15%] misc/misc
 >> 
 >>  Exception occurred:
 >>  File "sage/misc/lazy_import.pyx", line 218, in
 >>  sage.misc.lazy_import.LazyImport._get_object
 >>  (build/cythonized/sage/misc/lazy_import.c:2495)
 >>    raise RuntimeError(f"resolving lazy import {self._name} 
 >>  during
 >>  startup")
 >>  RuntimeError: resolving lazy import dumps during startup
 >> 
 >>  See also the more complete log in attachment.
 >> 
 >>  Vincent
 >> >>
 >> >> --
 >> >> You received this message because you are subscribed to the Google 
 >> >> Groups
 >> >> "sage-devel" group.
 >> >> To unsubscribe from this group and stop receiving emails from it, 
 >> >> send an
 >> >> email to sage-...@googlegroups.com.
 >> >> To post to this group, send email to sage-...@googlegroups.com.
 >> >> Visit this group at https://groups.google.com/group/sage-devel.
 >> >> For more options, visit https://groups.google.com/d/optout.
 >> >>
 >> >
 >
 > --
 > You received this message because you are subscribed to the Google 
 > Groups "sage-devel" group.
 > To unsubscribe from this group and stop receiving emails from it, send 
 > an email to sage-...@googlegroups.com.
 > To post to this group, send email to sage-...@googlegroups.com.
 > Visit this group at https://groups.google.com/group/sage-devel.
 > To view this discussion on the web visit 
 > https://groups.google.com/d/msgid/sage-devel/85ea0bea-c855-47fa-b82e-f21d2594cd95%40googlegroups.com.
 > For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: sagenb failed to build on 8.8.beta3

2019-05-30 Thread Colby Kelln 
I'm nearly certain this is the file you asked for; if not, let me know. I 
appreciate your help. 

On Thursday, May 30, 2019 at 4:44:18 AM UTC-4, Dima Pasechnik wrote:
>
> Thanks. sagenb is a package that depends on sage, and sage should better 
> be in working order at the moment it is built. 
>
> the error message in the log indicates that perhaps libgd, another 
> package, has not been built correctly.
> Could you post log of it, logs/pkgs/libgd*.log ?
>
> thanks.
>
> On Thu, 30 May 2019 05:39 Colby Kelln, > 
> wrote:
>
>> The error message reads: 
>>
>> Error installing package sagenb-1.1.2
>>
>>
>> So I've attached the sagenb-1.1.2 log file. 
>> If it's relevant, the output also reads:
>>
>> RuntimeError: resolving lazy import dumps during startup
>>
>>
>> These errors occur just when building sage. I also attempted to run sage 
>> to see if that gave more info and I attached the crash report. Thanks, 
>> again. 
>>
>> On Wednesday, May 29, 2019 at 3:43:35 AM UTC-4, Dima Pasechnik wrote:
>>>
>>> On Wed, May 29, 2019 at 2:12 AM Colby Kelln  wrote: 
>>> > 
>>> > Hi, 
>>> > 
>>> > I'm receiving a similar error message. What exactly did you do to fix 
>>> the problem? 
>>>
>>> it depends - try starting sage, and post the error message (and 
>>> probably the relevant logs, too) here. 
>>>
>>> I wonder whether changing the way sagenb dependencies are dealt with 
>>> might make this error handling more robust. 
>>>
>>> > 
>>> > Thanks 
>>> > 
>>> > On Sunday, April 21, 2019 at 10:30:49 AM UTC-4, vdelecroix wrote: 
>>> >> 
>>> >> Indeed, sage did not start... After fixing it, sagenb installs. 
>>> >> 
>>> >> The error message is really confusing. 
>>> >> 
>>> >> Le 21/04/2019 à 16:25, Dima Pasechnik a écrit : 
>>> >> > this error is an indication of an earlier build error. Try starting 
>>> sage. 
>>> >> > 
>>> >> > On Sun, 21 Apr 2019 15:13 Vincent Delecroix, <20100.d...@gmail.com> 
>>>
>>> >> > wrote: 
>>> >> > 
>>> >> >> Ignore the second e-mail: the error occurred again compiling 
>>> >> >> from scratch. 
>>> >> >> 
>>> >> >> Le 21/04/2019 à 14:24, Vincent Delecroix a écrit : 
>>> >> >>> It appears to be a problem with my setup. 
>>> >> >>> 
>>> >> >>> I had some Python libraries in my $HOME/.sage/local 
>>> >> >>> that made interference with the sage installation. 
>>> >> >>> 
>>> >> >>> Vincent 
>>> >> >>> 
>>> >> >>> Le 21/04/2019 à 13:22, Vincent Delecroix a écrit : 
>>> >>  Dear all, 
>>> >>  
>>> >>  Starting from scratch, I failed to build sagenb. More precisely, 
>>> >>  it failed building its documentation with 
>>> >>  
>>> >>  Running Sphinx v1.8.5 
>>> >>  making output directory... 
>>> >>  building [mo]: targets for 0 po files that are out of date 
>>> >>  building [html]: targets for 19 source files that are out of 
>>> date 
>>> >>  updating environment: 19 added, 0 changed, 0 removed 
>>> >>  reading sources... [  5%] index 
>>> >>  reading sources... [ 10%] misc/introspect 
>>> >>  reading sources... [ 15%] misc/misc 
>>> >>  
>>> >>  Exception occurred: 
>>> >>  File "sage/misc/lazy_import.pyx", line 218, in 
>>> >>  sage.misc.lazy_import.LazyImport._get_object 
>>> >>  (build/cythonized/sage/misc/lazy_import.c:2495) 
>>> >>    raise RuntimeError(f"resolving lazy import {self._name} 
>>> during 
>>> >>  startup") 
>>> >>  RuntimeError: resolving lazy import dumps during startup 
>>> >>  
>>> >>  See also the more complete log in attachment. 
>>> >>  
>>> >>  Vincent 
>>> >> >> 
>>> >> >> -- 
>>> >> >> You received this message because you are subscribed to the Google 
>>> Groups 
>>> >> >> "sage-devel" group. 
>>> >> >> To unsubscribe from this group and stop receiving emails from it, 
>>> send an 
>>> >> >> email to sage-...@googlegroups.com. 
>>> >> >> To post to this group, send email to sage-...@googlegroups.com. 
>>> >> >> Visit this group at https://groups.google.com/group/sage-devel. 
>>> >> >> For more options, visit https://groups.google.com/d/optout. 
>>> >> >> 
>>> >> > 
>>> > 
>>> > -- 
>>> > You received this message because you are subscribed to the Google 
>>> Groups "sage-devel" group. 
>>> > To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to sage-...@googlegroups.com. 
>>> > To post to this group, send email to sage-...@googlegroups.com. 
>>> > Visit this group at https://groups.google.com/group/sage-devel. 
>>> > To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/sage-devel/85ea0bea-c855-47fa-b82e-f21d2594cd95%40googlegroups.com.
>>>  
>>>
>>> > For more options, visit https://groups.google.com/d/optout. 
>>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "sage-devel" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to sage-...@googlegroups.com .
>> To post to this group, send email to sage-...@googlegroups.com

Re: [sage-devel] build error on Mac OS X 10.12.6

2019-05-30 Thread Brian Ball 
Thanks!  That was the clue I needed.  I had a *lot* of "zombie" processes I
needed to kill.

I finished the install:

This looks like the first time you are running Sage.

Cleaning up, do not interrupt this.

Done cleaning.

┌┐

│ SageMath version 8.7, Release Date: 2019-03-23 │

│ Using Python 3.6.6. Type "help()" for help.│

└┘

sage:

On Thu, May 30, 2019 at 7:21 AM Dima Pasechnik  wrote:

> this looks like:
>
> https://lists.apple.com/archives/xcode-users/2012/Nov/msg00215.html
>
> On Thu, 30 May 2019 03:51 Brian Ball,  wrote:
>
>> I am attempting to build Sage from source with Python 3.7.3
>>
>> Logs attached.
>>
>> I run
>>
>> ./configure --with-python=3
>>
>>
>> and at the end I get the following:
>>
>> make[3]: ***
>> [/MyFiles/Numbthy/sage-8.7/local/var/lib/sage/installed/openblas-0.3.5.p0]
>> Error 1
>>
>> make[2]: *** [all-build] Error 2
>>
>>
>> real 74m3.592s
>>
>> user 22m42.854s
>>
>> sys 4m29.081s
>>
>> ***
>>
>> Error building Sage.
>>
>>
>> The following package(s) may have failed to build (not necessarily
>>
>> during this run of 'make all-build'):
>>
>>
>> * package: openblas-0.3.5.p0
>>
>>   log file: /MyFiles/Numbthy/sage-8.7/logs/pkgs/openblas-0.3.5.p0.log
>>
>>   build directory:
>> /MyFiles/Numbthy/sage-8.7/local/var/tmp/sage/build/openblas-0.3.5.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-build] Error 1
>>
>> make: *** [build] Error 2
>>
>>
>> Thanks for your help
>>
>>
>> Brian Ball
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "sage-devel" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to sage-devel+unsubscr...@googlegroups.com.
>> To post to this group, send email to sage-devel@googlegroups.com.
>> Visit this group at https://groups.google.com/group/sage-devel.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/sage-devel/d3ef8a6c-7642-43cd-808b-0488b0597a72%40googlegroups.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-devel+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-devel.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-devel/CAAWYfq2G7%2B__Ti7wYFb-RJbkAS0-1RTWOuseJCEV4_%2BPw1r_KA%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAHVkz5PqKwiASBSpF8wBesksrCkTYjvMx9US3hsDEyhF92E3iQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] build error on Mac OS X 10.12.6

2019-05-30 Thread Dima Pasechnik 
this looks like:

https://lists.apple.com/archives/xcode-users/2012/Nov/msg00215.html

On Thu, 30 May 2019 03:51 Brian Ball,  wrote:

> I am attempting to build Sage from source with Python 3.7.3
>
> Logs attached.
>
> I run
>
> ./configure --with-python=3
>
>
> and at the end I get the following:
>
> make[3]: ***
> [/MyFiles/Numbthy/sage-8.7/local/var/lib/sage/installed/openblas-0.3.5.p0]
> Error 1
>
> make[2]: *** [all-build] Error 2
>
>
> real 74m3.592s
>
> user 22m42.854s
>
> sys 4m29.081s
>
> ***
>
> Error building Sage.
>
>
> The following package(s) may have failed to build (not necessarily
>
> during this run of 'make all-build'):
>
>
> * package: openblas-0.3.5.p0
>
>   log file: /MyFiles/Numbthy/sage-8.7/logs/pkgs/openblas-0.3.5.p0.log
>
>   build directory:
> /MyFiles/Numbthy/sage-8.7/local/var/tmp/sage/build/openblas-0.3.5.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-build] Error 1
>
> make: *** [build] Error 2
>
>
> Thanks for your help
>
>
> Brian Ball
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-devel+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-devel.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-devel/d3ef8a6c-7642-43cd-808b-0488b0597a72%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAAWYfq2G7%2B__Ti7wYFb-RJbkAS0-1RTWOuseJCEV4_%2BPw1r_KA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] error building pynormaliz with 8.8.beta6

2019-05-30 Thread Michael Orlitzky 
On 5/30/19 12:33 AM, Michael Orlitzky wrote:
> 
> As yet unexplained is why manually running "bash configure" works, but
> the autoconf bash re-exec does not. My own strace shows that running
> "dash configure" will wind up running
> 
>   execve("/bin/bash", ["/bin/bash", "/home/mjo/src/sage-8.8.beta6
>   /con"...], 0x55d1c04303f8 /* 68 vars */) = 0
> 
> instead of executing either "/bin/bash configure" in the CWD, or
> "/bin/bash /path/to/pynormaliz's/configure".
> 

This is due to the "what script am I" detection built in to the
configure script by autoconf:

  # Find who we are.  Look in the path if we contain no directory
  # separator.
  as_myself=
  case $0 in #((
*[\\/]* ) as_myself=$0 ;;
*) as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
  for as_dir in $PATH
  do
IFS=$as_save_IFS
test -z "$as_dir" && as_dir=.
  test -r "$as_dir/$0" && as_myself=$as_dir/$0 && break
done
  IFS=$as_save_IFS

   ;;
  esac

I'm going to ask about this on the autoconf mailing list, but for
pre-existing ./configure scripts, there's nothing we can do about it.
The best fix is probably what we've already decided: to make sure that
we run "./configure" instead of "sh configure".

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/e47ee757-978e-8273-5c6f-076085b47f75%40orlitzky.com.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] numerical_approx for polynomials

2019-05-30 Thread Thierry 
Hi,

i would prefer to raise an error promoting the use of change_ring (same
for matrices), which allows more tuning on the base ring.

By the way, note that the best approx with floating-point coefficients
(e.g. for the sup norm on [-1,1]), is not necessarilly obtained with the
best approx on each coefficients.

Ciao,
Thierry



On Thu, May 30, 2019 at 11:38:45AM +0200, Vincent Delecroix wrote:
> Dear devs,
> 
> Is it fine if I implement numerical_approx on polynomials by calling
> it recursively on coefficients? For example, we would have
> 
> sage: x = polygen(QQ)
> sage: p = 1343235439458/23 * x^2 - 234 / 143425*x + 1432/6512
> sage: p.numerical_approx()
> 5.8401540846e10*x^2 - 0.00163151472895241*x + 0.219901719901720
> 
> Right now, it does raise a TypeError (raised inside the generic
> numerical_approx).
> 
> It would fit with what we have for matrices
> 
> sage: matrix(2, [11/23, -5/3, 132/7, 77/12]).n()
> [0.478260869565217 -1.67]
> [ 18.8571428571429  6.416667]
> 
> Best
> Vincent
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to sage-devel+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-devel.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/f75cfe1a-5856-03be-4940-aafd7a4812f5%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-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/20190530103036.aa34rpw2xplrejei%40metelu.net.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] numerical_approx for polynomials

2019-05-30 Thread Vincent Delecroix 

Dear devs,

Is it fine if I implement numerical_approx on polynomials by calling
it recursively on coefficients? For example, we would have

sage: x = polygen(QQ)
sage: p = 1343235439458/23 * x^2 - 234 / 143425*x + 1432/6512
sage: p.numerical_approx()
5.8401540846e10*x^2 - 0.00163151472895241*x + 0.219901719901720

Right now, it does raise a TypeError (raised inside the generic
numerical_approx).

It would fit with what we have for matrices

sage: matrix(2, [11/23, -5/3, 132/7, 77/12]).n()
[0.478260869565217 -1.67]
[ 18.8571428571429  6.416667]

Best
Vincent

--
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/f75cfe1a-5856-03be-4940-aafd7a4812f5%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: sagenb failed to build on 8.8.beta3

2019-05-30 Thread Dima Pasechnik 
Thanks. sagenb is a package that depends on sage, and sage should better be
in working order at the moment it is built.

the error message in the log indicates that perhaps libgd, another package,
has not been built correctly.
Could you post log of it, logs/pkgs/libgd*.log ?

thanks.

On Thu, 30 May 2019 05:39 Colby Kelln,  wrote:

> The error message reads:
>
> Error installing package sagenb-1.1.2
>
>
> So I've attached the sagenb-1.1.2 log file.
> If it's relevant, the output also reads:
>
> RuntimeError: resolving lazy import dumps during startup
>
>
> These errors occur just when building sage. I also attempted to run sage
> to see if that gave more info and I attached the crash report. Thanks,
> again.
>
> On Wednesday, May 29, 2019 at 3:43:35 AM UTC-4, Dima Pasechnik wrote:
>>
>> On Wed, May 29, 2019 at 2:12 AM Colby Kelln  wrote:
>> >
>> > Hi,
>> >
>> > I'm receiving a similar error message. What exactly did you do to fix
>> the problem?
>>
>> it depends - try starting sage, and post the error message (and
>> probably the relevant logs, too) here.
>>
>> I wonder whether changing the way sagenb dependencies are dealt with
>> might make this error handling more robust.
>>
>> >
>> > Thanks
>> >
>> > On Sunday, April 21, 2019 at 10:30:49 AM UTC-4, vdelecroix wrote:
>> >>
>> >> Indeed, sage did not start... After fixing it, sagenb installs.
>> >>
>> >> The error message is really confusing.
>> >>
>> >> Le 21/04/2019 à 16:25, Dima Pasechnik a écrit :
>> >> > this error is an indication of an earlier build error. Try starting
>> sage.
>> >> >
>> >> > On Sun, 21 Apr 2019 15:13 Vincent Delecroix, <20100.d...@gmail.com>
>> >> > wrote:
>> >> >
>> >> >> Ignore the second e-mail: the error occurred again compiling
>> >> >> from scratch.
>> >> >>
>> >> >> Le 21/04/2019 à 14:24, Vincent Delecroix a écrit :
>> >> >>> It appears to be a problem with my setup.
>> >> >>>
>> >> >>> I had some Python libraries in my $HOME/.sage/local
>> >> >>> that made interference with the sage installation.
>> >> >>>
>> >> >>> Vincent
>> >> >>>
>> >> >>> Le 21/04/2019 à 13:22, Vincent Delecroix a écrit :
>> >>  Dear all,
>> >> 
>> >>  Starting from scratch, I failed to build sagenb. More precisely,
>> >>  it failed building its documentation with
>> >> 
>> >>  Running Sphinx v1.8.5
>> >>  making output directory...
>> >>  building [mo]: targets for 0 po files that are out of date
>> >>  building [html]: targets for 19 source files that are out of date
>> >>  updating environment: 19 added, 0 changed, 0 removed
>> >>  reading sources... [  5%] index
>> >>  reading sources... [ 10%] misc/introspect
>> >>  reading sources... [ 15%] misc/misc
>> >> 
>> >>  Exception occurred:
>> >>  File "sage/misc/lazy_import.pyx", line 218, in
>> >>  sage.misc.lazy_import.LazyImport._get_object
>> >>  (build/cythonized/sage/misc/lazy_import.c:2495)
>> >>    raise RuntimeError(f"resolving lazy import {self._name}
>> during
>> >>  startup")
>> >>  RuntimeError: resolving lazy import dumps during startup
>> >> 
>> >>  See also the more complete log in attachment.
>> >> 
>> >>  Vincent
>> >> >>
>> >> >> --
>> >> >> You received this message because you are subscribed to the Google
>> Groups
>> >> >> "sage-devel" group.
>> >> >> To unsubscribe from this group and stop receiving emails from it,
>> send an
>> >> >> email to sage-...@googlegroups.com.
>> >> >> To post to this group, send email to sage-...@googlegroups.com.
>> >> >> Visit this group at https://groups.google.com/group/sage-devel.
>> >> >> For more options, visit https://groups.google.com/d/optout.
>> >> >>
>> >> >
>> >
>> > --
>> > You received this message because you are subscribed to the Google
>> Groups "sage-devel" group.
>> > To unsubscribe from this group and stop receiving emails from it, send
>> an email to sage-...@googlegroups.com.
>> > To post to this group, send email to sage-...@googlegroups.com.
>> > Visit this group at https://groups.google.com/group/sage-devel.
>> > To view this discussion on the web visit
>> https://groups.google.com/d/msgid/sage-devel/85ea0bea-c855-47fa-b82e-f21d2594cd95%40googlegroups.com.
>>
>> > For more options, visit https://groups.google.com/d/optout.
>>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-devel+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-devel.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-devel/89753d95-56d0-486a-8417-1a9634ebfced%40googlegroups.com
> 
> .
> For more options, visit

[sage-devel] Continuous benchmarking

2019-05-30 Thread Samuel Lelièvre 
Dear sage-devel,

This blog post on continuous benchmarking looks interesting!

https://medium.com/@wolfv/building-an-open-source-continuous-benchmark-system-717839093962

There have been related discussions on this list in the past,
for example around airspeed velocity:

https://groups.google.com/forum/#!searchin/sage-devel/airspeed$20velocity%7Csort:date

Kind regards,
Samuel

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAEcArF0nArs2Jos4U7BbpcyDS%2BqGx%3D%3DaHjN2s9fnY9GfCaYPQA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.