[sage-devel] Re: can no longer push to trac from ubuntu 22.04

[Steven Trogdon]

I must sent email to you by mistake. Perhaps this is the issue

https://groups.google.com/g/sage-devel/c/RArcnGt0i6E

On Thursday, May 5, 2022 at 8:43:38 AM UTC-6 Frédéric Chapoton wrote:

> Hello,
> Since I recently upgraded my ubuntu to 22.04, I cannot push from and pull 
> to 
>
> g...@trac.sagemath.org: Permission denied (publickey).
>
> I suspect some incompatibility between my brand-new local ssh installation 
> and the one on the trac server. Maybe the trac server should be updated to 
> use a more recent os, with a more recent ssh ?
>
> The ssh log indicates that there is some incompatibility :
>
> debug1: send_pubkey_test: no mutual signature algorithm
>
> Frédéric
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/0b1375a5-cdb1-462a-aec1-839c239c9dfan%40googlegroups.com.

[sage-devel] --random-seed and consistent doctest results

[Steven Trogdon]

With 9.6.beta7 I have the following failure when running the testsuite

sage -t --long --warn-long 96.7 
--random-seed=323793429833434243810534467855837341563 
src/sage/schemes/toric/sheaf/klyachko.py
**
File "src/sage/schemes/toric/sheaf/klyachko.py", line 951, in 
sage.schemes.toric.sheaf.klyachko.KlyachkoBundle_class.random_deformation
Failed example:
Vtilde.cohomology(dim=True, weight=(0,))
Expected:
(1, 0)
Got:
(0, 0)

which I can replicate by running the test individually as

./sage -t --long --warn-long 96.7 
--random-seed=323793429833434243810534467855837341563 
src/sage/schemes/toric/sheaf/klyachko.py

However, when I run the individual test as
./sage -t --long src/sage/schemes/toric/sheaf/klyachko.py

I get

sage -t --long --warn-long 90.1 
--random-seed=257179504306441420102668740208004283296 
src/sage/schemes/toric/sheaf/klyachko.py
[151 tests, 13.49 s]
--
All tests passed! 

So, it appears the choice of random-seed affects the test results. And Sage 
makes this sellection. Isn't this odd?

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/97d5bb6d-0ca6-46e9-a3c4-3c922a3b8a6bn%40googlegroups.com.

[sage-devel] Re: pdf docs from jupyter notebook

[Steven Trogdon]

This is now https://trac.sagemath.org/ticket/33206 where the issue is, 
hopefully, more clearly explained and a potential solution provided.

On Monday, January 10, 2022 at 11:30:27 AM UTC-7 Eric Gourgoulhon wrote:

> Hi, 
>
> I am not sure to understand what your problem is:  from a Sage Jupyter 
> notebook, if I click on the "Help" menu and select "Sage Documentation", 
> then a new tab opens in the browser at the address
> http://localhost:/kernelspecs/sagemath/doc/index.html
> It displays html documentation and there is no attempt to show any pdf 
> file.
> This is with Sage 9.5.rc0 running on Ubuntu 20.04. 
>
> Eric.
> Le dimanche 9 janvier 2022 à 19:26:01 UTC+1, Steven Trogdon a écrit :
>
>> From a new Sagemath jupyter notebook if I select the Sage Documentation I 
>> have numerous PDF links which are broken., for example
>>
>> [W 11:01:19.061 NotebookApp] 404 GET 
>> /kernelspecs/pdf/en/tutorial/SageTutorial.pdf (::1): Kernel spec pdf not 
>> found
>> [W 11:01:19.062 NotebookApp] 404 GET 
>> /kernelspecs/pdf/en/tutorial/SageTutorial.pdf (::1) 3.14ms referer=
>> http://localhost:/kernelspecs/sagemath/doc/index.html
>>
>> Are these links supposed to work from the notebook? They do work if the 
>> path
>>
>> file:///$SAGE_ROOT/local/share/doc/sage/html/en/index.html
>>
>> is pasted in a brower.
>>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/2a85aa5b-600c-49d4-8bfd-3d683f4a1540n%40googlegroups.com.

Re: [sage-devel] trouble pushing to a ticket

[Steven Trogdon]

Didn't mean to send a private email. This worked, thanks. I was aware of 
the change but didn't realize the extent. Thanks again.

On Wednesday, January 19, 2022 at 10:09:42 PM UTC-7 Michael Orlitzky wrote:

> On Wed, 2022-01-19 at 21:04 -0800, Steven Trogdon wrote:
> > I'm having difficulty pushing to a ticket, which I've done many times 
> > previously. When I push, i.e.
> > 
> > 
>
> OpenSSH 8.8 (recently stable on Gentoo) disables RSA with SHA-1. You
> can work around it, but probably the best long-term solution is to
> replace your RSA key with an ECDSA one (ssh-keygen -t ecdsa) and re-
> upload it to trac.
>
>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/2110484e-b8a4-4ceb-8311-e1b1c946331bn%40googlegroups.com.

[sage-devel] trouble pushing to a ticket

[Steven Trogdon]

I'm having difficulty pushing to a ticket, which I've done many times 
previously. When I push, i.e.

git trac push ticket#

I get

STDERR: g...@trac.sagemath.org: Permission denied (publickey).
STDERR: fatal: Could not read from remote repository.
STDERR: 
STDERR: Please make sure you have the correct access rights
STDERR: and the repository exists

My ssh key is correct (I have not changed it) however

ssh g...@trac.sagemath.org info

gives

g...@trac.sagemath.org: Permission denied (publickey)

Any ideas how to resolve this. I can login, create a ticket but unable to 
push to a ticket.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/16960982-17e5-4c66-82a0-d35807a0345bn%40googlegroups.com.

[sage-devel] Re: pdf docs from jupyter notebook

[Steven Trogdon]

Things are now working. When I open "Sage Documentation", at the top of the 
page there is "Sage Documentation v9.5.rc0", then "Tutorials and FAQ" and 
then, for example "Tutorial". The "Tutorial" is a link to the "html" 
documentation, but beside this link is a PDF icon that links to pdf 
documentation. The "Tutorial" link works but the PDF link fails. This may 
only show if the pdf documentation has been built.
On Monday, January 10, 2022 at 11:30:27 AM UTC-7 Eric Gourgoulhon wrote:

> Hi, 
>
> I am not sure to understand what your problem is:  from a Sage Jupyter 
> notebook, if I click on the "Help" menu and select "Sage Documentation", 
> then a new tab opens in the browser at the address
> http://localhost:/kernelspecs/sagemath/doc/index.html
> It displays html documentation and there is no attempt to show any pdf 
> file.
> This is with Sage 9.5.rc0 running on Ubuntu 20.04. 
>
> Eric.
> Le dimanche 9 janvier 2022 à 19:26:01 UTC+1, Steven Trogdon a écrit :
>
>> From a new Sagemath jupyter notebook if I select the Sage Documentation I 
>> have numerous PDF links which are broken., for example
>>
>> [W 11:01:19.061 NotebookApp] 404 GET 
>> /kernelspecs/pdf/en/tutorial/SageTutorial.pdf (::1): Kernel spec pdf not 
>> found
>> [W 11:01:19.062 NotebookApp] 404 GET 
>> /kernelspecs/pdf/en/tutorial/SageTutorial.pdf (::1) 3.14ms referer=
>> http://localhost:/kernelspecs/sagemath/doc/index.html
>>
>> Are these links supposed to work from the notebook? They do work if the 
>> path
>>
>> file:///$SAGE_ROOT/local/share/doc/sage/html/en/index.html
>>
>> is pasted in a brower.
>>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/78e2ad53-5db5-427f-8003-34f8573aefcbn%40googlegroups.com.

[sage-devel] Re: pdf docs from jupyter notebook

[Steven Trogdon]

I'm presently unable to get the jupyter kernel to start with Sage 9.5.rc0 , 
so I will respond more directly when that is fixed. However, with 9.5.beta9 
when I opened "Sage Documentation" there was not only links to html 
documentation but beside each link there was a PDF icon to get pdf 
documentation. When that PDF icon was "clicked" I received the terminal 
error in my first post. I'm rebuilding 9.5.rc0 to see if the jupyter kernel 
issue is resolved.
On Monday, January 10, 2022 at 11:30:27 AM UTC-7 Eric Gourgoulhon wrote:

> Hi, 
>
> I am not sure to understand what your problem is:  from a Sage Jupyter 
> notebook, if I click on the "Help" menu and select "Sage Documentation", 
> then a new tab opens in the browser at the address
> http://localhost:/kernelspecs/sagemath/doc/index.html
> It displays html documentation and there is no attempt to show any pdf 
> file.
> This is with Sage 9.5.rc0 running on Ubuntu 20.04. 
>
> Eric.
> Le dimanche 9 janvier 2022 à 19:26:01 UTC+1, Steven Trogdon a écrit :
>
>> From a new Sagemath jupyter notebook if I select the Sage Documentation I 
>> have numerous PDF links which are broken., for example
>>
>> [W 11:01:19.061 NotebookApp] 404 GET 
>> /kernelspecs/pdf/en/tutorial/SageTutorial.pdf (::1): Kernel spec pdf not 
>> found
>> [W 11:01:19.062 NotebookApp] 404 GET 
>> /kernelspecs/pdf/en/tutorial/SageTutorial.pdf (::1) 3.14ms referer=
>> http://localhost:/kernelspecs/sagemath/doc/index.html
>>
>> Are these links supposed to work from the notebook? They do work if the 
>> path
>>
>> file:///$SAGE_ROOT/local/share/doc/sage/html/en/index.html
>>
>> is pasted in a brower.
>>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/eb8228d7-55f1-41f4-a816-2119896e0e6fn%40googlegroups.com.

[sage-devel] pdf docs from jupyter notebook

[Steven Trogdon]

>From a new Sagemath jupyter notebook if I select the Sage Documentation I 
have numerous PDF links which are broken., for example

[W 11:01:19.061 NotebookApp] 404 GET 
/kernelspecs/pdf/en/tutorial/SageTutorial.pdf (::1): Kernel spec pdf not 
found
[W 11:01:19.062 NotebookApp] 404 GET 
/kernelspecs/pdf/en/tutorial/SageTutorial.pdf (::1) 3.14ms 
referer=http://localhost:/kernelspecs/sagemath/doc/index.html

Are these links supposed to work from the notebook? They do work if the path

file:///$SAGE_ROOT/local/share/doc/sage/html/en/index.html

is pasted in a brower.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/051a5904-7612-4b5e-819a-97dda3ac466cn%40googlegroups.com.

[sage-devel] sage --install

[Steven Trogdon]

Is this still supposed to work?

./sage --installed
[package]...[latest version] ([version])

Traceback (most recent call last):
  File "/local/sage-git/sage/src/bin/sage-list-packages", line 102, in 

pkg.installed_version = pkg.installed_version or 'not_installed'
AttributeError: can't set attribute

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/be74ef2a-54c8-482d-9377-30696e188855n%40googlegroups.com.

Re: [sage-devel] [abi:cxx11] in givaro prevents linking to system givaro on Fedora 32

[Steven Trogdon]

Building Givaro on Gentoo I have

CXXFLAGS=-O2 -pipe -march=native -O2 -pipe   -fabi-version=6   -msse -msse2 
-msse3 -mssse3 -msse4.1 -msse4.2 -mavx

Your Redhat has

CXXFLAGS=-O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 
-Wp,-D_GLIBCXX_ASSERTIONS -fexceptions -fstack-protector-strong 
-grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 
-specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic 
-fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection

Could the  abi-version=6 be the issue?

On Saturday, May 8, 2021 at 6:01:02 AM UTC-6 dim...@gmail.com wrote:

> one has 
> https://kojipkgs.fedoraproject.org//packages/givaro/4.1.1/1.fc32/data/logs/x86_64/build.log
> and other logs there
>
> On Saturday, May 8, 2021 at 12:45:07 PM UTC+1 Dima Pasechnik wrote:
>
>> On Saturday, May 8, 2021 at 12:34:11 PM UTC+1 François Bissey wrote:
>>
>>> What compiler and flags have used to compile fedora 32 givaro? Can we 
>>> easily find out?
>>
>>
>> the compiler used to build Sage is g++ 10.2.1
>>
>> $ g++ -v
>> Using built-in specs.
>> COLLECT_GCC=/usr/bin/g++
>> COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-redhat-linux/10/lto-wrapper
>> OFFLOAD_TARGET_NAMES=nvptx-none
>> OFFLOAD_TARGET_DEFAULT=1
>> Target: x86_64-redhat-linux
>> Configured with: ../configure --enable-bootstrap 
>> --enable-languages=c,c++,fortran,objc,obj-c++,ada,go,d,lto --prefix=/usr 
>> --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=
>> http://bugzilla.redhat.com/bugzilla --enable-shared 
>> --enable-threads=posix --enable-checking=release --enable-multilib 
>> --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions 
>> --enable-gnu-unique-object --enable-linker-build-id 
>> --with-gcc-major-version-only --with-linker-hash-style=gnu --enable-plugin 
>> --enable-initfini-array --with-isl --enable-offload-targets=nvptx-none 
>> --without-cuda-driver --enable-gnu-indirect-function --enable-cet 
>> --with-tune=generic --with-arch_32=i686 --build=x86_64-redhat-linux
>> Thread model: posix
>> Supported LTO compression algorithms: zlib zstd
>> gcc version 10.2.1 20201125 (Red Hat 10.2.1-9) (GCC) 
>>
>>  
>>
>>>
>>>
>>> > On 8/05/2021, at 23:31, Dima Pasechnik  wrote: 
>>> > 
>>> > With system Givaro, one gets 
>>> > 
>>> > [dochtml] ImportError: 
>>> /home/scratch2/dimpase/sage/sage/local/lib64/python3.8/site-packages/sage/matrix/
>>> matrix_modn_sparse.cpython-38-x86_64-linux-gnu.so: undefined symbol: 
>>> _ZNK6Givaro7IntegercvNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEB5cxx11Ev
>>>  
>>>
>>> > make[3]: *** [Makefile:2280: doc-html] Error 1 
>>> > 
>>> > which demangled says 
>>> > 
>>> > $ c++filt 
>>> _ZNK6Givaro7IntegercvNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEB5cxx11Ev
>>>  
>>>
>>> > Givaro::Integer::operator std::__cxx11::basic_string>> std::char_traits, std::allocator >[abi:cxx11]() const 
>>> > 
>>> > The system library has Givaro::Integer::operator 
>>> std::__cxx11::basic_string, 
>>> std::allocator >() const 
>>> > 
>>> > (no of that weird [abi:cxx11] qualifier) 
>>> > 
>>> > Any ideas how to fix this? (besides not using system Givaro) ? 
>>> > 
>>> > Dima 
>>> > 
>>> > -- 
>>> > 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+...@googlegroups.com. 
>>> > To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/sage-devel/b187faf3-50c4-42c4-ae37-77c5a3902bbcn%40googlegroups.com.
>>>  
>>>
>>>
>>>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/8321ce07-a17e-4d65-9bf2-18abe9b82e12n%40googlegroups.com.

[sage-devel] ModuleNotFoundError in doctesting src/sage/misc/sageinspect.py

[Steven Trogdon]

I've created https://trac.sagemath.org/ticket/31626 for the above. Perhaps 
someone has some input. The computer (gentoo linux) on which Sage is 
installed is relatively new.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/22787887-d72c-48d6-a777-51cb62ec4cddn%40googlegroups.com.

[sage-devel] Gentoo: Unable to configure vanilla Sage with system fplll

[Steven Trogdon]

On gentoo, after

make fplll-clean
./configure --with-system-fplll=yes

from config.log there is

configure:39046: result: fplll-5.4.0: no 
suitable system package; will be installed as an SPKG

However, I have system fplll-5.4.0 installed

[I] sci-libs/fplll
 Available versions:  ~4.0.4 5.3.2(0/6) (~)5.3.3(0/6) (~)5.4.0(0/7) {qd 
static-libs}
 Installed versions:  5.4.0(0/7)(12:27:23 PM 12/22/2020)(-qd 
-static-libs)
 Homepage:https://github.com/fplll/fplll
 Description: Implementations of the floating-point LLL 
reduction algorithm

Is this the expected behavior?

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/beb8dff9-7208-4bf6-9824-e962aaadef47n%40googlegroups.com.

[sage-devel] Re: Sage with system brial

[Steven Trogdon]

Thanks much. I knew there should be something simple.

On Wednesday, September 2, 2020 at 12:34:20 PM UTC-6, Matthias Koeppe wrote:
>
> Use "make brial-clean" to uninstall the spkg.
>
> On Wednesday, September 2, 2020 at 11:29:21 AM UTC-7, Steven Trogdon wrote:
>>
>> Is it possible to build Sage using ones system brial? I have
>>
>> ./configure --with-system-brial=yes LDFLAGS=-Wl,-O1 -Wl,--as-needed 
>> --no-create --no-recursion
>>
>> and then from config.log
>>
>> ## -- ##
>> ## Checking whether SageMath should install SPKG brial... ##
>> ## -- ##
>> configure:14262: brial has already been installed by SageMath
>> ## -- ##
>>
>> So, apparently since the brial spkg has been installed Sage will not use 
>> my system brial. Is there a way to sanely remove the brial spkg so that my 
>> system brial will be used? I don't see anything from 'configure --help' 
>> that directly addressed this.
>>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/70ab050f-c638-4d78-ad21-213b62750c57o%40googlegroups.com.

[sage-devel] Sage with system brial

[Steven Trogdon]

Is it possible to build Sage using ones system brial? I have

./configure --with-system-brial=yes LDFLAGS=-Wl,-O1 -Wl,--as-needed 
--no-create --no-recursion

and then from config.log

## -- ##
## Checking whether SageMath should install SPKG brial... ##
## -- ##
configure:14262: brial has already been installed by SageMath
## -- ##

So, apparently since the brial spkg has been installed Sage will not use my 
system brial. Is there a way to sanely remove the brial spkg so that my 
system brial will be used? I don't see anything from 'configure --help' 
that directly addressed this.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/1fdc70d2-44af-4e47-9dae-48acfb073510o%40googlegroups.com.

[sage-devel] Re: Should valgrind work when running doctests?

[Steven Trogdon]

I believe 

./sage -t --long --valgrind "doctest"

is broken. Please see https://trac.sagemath.org/ticket/27381 for a fix.

On Monday, February 25, 2019 at 10:36:47 PM UTC-6, Steven Trogdon wrote:
>
> Running ./sage --valgrind works with a resulting sage prompt. However,
>
> ./sage -t --long --valgrind src/sage/combinat/tableau.py
>
> does not work. The ~/.sage/valgrind/sage-memcheck. file reads
>
> ==8525== Memcheck, a memory error detector
> ==8525== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
> ==8525== Using Valgrind-3.14.0 and LibVEX; rerun with -h for copyright info
> ==8525== Command: python 
> /64bitdev/storage/sage-git_develop/sage/local/bin/sage-runtests --serial 
> --long --timeout=172800 --memlimit=3300 
> --stats_path=/home/volj/27/strogdon/.sage/timings2.json 
> --optional=dochtml,memlimit,mpir,python2,sage src/sage/combinat/tableau.py
> ==8525== Parent PID: 8495
> ==8525==
> ==8525== FATAL: can't open suppressions file 
> "/64bitdev/storage/sage-git_develop/sage/local/lib/valgrind/sage.supp"
>
> So, the *.supp files which. I believe,  are under 
> local/share/sage/ext/valgrind/ cannot be found.
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Should valgrind work when running doctests?

[Steven Trogdon]

Running ./sage --valgrind works with a resulting sage prompt. However,

./sage -t --long --valgrind src/sage/combinat/tableau.py

does not work. The ~/.sage/valgrind/sage-memcheck. file reads

==8525== Memcheck, a memory error detector
==8525== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==8525== Using Valgrind-3.14.0 and LibVEX; rerun with -h for copyright info
==8525== Command: python 
/64bitdev/storage/sage-git_develop/sage/local/bin/sage-runtests --serial 
--long --timeout=172800 --memlimit=3300 
--stats_path=/home/volj/27/strogdon/.sage/timings2.json 
--optional=dochtml,memlimit,mpir,python2,sage src/sage/combinat/tableau.py
==8525== Parent PID: 8495
==8525==
==8525== FATAL: can't open suppressions file 
"/64bitdev/storage/sage-git_develop/sage/local/lib/valgrind/sage.supp"

So, the *.supp files which. I believe,  are under 
local/share/sage/ext/valgrind/ cannot be found.

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] MemoryError when individually doctesting sage/combinat/tableau.py

[Steven Trogdon]

One more thing. If I remove

sage: StandardTableaux(50).cardinality()  # long time

then doctesting `tableary.py` with --long passes.

On Wednesday, February 13, 2019 at 12:27:03 PM UTC-6, Steven Trogdon wrote:
>
> Assuming this is the correct thing to do, starting at line 7740, the 
> following
>
>sage: def cardinality_using_hook_formula(n):
> : import gc
> : c = 0
> : for p in Partitions(n):
> : gc.collect()
> : c += StandardTableaux(p).cardinality()
> : return c
>
> gets rid of the MemoryError. This is on my gentoo prefix where the test 
> also fails. I have to rebuild sagelib to get results on vanilla. However, I 
> still see
>
> Process DocTestWorker-1:
> Traceback (most recent call last):
>   File 
> "/storage/strogdon/gentoo-rap/usr/lib64/python2.7/multiprocessing/process.py",
>  
> line 267, in _bootstrap
> self.run()
>   File 
> "/storage/strogdon/gentoo-rap/usr/lib64/python2.7/site-packages/sage/doctest/forker.py",
>  
> line 2139, in run
> task(self.options, self.outtmpfile, msgpipe, self.result_queue)
>   File 
> "/storage/strogdon/gentoo-rap/usr/lib64/python2.7/site-packages/sage/doctest/forker.py",
>  
> line 2498, in __call__
> result_queue.put(result, False)
>   File 
> "/storage/strogdon/gentoo-rap/usr/lib64/python2.7/multiprocessing/queues.py", 
> line 107, in put
> self._start_thread()
>   File 
> "/storage/strogdon/gentoo-rap/usr/lib64/python2.7/multiprocessing/queues.py", 
> line 195, in _start_thread
> self._thread.start()
>   File "/storage/strogdon/gentoo-rap/usr/lib64/python2.7/threading.py", 
> line 736, in start
> _start_new_thread(self.__bootstrap, ())
> error: can't start new thread
> Bad exit: 1
>
> It's not clear the origin of this since it appears all tests passed?
>
> 1650 tests in 281 items.
> 1650 passed and 0 failed.
> Test passed.
>
> On Wednesday, February 13, 2019 at 10:33:38 AM UTC-6, Travis Scrimshaw 
> wrote:
>>
>> My (complete) guess is that there are so many partitions of 50 (204226 to 
>> be precise) and in such a tight for loop that the garbage collector does 
>> not have enough time to actually collect the parents being created and 
>> discarded. Maybe also other stuff in tableau.py built up is causing a 
>> memory problem? Could you try inserting a `gc.collect()` in the for loop 
>> and seeing if the file passes after that?
>>
>> Best,
>> Travis
>>
>>
>> On Tuesday, February 12, 2019 at 7:52:09 AM UTC+10, Dima Pasechnik wrote:
>>>
>>> I see similar errors on Fedora 26 
>>>
>>> On Mon, Feb 11, 2019 at 9:19 PM Steven Trogdon  
>>> wrote: 
>>> > 
>>> > When individually doctesting tableau.py with vanilla 8.7.beta3 I see: 
>>> > 
>>> > sage -t --long src/sage/combinat/tableau.py  # Bad exit: 1 
>>> > 
>>> > The source is 
>>> > 
>>> > Trying (line 7735):StandardTableaux(50).cardinality()  # long time 
>>> > Expecting: 
>>> > 27886995605342342839104615869259776 
>>> > ** 
>>> > File "src/sage/combinat/tableau.py", line 7735, in 
>>> sage.combinat.tableau.StandardTableaux_size.cardinality 
>>> > Failed example: 
>>> > StandardTableaux(50).cardinality()  # long time 
>>> > Exception raised: 
>>> > Traceback (most recent call last): 
>>> >   File 
>>> "/64bitdev/storage/sage-git_develop/sage/local/lib/python2.7/site-packages/sage/doctest/forker.py",
>>>  
>>> line 671, in _run 
>>> > self.compile_and_execute(example, compiler, test.globs) 
>>> >   File 
>>> "/64bitdev/storage/sage-git_develop/sage/local/lib/python2.7/site-packages/sage/doctest/forker.py",
>>>  
>>> line 1095, in compile_and_execute 
>>> > exec(compiled, globs) 
>>> >   File ">> sage.combinat.tableau.StandardTableaux_size.cardinality[4]>", line 1, in 
>>>  
>>> > StandardTableaux(Integer(50)).cardinality()  # long time 
>>> >   File "sage/misc/lazy_import.pyx", line 354, in 
>>> sage.misc.lazy_import.LazyImport.__call__ 
>>> (build/cythonized/sage/misc/lazy_import.c:3683) 
>>> > return self.get_o

Re: [sage-devel] MemoryError when individually doctesting sage/combinat/tableau.py

[Steven Trogdon]

Assuming this is the correct thing to do, starting at line 7740, the 
following

   sage: def cardinality_using_hook_formula(n):
: import gc
: c = 0
: for p in Partitions(n):
: gc.collect()
: c += StandardTableaux(p).cardinality()
: return c

gets rid of the MemoryError. This is on my gentoo prefix where the test 
also fails. I have to rebuild sagelib to get results on vanilla. However, I 
still see

Process DocTestWorker-1:
Traceback (most recent call last):
  File 
"/storage/strogdon/gentoo-rap/usr/lib64/python2.7/multiprocessing/process.py", 
line 267, in _bootstrap
self.run()
  File 
"/storage/strogdon/gentoo-rap/usr/lib64/python2.7/site-packages/sage/doctest/forker.py",
 
line 2139, in run
task(self.options, self.outtmpfile, msgpipe, self.result_queue)
  File 
"/storage/strogdon/gentoo-rap/usr/lib64/python2.7/site-packages/sage/doctest/forker.py",
 
line 2498, in __call__
result_queue.put(result, False)
  File 
"/storage/strogdon/gentoo-rap/usr/lib64/python2.7/multiprocessing/queues.py", 
line 107, in put
self._start_thread()
  File 
"/storage/strogdon/gentoo-rap/usr/lib64/python2.7/multiprocessing/queues.py", 
line 195, in _start_thread
self._thread.start()
  File "/storage/strogdon/gentoo-rap/usr/lib64/python2.7/threading.py", 
line 736, in start
_start_new_thread(self.__bootstrap, ())
error: can't start new thread
Bad exit: 1

It's not clear the origin of this since it appears all tests passed?

1650 tests in 281 items.
1650 passed and 0 failed.
Test passed.

On Wednesday, February 13, 2019 at 10:33:38 AM UTC-6, Travis Scrimshaw 
wrote:
>
> My (complete) guess is that there are so many partitions of 50 (204226 to 
> be precise) and in such a tight for loop that the garbage collector does 
> not have enough time to actually collect the parents being created and 
> discarded. Maybe also other stuff in tableau.py built up is causing a 
> memory problem? Could you try inserting a `gc.collect()` in the for loop 
> and seeing if the file passes after that?
>
> Best,
> Travis
>
>
> On Tuesday, February 12, 2019 at 7:52:09 AM UTC+10, Dima Pasechnik wrote:
>>
>> I see similar errors on Fedora 26 
>>
>> On Mon, Feb 11, 2019 at 9:19 PM Steven Trogdon  
>> wrote: 
>> > 
>> > When individually doctesting tableau.py with vanilla 8.7.beta3 I see: 
>> > 
>> > sage -t --long src/sage/combinat/tableau.py  # Bad exit: 1 
>> > 
>> > The source is 
>> > 
>> > Trying (line 7735):StandardTableaux(50).cardinality()  # long time 
>> > Expecting: 
>> > 27886995605342342839104615869259776 
>> > ** 
>> > File "src/sage/combinat/tableau.py", line 7735, in 
>> sage.combinat.tableau.StandardTableaux_size.cardinality 
>> > Failed example: 
>> > StandardTableaux(50).cardinality()  # long time 
>> > Exception raised: 
>> > Traceback (most recent call last): 
>> >   File 
>> "/64bitdev/storage/sage-git_develop/sage/local/lib/python2.7/site-packages/sage/doctest/forker.py",
>>  
>> line 671, in _run 
>> > self.compile_and_execute(example, compiler, test.globs) 
>> >   File 
>> "/64bitdev/storage/sage-git_develop/sage/local/lib/python2.7/site-packages/sage/doctest/forker.py",
>>  
>> line 1095, in compile_and_execute 
>> > exec(compiled, globs) 
>> >   File "> sage.combinat.tableau.StandardTableaux_size.cardinality[4]>", line 1, in 
>>  
>> > StandardTableaux(Integer(50)).cardinality()  # long time 
>> >   File "sage/misc/lazy_import.pyx", line 354, in 
>> sage.misc.lazy_import.LazyImport.__call__ 
>> (build/cythonized/sage/misc/lazy_import.c:3683) 
>> > return self.get_object()(*args, **kwds) 
>> >   File "sage/misc/classcall_metaclass.pyx", line 330, in 
>> sage.misc.classcall_metaclass.ClasscallMetaclass.__call__ 
>> (build/cythonized/sage/misc/classcall_metaclass.c:1700) 
>> > return cls.classcall(cls, *args, **kwds) 
>> >   File 
>> "/64bitdev/storage/sage-git_develop/sage/local/lib/python2.7/site-packages/sage/combinat/tableau.py",
>>  
>> line 7568, in __classcall_private__ 
>> > return StandardTableaux_size(n) 
>> >   File "sage/misc/classcall_metaclass.pyx", line 330, in 
>> sage.misc.classcall_metaclass.ClasscallMetacl

[sage-devel] MemoryError when individually doctesting sage/combinat/tableau.py

[Steven Trogdon]

When individually doctesting tableau.py with vanilla 8.7.beta3 I see:

sage -t --long src/sage/combinat/tableau.py  # Bad exit: 1

The source is

Trying (line 7735):StandardTableaux(50).cardinality()  # long time
Expecting:
27886995605342342839104615869259776
**
File "src/sage/combinat/tableau.py", line 7735, in 
sage.combinat.tableau.StandardTableaux_size.cardinality
Failed example:
StandardTableaux(50).cardinality()  # long time
Exception raised:
Traceback (most recent call last):
  File 
"/64bitdev/storage/sage-git_develop/sage/local/lib/python2.7/site-packages/sage/doctest/forker.py",
 
line 671, in _run
self.compile_and_execute(example, compiler, test.globs)
  File 
"/64bitdev/storage/sage-git_develop/sage/local/lib/python2.7/site-packages/sage/doctest/forker.py",
 
line 1095, in compile_and_execute
exec(compiled, globs)
  File "", line 1, in 

StandardTableaux(Integer(50)).cardinality()  # long time
  File "sage/misc/lazy_import.pyx", line 354, in 
sage.misc.lazy_import.LazyImport.__call__ 
(build/cythonized/sage/misc/lazy_import.c:3683)
return self.get_object()(*args, **kwds)
  File "sage/misc/classcall_metaclass.pyx", line 330, in 
sage.misc.classcall_metaclass.ClasscallMetaclass.__call__ 
(build/cythonized/sage/misc/classcall_metaclass.c:1700)
return cls.classcall(cls, *args, **kwds)
  File 
"/64bitdev/storage/sage-git_develop/sage/local/lib/python2.7/site-packages/sage/combinat/tableau.py",
 
line 7568, in __classcall_private__
return StandardTableaux_size(n)
  File "sage/misc/classcall_metaclass.pyx", line 330, in 
sage.misc.classcall_metaclass.ClasscallMetaclass.__call__ 
(build/cythonized/sage/misc/classcall_metaclass.c:1700)
return cls.classcall(cls, *args, **kwds)
  File "sage/misc/cachefunc.pyx", line 1005, in 
sage.misc.cachefunc.CachedFunction.__call__ 
(build/cythonized/sage/misc/cachefunc.c:6067)
w = self.f(*args, **kwds)
  File 
"/64bitdev/storage/sage-git_develop/sage/local/lib/python2.7/site-packages/sage/structure/unique_representation.py",
 
line 1027, in __classcall__
instance = typecall(cls, *args, **options)
  File "sage/misc/classcall_metaclass.pyx", line 497, in 
sage.misc.classcall_metaclass.typecall 
(build/cythonized/sage/misc/classcall_metaclass.c:2150)
return (type).tp_call(cls, args, kwds)
  File 
"/64bitdev/storage/sage-git_develop/sage/local/lib/python2.7/site-packages/sage/combinat/tableau.py",
 
line 7677, in __init__
facade=True, keepkey=False)
  File 
"/64bitdev/storage/sage-git_develop/sage/local/lib/python2.7/site-packages/sage/sets/disjoint_union_enumerated_sets.py",
 
line 288, in __init__
self._facade_for = tuple(family)
  File 
"/64bitdev/storage/sage-git_develop/sage/local/lib/python2.7/site-packages/sage/sets/family.py",
 
line 1061, in __iter__
for i in self.set:
  File 
"/64bitdev/storage/sage-git_develop/sage/local/lib/python2.7/site-packages/sage/combinat/partition.py",
 
line 6698, in __iter__
yield self.element_class(self, p)
  File "sage/misc/classcall_metaclass.pyx", line 333, in 
sage.misc.classcall_metaclass.ClasscallMetaclass.__call__ 
(build/cythonized/sage/misc/classcall_metaclass.c:1725)
return (type).tp_call(cls, args, kwds)
MemoryError
Trying (line 7740):def cardinality_using_hook_formula(n):
c = 0
for p in Partitions(n):
c += StandardTableaux(p).cardinality()
return c
Expecting nothing
ok [0.00 s]
Trying (line 7745):all(cardinality_using_hook_formula(i) == 
StandardTableaux(i).cardinality() for i in range(10))
Expecting:
True
Process DocTestWorker-1:
Traceback (most recent call last):
  File 
"/64bitdev/storage/sage-git_develop/sage/local/lib/python2.7/multiprocessing/process.py",
 
line 267, in _bootstrap
self.run()
  File 
"/64bitdev/storage/sage-git_develop/sage/local/lib/python2.7/site-packages/sage/doctest/forker.py",
 
line 2139, in run
task(self.options, self.outtmpfile, msgpipe, self.result_queue)
  File 
"/64bitdev/storage/sage-git_develop/sage/local/lib/python2.7/site-packages/sage/doctest/forker.py",
 
line 2498, in __call__
result_queue.put(result, False)
  File 
"/64bitdev/storage/sage-git_develop/sage/local/lib/python2.7/multiprocessing/queues.py",
 
line 107, in put
self._start_thread()
  File 
"/64bitdev/storage/sage-git_develop/sage/local/lib/python2.7/multiprocessing/queues.py",
 
line 195, in _start_thread
self._thread.start()
  File 
"/64bitdev/storage/sage-git_develop/sage/local/lib/python2.7/threading.py", 
line 736, in start
_start_new_thread(self.__bootstrap, ())
error: can't start new thread
Bad exit: 1
**

Usually there is no failure if the doctest is run again. I've been able to 
replicate this by rebuilding s

[sage-devel] Re: Sage 8.4 does not compile / CentOS 6.10

[Steven Trogdon]

This looks suspiciously like https://github.com/wbhart/mpir/issues/217 
although on OSX instead of CentOS.

On Monday, November 5, 2018 at 4:27:29 PM UTC-6, Daniel Ouimet wrote:
>
> Hi,
>
> on a Linux CentOS 6.10, I have an error compiling: 
> [mpir-3.0.0-644faf502c56f97d9accd301965fc57d6ec70868.p0] tmp-mul_1.s: 
> Assembler messages:
> [mpir-3.0.0-644faf502c56f97d9accd301965fc57d6ec70868.p0] tmp-mul_1.s:94: 
> Error: no such instruction: `mulx (%rsi),%r9,%r8'
> [mpir-3.0.0-644faf502c56f97d9accd301965fc57d6ec70868.p0] tmp-mul_1.s:95: 
> Error: no such instruction: `mulx 8(%rsi),%r11,%r10'
> [mpir-3.0.0-644faf502c56f97d9accd301965fc57d6ec70868.p0] tmp-mul_1.s:96: 
> Error: no such instruction: `mulx 16(%rsi),%rcx,%r12'
> [mpir-3.0.0-644faf502c56f97d9accd301965fc57d6ec70868.p0] tmp-mul_1.s:100: 
> Error: no such instruction: `mulx (%rsi),%rcx,%r12'
> [mpir-3.0.0-644faf502c56f97d9accd301965fc57d6ec70868.p0] tmp-mul_1.s:101: 
> Error: no such instruction: `mulx 8(%rsi),%rbx,%rax'
> [mpir-3.0.0-644faf502c56f97d9accd301965fc57d6ec70868.p0] tmp-mul_1.s:105: 
> Error: no such instruction: `mulx 16(%rsi),%r9,%r8'
> [mpir-3.0.0-644faf502c56f97d9accd301965fc57d6ec70868.p0] tmp-mul_1.s:113: 
> Error: no such instruction: `mulx (%rsi),%rbx,%rax'
> [mpir-3.0.0-644faf502c56f97d9accd301965fc57d6ec70868.p0] tmp-mul_1.s:117: 
> Error: no such instruction: `mulx 8(%rsi),%r9,%r8'
> [mpir-3.0.0-644faf502c56f97d9accd301965fc57d6ec70868.p0] tmp-mul_1.s:121: 
> Error: no such instruction: `mulx (%rsi),%r11,%r10'
> [mpir-3.0.0-644faf502c56f97d9accd301965fc57d6ec70868.p0] tmp-mul_1.s:122: 
> Error: no such instruction: `mulx 8(%rsi),%rcx,%r12'
> [mpir-3.0.0-644faf502c56f97d9accd301965fc57d6ec70868.p0] tmp-mul_1.s:123: 
> Error: no such instruction: `mulx 16(%rsi),%rbx,%rax'
> [mpir-3.0.0-644faf502c56f97d9accd301965fc57d6ec70868.p0] tmp-mul_1.s:134: 
> Error: no such instruction: `mulx (%rsi),%r9,%r8'
> [mpir-3.0.0-644faf502c56f97d9accd301965fc57d6ec70868.p0] tmp-mul_1.s:139: 
> Error: no such instruction: `mulx 8(%rsi),%r11,%r10'
> [mpir-3.0.0-644faf502c56f97d9accd301965fc57d6ec70868.p0] tmp-mul_1.s:141: 
> Error: no such instruction: `mulx 16(%rsi),%rcx,%r12'
> [mpir-3.0.0-644faf502c56f97d9accd301965fc57d6ec70868.p0] tmp-mul_1.s:143: 
> Error: no such instruction: `mulx 24(%rsi),%rbx,%rax'
> [mpir-3.0.0-644faf502c56f97d9accd301965fc57d6ec70868.p0] make[5]: *** 
> [mul_1.lo] Error 1
> with this version of gcc:
> gcc version 4.4.7 20120313 (Red Hat 4.4.7-23) (GCC)
>
> In attachment, the log file.
>
> Is there a missing piece that I don't have?  anybody wants to take a shot 
> at a solution?
>
> Thanks,
> Daniel
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Can't compile 8.4.beta3

[Steven Trogdon]

The log file would be good. Though not on a Mac I had a "similar" situation 
where, for some reasion, local/bin/pip was missing. 
See https://groups.google.com/d/msg/sage-release/XUYlh2DHP9E/qIZEf8qRAAAJ

On Thursday, September 6, 2018 at 1:21:42 AM UTC-5, Andrew wrote:
>
> I'm not able compile any of the 8.4 betas on both my laptop and a desktop 
> machine. I had no problem with 8.3 betas. 
>
> Quite possibly I am doing, or have done, something stupid but I don't 
> think that I have changed anything from 8.3. I am running
>
> ProductName:Mac OS X
> ProductVersion:10.13.6
> BuildVersion:17G65
> Xcode 9.4.1
> Build version 9F2000
>
> The full log file is too large to attach so I have put in on install.log 
> , but the last message 
> is
>
> ***
> Error building Sage.
>
> The following package(s) may have failed to build (not necessarily
> during this run of 'make all-start'):
>
> * package: pip-18.0
>   log file: /usr/local/src/sage/logs/pkgs/pip-18.0.log
>   build directory: /usr/local/src/sage/local/var/tmp/sage/build/pip-18.0
>
> 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.
>
> Can anyone see what I am doing wrong?
>
> Andrew
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: typesetting of math formulas in (certain) docstrings is broken

[Steven Trogdon]

OK, so my log files indicated that mathjax-2.6.1 had been successfully 
installed, but upon looking at what should have been installed it was clear 
that the install was not correct.

After

   ./sage -f mathjax

and rebuilding the html-docs the math (latex) typsetting is now what it 
should be. Apparently, this has been this way for some time? Perhaps 
someone else can get some mileage from this.

On Monday, January 8, 2018 at 11:33:04 AM UTC-6, Steven Trogdon wrote:
>
> The html code for plot.html appears to be correct. In places where `(0,1)` 
> is typeset there is \((0,1)\). However at the 
> beginning of plot.html there is
>
> 
>  src="../../_static/underscore.js">
>  src="../../_static/doctools.js">
>  src="../../_static/MathJax.js?config=TeX-AMS_HTML-full,../mathjax_sage.js">
>  src="../../_static/MathJax.js?config=TeX-AMS_HTML-full,../mathjax_sage.js">
> 
> 
> 
> 
> 
>  />
> 
>  type="text/javascript">
>
> All links are good except
>  src="../../_static/MathJax.js?config=TeX-AMS_HTML-full,../mathjax_sage.js">
>
> which is stale (file not found). So the MathJax stuff is not being loaded? 
> So what could be causing this?
>
>
> On Sunday, January 7, 2018 at 11:52:41 PM UTC-6, Steven Trogdon wrote:
>>
>> This appears to be since version 8.1. In src/sage/plot/plot.py there is
>>
>> .. warning::
>>
>> If ``plotjoined`` is ``False`` then the axis that is in log scale
>> must have all points strictly positive. For instance, the 
>> following
>> plot will show no points in the figure since the points in the
>> horizontal axis starts from `(0,1)`. Further, matplotlib will 
>> display
>> a user warning.
>>
>> ::
>>
>> In the html docs, the `(0,1)` now appears literally as \((0,1)\), i.e. no 
>> math typesetting.
>>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: typesetting of math formulas in (certain) docstrings is broken

[Steven Trogdon]

The html code for plot.html appears to be correct. In places where `(0,1)` 
is typeset there is \((0,1)\). However at the 
beginning of plot.html there is















All links are good except


which is stale (file not found). So the MathJax stuff is not being loaded? 
So what could be causing this?


On Sunday, January 7, 2018 at 11:52:41 PM UTC-6, Steven Trogdon wrote:
>
> This appears to be since version 8.1. In src/sage/plot/plot.py there is
>
> .. warning::
>
> If ``plotjoined`` is ``False`` then the axis that is in log scale
> must have all points strictly positive. For instance, the following
> plot will show no points in the figure since the points in the
> horizontal axis starts from `(0,1)`. Further, matplotlib will 
> display
> a user warning.
>
> ::
>
> In the html docs, the `(0,1)` now appears literally as \((0,1)\), i.e. no 
> math typesetting.
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: typesetting of math formulas in (certain) docstrings is broken

[Steven Trogdon]

So after a  make doc-clean && make, I have

<https://lh3.googleusercontent.com/-SlsyKr5lOv8/WlOR2Ga2n_I/AAg/1RJpCalxy7Yj1NM7e1zlY35NUeqqVbkQgCLcBGAs/s1600/inline_math.png>
So something is doing this.

On Monday, January 8, 2018 at 4:06:45 AM UTC-6, Eric Gourgoulhon wrote:
>
> Hi Steven,
>
> Le lundi 8 janvier 2018 06:52:41 UTC+1, Steven Trogdon a écrit :
>
>>
>> In the html docs, the `(0,1)` now appears literally as \((0,1)\), i.e. no 
>> math typesetting.
>>
>
> I don't see the issue: (0,1) in this warning appears LaTeX-typeset in the 
> 8.1. documentation posted at
> http://doc.sagemath.org/html/en/reference/plotting/sage/plot/plot.html
> On my computer, it is also OK for Sage 8.2.beta0 and 8.2.beta2 and I see 
> no difference with Sage 7.6.
>
> Best regards,
>
> Eric.
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] typesetting of math formulas in (certain) docstrings is broken

[Steven Trogdon]

This appears to be since version 8.1. In src/sage/plot/plot.py there is

.. warning::

If ``plotjoined`` is ``False`` then the axis that is in log scale
must have all points strictly positive. For instance, the following
plot will show no points in the figure since the points in the
horizontal axis starts from `(0,1)`. Further, matplotlib will 
display
a user warning.

::

In the html docs, the `(0,1)` now appears literally as \((0,1)\), i.e. no 
math typesetting.

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Keyboard bindings

[Steven Trogdon]

Well Gentoo (my OS) patches ncurses to include rxvt-unicode term types. So 
perhaps that's a partial explanation?

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Keyboard bindings

[Steven Trogdon]

In addition to python, these also have this same odd behavior

./sage -gap
./sage -gp
./sage -R
./sage -singular
./sage -sqlite3

The other "external" programs do not have the issue.

On Tuesday, November 21, 2017 at 10:10:27 AM UTC-6, Steven Trogdon wrote:
>
> I have 8.1.rc2 installed and my default terminal emulator
>
> echo $TERM
> rxvt-unicode-256color
>
> The  key, the history keys (up/down arrows) as well as the 
> (left/right arrows) are messed up when using the Sage built python.
>
> ./sage -python
> Python 2.7.14 (default, Nov 16 2017, 09:21:42) 
> [GCC 5.4.0] on linux2
> Type "help", "copyright", "credits" or "license" for more information.
> >>> sss
>
> Pressing  3 times erases the 'sss' but the cursor moves 3 
> spaces to the right and then the (left/right) arrow keys don't function. 
> Everything works as it should from the Sage prompt and my system python 
> works as expected. If I unset TERM or work in a normal 'xterm' the Sage 
> python functions as expected. The issue seems to be with how the Sage built 
> python interacts with my default terminal emulator.
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Keyboard bindings

[Steven Trogdon]

I have 8.1.rc2 installed and my default terminal emulator

echo $TERM
rxvt-unicode-256color

The  key, the history keys (up/down arrows) as well as the 
(left/right arrows) are messed up when using the Sage built python.

./sage -python
Python 2.7.14 (default, Nov 16 2017, 09:21:42) 
[GCC 5.4.0] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> sss

Pressing  3 times erases the 'sss' but the cursor moves 3 spaces 
to the right and then the (left/right) arrow keys don't function. 
Everything works as it should from the Sage prompt and my system python 
works as expected. If I unset TERM or work in a normal 'xterm' the Sage 
python functions as expected. The issue seems to be with how the Sage built 
python interacts with my default terminal emulator.

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: Make OpenBLAS Error

[Steven Trogdon]

>From a bash shell where you build Sage:

export OPENBLAS_CONFIGURE="TARGET=ATOM" MAKE="make -j5 -l3.5"

should set the important variables. This is the MAKE I use for a very, very 
old 4 core machine. The OPENBLAS_CONFIGURE variable is alluded to 
in build/pkgs/openblas/spkg-check but I find it no where else. Somewhere in 
the openblas code there is a listing of supported architectures. I don't 
know how many ATOM processor variations there are? And getting the openblas 
code to work properly is probably an upstream issue.

On Tuesday, April 11, 2017 at 2:23:42 PM UTC-5, Ackbach wrote:
>
> All right! Sage 7.6 compiled correctly, so far as I know. I haven't run 
> the tests, but it opens into a notebook in Firefox, and correctly computes
>
> integrate(e^(-x^2),x,-infinity,infinity)
>
> Is there a way to combine the OPENBLAS_CONFIGURE command with the -j4 
> option for using multiple cores to compile? It did take a VERY long time to 
> compile - I think it was about 8 hours. 
>
> In any case, targeting an ATOM processor seems like a common-enough 
> occurrence that it deserves a mention in the manual, if it's not there 
> already (I haven't looked, and please don't shoot me).
>
> Thanks much!
>
> Cheers.
>
> On Tuesday, April 11, 2017 at 6:50:10 AM UTC-4, Ackbach wrote:
>>
>> 7.5.1 failed to build. Looks like the same error as before. I'll try 
>> Steven's linked suggestion with 7.6, and see if that flies. 
>>
>> Thanks for all your help, by the way! 
>>
>> One suggestion: if the OPENBLAS_CONFIGURE="TARGET=ATOM" make command 
>> builds everything correctly, then maybe the next version of Sage could 
>> automate processor detection and do the right switches on that basis? 
>>
>> Cheers.
>>
>> On Tuesday, April 11, 2017 at 12:45:44 AM UTC-4, Steven Trogdon wrote:
>>>
>>> It is curious that 7.5.1 would build but not 7.6. You might get some 
>>> mileage with
>>>
>>> OPENBLAS_CONFIGURE="TARGET=ATOM" make 
>>>
>>> See this thread:
>>>
>>> https://groups.google.com/forum/#!topic/sage-release/3QJoAgg9bgo
>>>
>>> On Monday, April 10, 2017 at 8:00:51 PM UTC-5, Ackbach wrote:
>>>>
>>>> I'm afraid I don't have that data. I will say I've never been able to 
>>>> compile Sage 7.6 the first time. I have definitely been able to compile 
>>>> 7.5.1 and earlier the first time, though sometimes there are still errors. 
>>>> I can try to compile 7.5.1 on this machine and get back to you how it 
>>>> works.
>>>>
>>>> On Monday, April 10, 2017 at 4:17:38 PM UTC-4, François wrote:
>>>>>
>>>>> Did it start happening with openblas 0.2.19 or did it suddenly happen 
>>>>> one release build openblas 0.2.19 successfully and the next didn’t? 
>>>>> I suspect it is a CPU detection problem, we have seen similar logs 
>>>>> before on atom chips. 
>>>>>
>>>>> François 
>>>>>
>>>>> > On 11/04/2017, at 07:45, Ackbach  wrote: 
>>>>> > 
>>>>> > Having issues building the same package. Only I get a different log 
>>>>> file. I always prefer building Sage from scratch for performance, but 
>>>>> have 
>>>>> lately been having trouble doing so, as Sage keeps failing to build. 
>>>>> Background: 
>>>>> > 
>>>>> > OS: Debian 8.7, 64-bit. 
>>>>> > Sage Version: 7.6. 
>>>>> > HW: Lenovo ThinkPad 11e, 120GB SSD, 8GB RAM, Intel Celeron N2940, 
>>>>> with 4 cpu cores (as evidenced by the cat /proc/cpuinfo command). 
>>>>> > 
>>>>> > I follow the instructions for [installing from source](
>>>>> http://doc.sagemath.org/html/en/installation/source.html), and I 
>>>>> execute the MAKE='make -j4' make command. The compile gets quite a ways 
>>>>> into the compile. It finishes compiling maxima, in fact, and then I get 
>>>>> the 
>>>>> following error message: 
>>>>> > 
>>>>> > Error building Sage. 
>>>>> > 
>>>>> > The following package(s) may have failed to build (not necessarily 
>>>>> during this run of 'make all'): 
>>>>> > 
>>>>> > * package: openblas-0.2.19.p0 
>>>>> >   log file: 
>>>>> /home/akeister/Downloads/sage-7.6/logs/pkgs/openbla

Re: [sage-devel] Re: Make OpenBLAS Error

[Steven Trogdon]

It is curious that 7.5.1 would build but not 7.6. You might get some 
mileage with

OPENBLAS_CONFIGURE="TARGET=ATOM" make 

See this thread:

https://groups.google.com/forum/#!topic/sage-release/3QJoAgg9bgo

On Monday, April 10, 2017 at 8:00:51 PM UTC-5, Ackbach wrote:
>
> I'm afraid I don't have that data. I will say I've never been able to 
> compile Sage 7.6 the first time. I have definitely been able to compile 
> 7.5.1 and earlier the first time, though sometimes there are still errors. 
> I can try to compile 7.5.1 on this machine and get back to you how it works.
>
> On Monday, April 10, 2017 at 4:17:38 PM UTC-4, François wrote:
>>
>> Did it start happening with openblas 0.2.19 or did it suddenly happen 
>> one release build openblas 0.2.19 successfully and the next didn’t? 
>> I suspect it is a CPU detection problem, we have seen similar logs 
>> before on atom chips. 
>>
>> François 
>>
>> > On 11/04/2017, at 07:45, Ackbach  wrote: 
>> > 
>> > Having issues building the same package. Only I get a different log 
>> file. I always prefer building Sage from scratch for performance, but have 
>> lately been having trouble doing so, as Sage keeps failing to build. 
>> Background: 
>> > 
>> > OS: Debian 8.7, 64-bit. 
>> > Sage Version: 7.6. 
>> > HW: Lenovo ThinkPad 11e, 120GB SSD, 8GB RAM, Intel Celeron N2940, with 
>> 4 cpu cores (as evidenced by the cat /proc/cpuinfo command). 
>> > 
>> > I follow the instructions for [installing from source](
>> http://doc.sagemath.org/html/en/installation/source.html), and I execute 
>> the MAKE='make -j4' make command. The compile gets quite a ways into the 
>> compile. It finishes compiling maxima, in fact, and then I get the 
>> following error message: 
>> > 
>> > Error building Sage. 
>> > 
>> > The following package(s) may have failed to build (not necessarily 
>> during this run of 'make all'): 
>> > 
>> > * package: openblas-0.2.19.p0 
>> >   log file: 
>> /home/akeister/Downloads/sage-7.6/logs/pkgs/openblas-0.2.19.p0.log 
>> >   build directory: 
>> /home/akeister/Downloads/sage-7.6/local/var/tmp/sage/build/openblas-0.2.19.p0
>>  
>>
>> > 
>> > I have attached the indicated log file, where it says to contact this 
>> group. You can see that the issue is different from the OP, but it's still 
>> a problem compiling that package. 
>> > 
>> > Ideas? 
>> > 
>> > Thanks for your time! 
>> > 
>> > Cheers, 
>> > Adrian 
>> > 
>> > On Wednesday, October 12, 2016 at 12:43:20 PM UTC-4, Ethan Petersen 
>> wrote: 
>> > Hello all, 
>> > 
>> > I'm building sage on a Lenovo Thinkpad W540 with Ubuntu 16.04, and 
>> there was an "Error building OpenBLAS"/"Error installing package 
>> openblas-0.2.19" with a suggestion to email this google group with the 
>> attached log file. If anyone has ideas on solving this issue, please let me 
>> know! 
>> > 
>> > Thanks, 
>> > 
>> > Ethan 
>> > 
>> > -- 
>> > 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+...@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-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.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: fail to build openblas

[Steven Trogdon]

These are the supported X86/X86_64

a)Intel CPU:
P2
KATMAI
COPPERMINE
NORTHWOOD
PRESCOTT
BANIAS
YONAH
CORE2
PENRYN
DUNNINGTON
NEHALEM
SANDYBRIDGE
HASWELL
ATOM

I guess you could try 'make TARGET=ATOM'. As a last resort 
'./configure --with-blas=atlas && make'. But I wouldn't do this until all 
the TARGETS had been exhausted. Building atlas may take for ever. See  
https://trac.sagemath.org/ticket/21561#comment:5 
 for amd archs that have problems.

On Thursday, February 23, 2017 at 10:39:09 PM UTC-6, Matthew Rennekamp 
wrote:
>
> I downloaded 7.5.1 from source 3x, (2x were git cloning and once from 
> files.sagemath.org), and  failed. I can interpret 
> Makefile:123: *** OpenBLAS: Detecting CPU failed. Please set TARGET 
> explicitly, e.g. make TARGET=your_cpu_target. Please read README for the 
> detail..  Stop.
> , but then I also tried  +  and the 
> build still failed.
>
> My system is running Fedora 25, on my HP laptop w/ an Intel Celeron N2830. 
> (
> http://ark.intel.com/products/81071/Intel-Celeron-Processor-N2830-1M-Cache-up-to-2_41-GHz
> ).
>
> I'll try the sage-7.5.1-Fedora_24-x86_64 binary to see if that works 
> though I could simply use the sagemath package in the Fedora repos.
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Build failed on OpenSuSE 42.2 64 bit linux

[Steven Trogdon]

This look like

https://trac.sagemath.org/ticket/21811

On Tuesday, February 21, 2017 at 12:23:36 PM UTC-6, a-go...@gmx.de wrote:
>
> Hi,
>
> I´ve just downloaded sage 7.5.1 and tried to build it. As it said in the 
> readme, I´ve just typed "make".
>
> The package ecl-16.1.2.p2 didn´t build.
>
> I´d like to attach the log file, but I don´t know exactly what the 
> relevant part is.
>
> This is my guess:
>
> dpp: 
> /home/ag/Downloads/sage-7.5.1/sage-7.5.1/local/var/tmp/sage/build/ecl-16.1.2.p2/src/src/c/ffi.d
>  
> -> ffi.o.c
> gcc 
> -DECLDIR="\"/home/ag/Downloads/sage-7.5.1/sage-7.5.1/local/lib/ecl-16.1.2\"" 
> -I. 
> -I/home/ag/Downloads/sage-7.5.1/sage-7.5.1/local/var/tmp/sage/build/ecl-16.1.2.p2/src/build
>  
> -I/home/ag/Downloads/sage-7.5.1/sage-7.5.1/local/var/tmp/sage/build/ecl-16.1.2.p2/src/src/c
>  
> -I../ecl/gc -DECL_API -DECL_NO_LEGACY   
> -I/home/ag/Downloads/sage-7.5.1/sage-7.5.1/local/include  -D_GNU_SOURCE 
> -D_FILE_OFFSET_BITS=64 -g -O2  -fPIC -Dlinux -c -o ffi.o ffi.o.c
> /home/ag/Downloads/sage-7.5.1/sage-7.5.1/local/var/tmp/sage/build/ecl-16.1.2.p2/src/src/c/ffi.d:148:34:
>  
> error: 'FFI_SYSV' undeclared here (not in a function)
> Makefile:85: recipe for target 'ffi.o' failed
> make[5]: *** [ffi.o] Error 1
> make[5]: Leaving directory 
> '/home/ag/Downloads/sage-7.5.1/sage-7.5.1/local/var/tmp/sage/build/ecl-16.1.2.p2/src/build/c'
> Makefile:119: recipe for target 'libeclmin.a' failed
> make[4]: *** [libeclmin.a] Error 2
> make[4]: Leaving directory 
> '/home/ag/Downloads/sage-7.5.1/sage-7.5.1/local/var/tmp/sage/build/ecl-16.1.2.p2/src/build'
> Makefile:70: recipe for target 'all' failed
> make[3]: *** [all] Error 2
> make[3]: Leaving directory 
> '/home/ag/Downloads/sage-7.5.1/sage-7.5.1/local/var/tmp/sage/build/ecl-16.1.2.p2/src'
> Error - Failed to build ECL ... exiting
>
> real 1m19.764s
> user 1m0.388s
> sys 0m10.256s
> 
> Error installing package ecl-16.1.2.p2
> 
> Please email sage-devel (http://groups.google.com/group/sage-devel)
> explaining the problem and including the relevant part of the log file
>   /home/ag/Downloads/sage-7.5.1/sage-7.5.1/logs/pkgs/ecl-16.1.2.p2.log
> Describe your computer, operating system, etc.
> If you want to try to fix the problem yourself, *don't* just cd to
> /home/ag/Downloads/sage-7.5.1/sage-7.5.1/local/var/tmp/sage/build/ecl-16.1.2.p2
>  
> and type 'make' or whatever is appropriate.
> Instead, the following commands setup all environment variables
> correctly and load a subshell for you to debug the error:
>   (cd 
> '/home/ag/Downloads/sage-7.5.1/sage-7.5.1/local/var/tmp/sage/build/ecl-16.1.2.p2'
>  
> && '/home/ag/Downloads/sage-7.5.1/sage-7.5.1/sage' --sh)
> When you are done debugging, you can type "exit" to leave the subshell.
> 
>
>
> E-Mail I did, I hope someone can shed some light on this!
>
> Regards,
>
> Andreas
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Make OpenBLAS Error

[Steven Trogdon]

Sorry, I'm slow. See https://trac.sagemath.org/ticket/21689

On Wednesday, October 12, 2016 at 12:40:57 PM UTC-5, Steven Trogdon wrote:
>
> It looks like you are missing libgfortran3 libraries or at least they 
> could not be found. Perhaps
>
> apt-get install libgfortran3
>
> but there could be something else that's the problem.
>
> On Wednesday, October 12, 2016 at 11:43:20 AM UTC-5, Ethan Petersen wrote:
>>
>> Hello all,
>>
>> I'm building sage on a Lenovo Thinkpad W540 with Ubuntu 16.04, and there 
>> was an "Error building OpenBLAS"/"Error installing package openblas-0.2.19" 
>> with a suggestion to email this google group with the attached log file. If 
>> anyone has ideas on solving this issue, please let me know!
>>
>> Thanks,
>>
>> Ethan
>>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Make OpenBLAS Error

[Steven Trogdon]

It looks like you are missing libgfortran3 libraries or at least they could 
not be found. Perhaps

apt-get install libgfortran3

but there could be something else that's the problem.

On Wednesday, October 12, 2016 at 11:43:20 AM UTC-5, Ethan Petersen wrote:
>
> Hello all,
>
> I'm building sage on a Lenovo Thinkpad W540 with Ubuntu 16.04, and there 
> was an "Error building OpenBLAS"/"Error installing package openblas-0.2.19" 
> with a suggestion to email this google group with the attached log file. If 
> anyone has ideas on solving this issue, please let me know!
>
> Thanks,
>
> Ethan
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] sagenb and pycrypto

[Steven Trogdon]

I have 7.0.beta3 installed so at some point in going from 6.10 -> 7.0.x I 
had to 

make distclean && make

However, in starting the notebook the warning from 
local/lib/python2.7/site-packages/Crypto/Util/number.py
line 57 would appear:

# You need libgmp v5 or later to get mpz_powm_sec.  Warn if it's not 
available.
if _fastmath is not None and not _fastmath.HAVE_DECL_MPZ_POWM_SEC:
_warn("Not using mpz_powm_sec.  You should rebuild using libgmp >= 5 to 
avoid timing attack vulnerability.", PowmInsecureWarning)

Well gmp was not the issue. After rebuilding pycrypto I no longer have the 
warning. I can't display the warning since rebuilding pycrypto fixed 
things, but is there a missing dependency somewhere or did I just miss 
something?

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Problem generating html docs [Sage-on-Gentoo]

[Steven Trogdon]

Plesse see http://trac.sagemath.org/ticket/16715#comment:2.

On Friday, July 25, 2014 9:51:47 AM UTC-5, Volker Braun wrote:
>
> The nonbreaking space tend to creep in when copy-pasting from a web 
> browser. Feel free to open a ticket and remove them.
>
>
>
>
> On Friday, July 25, 2014 10:43:08 AM UTC-4, Steven Trogdon wrote:
>>
>> The following error is present in generating the html docs for 
>> sage-on-gentoo:
>>
>> OSError: [tutorial ] 
>> /storage/strogdon/gentoo-redlizard/var/tmp/portage/sci-mathematics/sage-doc--r1/work/sage-/src/doc/fr/tutorial/tour_coercion.rst:149:
>>  
>> WARNING: Inline literal start-string without end-string.
>>
>> and
>>
>> $ rst2html.py src/doc/fr/tutorial/tour_coercion.rst > /dev/null
>> src/doc/fr/tutorial/tour_coercion.rst:149: (WARNING/2) Inline literal 
>> start-string without end-string
>>
>> We are using docutils-0.11. Everything seems OK with the docutils that's 
>> shipped with vanilla Sage. Line 149 of tour_coercion.rst begins with
>>
>> Le type ``RingElement`` ne correspond pas parfaitement à la notion
>> mathématique d'élément d'anneau. Par exemple, bien que les matrices 
>> carrées
>> appartiennent à un anneau, elles ne sont pas de type ``RingElement`` :
>>
>> The problem seems to be with the second RingElement. Between the `` and : 
>> there is a hidden character or perhaps composition of characters. An octal 
>> dump (od -c) of the file reveals the character(s)
>>
>> 0013400   `   `   R   i   n   g   E   l   e   m   e   n   t   `   `
>> 0013420 302 240   :  \n  \n   :   :  \n  \n   s   a   g
>>
>> The 302 is octal for a "circumflex capital A" and 240 is for a 
>> "nonbreaking space". Apparently, docutils-0.11 doesn't like this. Are there 
>> any ideas of how these characters made their way into tour_coercion.rst? If 
>> Sage upgrades to docutils-0.11 I'm reasonably sure the error will be 
>> present.
>>
>>

-- 
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 http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Problem generating html docs [Sage-on-Gentoo]

[Steven Trogdon]

The following error is present in generating the html docs for 
sage-on-gentoo:

OSError: [tutorial ] 
/storage/strogdon/gentoo-redlizard/var/tmp/portage/sci-mathematics/sage-doc--r1/work/sage-/src/doc/fr/tutorial/tour_coercion.rst:149:
 
WARNING: Inline literal start-string without end-string.

and

$ rst2html.py src/doc/fr/tutorial/tour_coercion.rst > /dev/null
src/doc/fr/tutorial/tour_coercion.rst:149: (WARNING/2) Inline literal 
start-string without end-string

We are using docutils-0.11. Everything seems OK with the docutils that's 
shipped with vanilla Sage. Line 149 of tour_coercion.rst begins with

Le type ``RingElement`` ne correspond pas parfaitement à la notion
mathématique d'élément d'anneau. Par exemple, bien que les matrices carrées
appartiennent à un anneau, elles ne sont pas de type ``RingElement`` :

The problem seems to be with the second RingElement. Between the `` and : 
there is a hidden character or perhaps composition of characters. An octal 
dump (od -c) of the file reveals the character(s)

0013400   `   `   R   i   n   g   E   l   e   m   e   n   t   `   `
0013420 302 240   :  \n  \n   :   :  \n  \n   s   a   g

The 302 is octal for a "circumflex capital A" and 240 is for a "nonbreaking 
space". Apparently, docutils-0.11 doesn't like this. Are there any ideas of 
how these characters made their way into tour_coercion.rst? If Sage 
upgrades to docutils-0.11 I'm reasonably sure the error will be present.

-- 
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 http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Error installing package conway_polynomials-0.5.p0 on Ubuntu 12.04 - Sage 6.1.1

[Steven Trogdon]

On Friday, February 7, 2014 12:31:59 PM UTC-6, François wrote:
>
> While gold is part of the problem it is not completely its fault in my 
> opinion. 
> gold I think default to "as-needed" sage/rings/model. complex_double.pyx 
> doesn't directly 
> call cblas so gold doesn't see it as needed and drop it. The problem here 
> is that libgsl 
> itself is not linked properly for it to work - regardless of gold. 
> If you check the readelf -d output for libgsl there is no mention of 
> libcblas/libgslcblas 
> in the nedded section. So the libgsl doesn't even know where to find its 
> undefined symbols. 
> I guess gold may be made to work here if we can convince it to include 
> libcblas in the 
> needed section of complex_double.so. But I think we should fix the 
> somewhat fishy 
> stuff in libgsl, sure it is legal and all in that you can link with the 
> libclas of your choice 
> and gold may even do the right thing for an executable where all symbols 
> have to be 
> resolved but a .so? Well undefined symbols is legal for a library. 
>
>  
Yes, I do find it somewhat odd that even with a properly built and linked 
Sage there are undefined symols in libgsl.so. There must be some level of 
linking where even this will fail.

So I would like to know what libgsl looks like before Jean-Pierre's fix for 
> cygwin. 
>
> Francois 
>  
> From: sage-...@googlegroups.com  
> [sage-...@googlegroups.com] 
> on behalf of Volker Braun [vbrau...@gmail.com ] 
> Sent: Saturday, 8 February 2014 6:32 
> To: sage-...@googlegroups.com  
> Subject: Re: [sage-devel] Error installing package 
> conway_polynomials-0.5.p0 on Ubuntu 12.04 - Sage 6.1.1 
>
> So that seems to be the answer, OP uses the gold linker instead of the 
> standard gnu ld. Which apparently can't link Sage. To fix this, uninstall 
> binutils-gold. Gold is geared towards C++ so I'm not too surprised that it 
> fails. Its also relatively new, especially for OP's linux version. 
>
>
>
> On Friday, February 7, 2014 5:24:58 PM UTC, Steven Trogdon wrote: 
> It would seem that there's a problem with Binutils. I basically have the 
> same OS and gcc but with different hardware. However I have 
>
> $ ld -v 
> GNU ld (GNU Binutils for Ubuntu) 2.22 
>
> and the linking is good. I had some other hiccups, mainly with cvxopt, 
> when building 6.1.1 but eventually the build completed. I'm not sure why 
> there is a difference in Binutils? 
>
> On Friday, February 7, 2014 10:13:34 AM UTC-6, sho...@ualberta.ca wrote: 
> Well I did build it successfully once. It was on 12.04 Ubuntu that had 
> been used a lot - many softwares built on it. I then upgraded to 13.10, had 
> many problems, and then decided to reinstall (fresh) 12.04LTS over the top 
> (even reformatted) of 13.10. So in essence, my Ubuntu is pretty new and may 
> not have a lot of "stuff", even though it does have all the prerequisites. 
>
> I've actually tried to build 5.13, 6.0, and 6.1.1 and none have worked. It 
> always complains about "conway_polynomail" I have the log files still 
> too if that can help. 
>
> I'll try the GIT build today and see what happens. 
>
> I've also wondered about the  PPA build of sagemath, though I don't like 
> the idea of not having a self-contained directory/tree - maybe though it 
> would install something in my /usr/bin or /usr/lib, etc. that I'm 
> missing. 
>
> Thanks for the suggestion. 
>
> Brett 
>
> On Friday, February 7, 2014 7:40:08 AM UTC-7, Niles Johnson wrote: 
> On Thursday, February 6, 2014 8:39:14 PM UTC-7, François wrote: 
> I am stumped. I will have to think it over for a bit. Output of "ld -v" 
> please. 
>
> While François is thinking, I'll make some other (more rudimentary) 
> suggestions. 
>
> * Have you successfully built older versions of sage?  What is the latest 
> one that builds? 
>
> * Are there any other packages failing to build? (My guess is no.) 
>
> * Could you try checking out and building from the git repository (this 
> shouldn't make a difference, but who knows!?) 
> [if you checkout the git repository, you can easily roll back to older 
> versions with, e.g., git checkout 6.0] 
>
> * In particular, maybe try building the develop branch, just to see 
> whether you get the same or different problems 
>
> -- 
> 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+...@googlegroups.com . 
> To post to this group, send email t

Re: [sage-devel] Error installing package conway_polynomials-0.5.p0 on Ubuntu 12.04 - Sage 6.1.1

[Steven Trogdon]

It would seem that there's a problem with Binutils. I basically have the 
same OS and gcc but with different hardware. However I have

$ ld -v
GNU ld (GNU Binutils for Ubuntu) 2.22

and the linking is good. I had some other hiccups, mainly with cvxopt, when 
building 6.1.1 but eventually the build completed. I'm not sure why there 
is a difference in Binutils?

On Friday, February 7, 2014 10:13:34 AM UTC-6, sho...@ualberta.ca wrote:
>
> Well I did build it successfully once. It was on 12.04 Ubuntu that had 
> been used a lot - many softwares built on it. I then upgraded to 13.10, had 
> many problems, and then decided to reinstall (fresh) 12.04LTS over the top 
> (even reformatted) of 13.10. So in essence, my Ubuntu is pretty new and may 
> not have a lot of "stuff", even though it does have all the prerequisites.
>
> I've actually tried to build 5.13, 6.0, and 6.1.1 and none have worked. It 
> always complains about "conway_polynomail" I have the log files still 
> too if that can help.
>
> I'll try the GIT build today and see what happens.
>
> I've also wondered about the  PPA build of sagemath, though I don't like 
> the idea of not having a self-contained directory/tree - maybe though it 
> would install something in my /usr/bin or /usr/lib, etc. that I'm 
> missing.
>
> Thanks for the suggestion.
>
> Brett
>
> On Friday, February 7, 2014 7:40:08 AM UTC-7, Niles Johnson wrote:
>>
>> On Thursday, February 6, 2014 8:39:14 PM UTC-7, François wrote:

 I am stumped. I will have to think it over for a bit. Output of "ld -v" 
 please. 

>>>
>> While François is thinking, I'll make some other (more rudimentary) 
>> suggestions.
>>
>> * Have you successfully built older versions of sage?  What is the latest 
>> one that builds?
>>
>> * Are there any other packages failing to build? (My guess is no.)
>>
>> * Could you try checking out and building from the git repository (this 
>> shouldn't make a difference, but who knows!?)
>> [if you checkout the git repository, you can easily roll back to older 
>> versions with, e.g., git checkout 6.0]
>>
>> * In particular, maybe try building the develop branch, just to see 
>> whether you get the same or different problems
>>
>

-- 
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 http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/groups/opt_out.