from:"Ralf Stephan"

Re: [sage-release] Re: Sage 8.3.beta0 released

2018-05-10 Thread Ralf Stephan

Upgrades fine with clang-5.0.1 on OpenSuSE Linux, clang-6 would not compile
giac I opened #25324.

On Thu, May 10, 2018 at 8:29 AM Henri Girard  wrote:

> On ubuntu I recently had a problem because curl didn't install properly I
> think with bionic I think it's ok
>
> Le 09/05/2018 à 22:11, John H Palmieri a écrit :
>
> Volker, it must be a conscious decision on your part to not include curl,
> git, gcc, and perhaps others in the upstream directory of the
> "self-contained" tarball. Can you explain? Are those the only three
> affected packages, or are there others?
>
> (If we expect people to have internet access while building, why include
> anything in upstream? If we want to allow for people building without
> internet access, why not include all standard packages, even those not
> built on every system?)
>
>   John
>
>
> On Wednesday, May 9, 2018 at 11:44:17 AM UTC-7, Volker Braun wrote:
>>
>> As always, you can get the latest beta version from the "develop" git
>> branch. Alternatively, the self-contained source tarball is at
>> http://www.sagemath.org/download-latest.html
>>
>>
>> 8bdc326ba5 (tag: 8.3.beta0, trac/develop) Updated SageMath version to
>> 8.3.beta0
>> 537a270597 Trac #24921: Add optional package "ninja_build" (build system
>> for polymake)
>> 31df4df870 Trac #24909: Boruvka algorithm for MST
>> ad537e4b5f Trac #24903: optional package autotools fail to build
>> 500d2feb38 Trac #24626: More substantial implementation of matrices over
>> complex ball fields
>> 96987ac2a5 Trac #25076: Fix Matrix_gfpn_dense * int
>> 80adc4fc7a Trac #24878: Improve function? docstring
>> 1968b08e11 Trac #24848: Implement join of polytopes
>> 4a4830018f Trac #24839: py3: an issue about dict iterators
>> ad6ee1bb25 Trac #24742: New MatrixArgs object to deal with constructing
>> matrices
>> 13fd23bb80 Trac #24370: Riemann surfaces: algebraization and automorphisms
>> 9fb25e50bd Trac #19506: Implement cellular algebras
>> 59c99eca6a Trac #16823: Implement the free Lie algebra
>> 70e163d515 Trac #24835: Change error message in construction of
>> polyhedron object
>> e498ec4415 Trac #24788: Multiplication of the Gram Matrix
>> 2c0ee06538 Trac #24680: Cleanup some deprecated functions (matrix and
>> coding)
>> 30c21d31cf Trac #24662: Upgrade scipoptsuite to 5.0.1
>> 0c9519f6c5 Trac #23665: Implement Frobenius formula for Hecke algebra
>> characters
>> d2deec20a0 Trac #24645: Support for spkg-postinst scripts
>> 68e8076fcc Trac #24644: Use $SAGE_SUDO when copying files from
>> SAGE_DESTDIR to SAGE_LOCAL
>> ea439259c1 Trac #24638: Fix OpenBLAS build on SPARC
>> 7e5f242d33 Trac #24623: Euclidean spaces and vector calculus
>> dce704249c Trac #24585: r_jupyter package is broken
>> c46927cb09 Trac #24577: is_genus for torsion quadratic modules
>> 0bdd6f9d39 Trac #24576: Brown invariant of a TorsionQuadraticModule
>> 5cc1dd4967 Trac #24564: Gluing of lattices
>> af11d43628 Trac #24559: py3: better backwards-compatibility for Python
>> longs
>> 3307f67637 Trac #24541: Fix Cone.orthogonal_sublattice
>> 52ab02ee18 Trac #24508: py3: problems with tests that use random_element
>> 87dcf8209d Trac #24481: Replace PARI stackwarn.patch with upstream version
>> 9dabe7b561 Trac #24433: Speed up p-adic Gamma by caching Dwork expansion
>> coefficients
>> 0c6181d7b3 Trac #24416: GeneralDiscreteDistribution broken when entries
>> >= 2^1024
>> 6aa51476fe Trac #24323: 'BrauerAlgebra' has no attribute 'options'
>> e4ec2f6209 Trac #24314: rootfinding for polynomials with complex ball
>> coefficients using arb
>> 79c3ec00ee Trac #24312: py3: fixes to sage.misc.sageinspect
>> 14669b2e42 Trac #24152: Bug when converting a Sage polyhedron into
>> Polymake pexpect
>> 68fd029608 Trac #24130: Reverse plane partitions and Hillman-Grassl
>> 24c396a1de Trac #24129: Complete the standard bijections on the symmetric
>> group
>> b3ce0ca72f Trac #23733: Stop supporting SAGE64 and CFLAG64
>> 94e5a73e75 Trac #23450: Smith form of p-adic matrices
>> 5d8a91b23c Trac #23353: Upgrade to gfan 0.6.2
>> d8c7427822 Trac #23344: p-adic square root
>> 577a9ce597 Trac #22984: Upgrade normaliz to 3.5.3 and pynormaliz to 1.12
>> cd4ad379e2 Trac #22604: autodoc unforking again
>> 9d10e48944 Trac #22572: Add a thematic tutorial on the polyhedron class
>> a24a9c6b30 Trac #22243: Make doctests not depend on the boost version
>> fdf74cc00b Trac #21022: version information in sage.__version__
>> 417875c300 Trac #20382: Replace is_package_installed with Features
>> b4829dabec Trac #19270: Matrix_integer_sparse object has no attribute
>> 'gap'
>> 82025348ef Trac #17340: can't plot immutable graphs
>> b1a0575489 Trac #15729: Graphics3d with fractional opacity will not save
>> image
>> 7926af1fa4 Trac #10577: Deepcopy fails on vectorspaces over GF(2) with
>> inner_product_matrix specified
>> 3c408bc16f Trac #7589: bug in coercion and cyclotomic fields
>> 7d35dbf26c Trac #25118: gfan fails when compiled with XCode 9.3
>> 3c0ce4d54e Trac #24880: gcd is

[sage-release] Re: Sage 8.2.rc3 released

2018-04-17 Thread Ralf Stephan

Builds fine from scratch with clang-5.0.1. sage -gdb will now abort here 
however.
https://trac.sagemath.org/ticket/25196

On Tuesday, April 17, 2018 at 12:34:24 AM UTC+2, Volker Braun wrote:
>
> As always, you can get the latest beta version from the "develop" git 
> branch. Alternatively, the self-contained source tarball is at 
> http://www.sagemath.org/download-latest.html
>
> a9d274b933 (tag: 8.2.rc3, trac/develop) Updated SageMath version to 8.2.rc3
> d85d03cfc3 Trac #25051: Add DESTDIR support to additional Python packages; 
> upgrade pip to latest patch release
> ab932bd4d3 Trac #23969: Downgrade cryptominisat to experimental
> 9bac572eb4 Trac #25107: Ignored OSErrors in test output on Cygwin
> 3d4ffb3923 Trac #25092: sage --gdb does not start due to SIGFPE
> f150587302 Trac #25137: Temporarily skip the test that causes #24986
> 303efaa461 (tag: 8.2.rc2) Updated SageMath version to 8.2.rc2
>
>

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

Re: [sage-release] Sage 8.2.rc1 released

2018-04-01 Thread Ralf Stephan

Testing on OpenSuSE fails because of https://trac.sagemath.org/ticket/24920
So, still no working patchbots with that system.

On Sun, Apr 1, 2018 at 8:46 AM Ralf Stephan <gtrw...@gmail.com> wrote:

> Builds fine with clang-5 on OpenSuSE but not with the new clang-6.0.0 due
> to gfan. I opened
> https://trac.sagemath.org/ticket/25072
>
> On Sun, Apr 1, 2018 at 6:03 AM Justin C. Walker <jus...@mac.com> wrote:
>
>>
>> > On Mar 31, 2018, at 15:39 , Volker Braun <vbraun.n...@gmail.com> wrote:
>> >
>> > As always, you can get the latest beta version from the "develop" git
>> branch. Alternatively, the self-contained source tarball is at
>> http://www.sagemath.org/download-latest.html
>>
>> Built from a fresh clone/update of the develop branch on macOS 10.11.6
>> (Quad-core Core i7) w/o problems, and all tests (‘testing’) passed!
>>
>> Justin
>>
>> --
>> Justin C. Walker, Curmudgeon-At-Large
>> Director
>> Institute for the Enhancement of the Director's Income
>> 
>> "Weaseling out of things is what separates us from the animals.
>>  Well, except the weasel."
>>   - Homer J Simpson
>> 
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "sage-release" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to sage-release+unsubscr...@googlegroups.com.
>> To post to this group, send email to sage-release@googlegroups.com.
>> Visit this group at https://groups.google.com/group/sage-release.
>> For more options, visit https://groups.google.com/d/optout.
>>
>

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

Re: [sage-release] Sage 8.2.rc1 released

2018-04-01 Thread Ralf Stephan

Builds fine with clang-5 on OpenSuSE but not with the new clang-6.0.0 due
to gfan. I opened
https://trac.sagemath.org/ticket/25072

On Sun, Apr 1, 2018 at 6:03 AM Justin C. Walker  wrote:

>
> > On Mar 31, 2018, at 15:39 , Volker Braun  wrote:
> >
> > As always, you can get the latest beta version from the "develop" git
> branch. Alternatively, the self-contained source tarball is at
> http://www.sagemath.org/download-latest.html
>
> Built from a fresh clone/update of the develop branch on macOS 10.11.6
> (Quad-core Core i7) w/o problems, and all tests (‘testing’) passed!
>
> Justin
>
> --
> Justin C. Walker, Curmudgeon-At-Large
> Director
> Institute for the Enhancement of the Director's Income
> 
> "Weaseling out of things is what separates us from the animals.
>  Well, except the weasel."
>   - Homer J Simpson
> 
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-release" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-release+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-release@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-release.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [sage-release] Sage 8.2.rc0 released

2018-03-28 Thread Ralf Stephan

Builds fine but crashes when testing combinat/posets/poset_examples.py on
OpenSuSE.
This is fixed by https://trac.sagemath.org/ticket/21828 which is positively
reviewed. Please merge!

On Wed, Mar 28, 2018 at 9:57 PM Volker Braun  wrote:

> As always, you can get the latest beta version from the "develop" git
> branch. Alternatively, the self-contained source tarball is at
> http://www.sagemath.org/download-latest.html
>
> e5c848a64c (tag: 8.2.rc0, trac/develop, github/develop) Updated SageMath
> version to 8.2.rc0
> ce8d5f7601 Trac #13135: list_plot3d.py should not generate NaN coordinates
> cf71ce3037 Trac #24995: $(SAGERUNTIME) dependency broken
> 18e7581f64 Trac #24111: Upgrade to Cython 0.28.1
> 015172aa47 Trac #24997: Typo correction: chose -> choose
> f13926d7dc Trac #24974: fix parent of zeta polynomials of posets
> 43c5a4ab69 Trac #24959: slightly faster tamari_pred
> e1fa8e6010 Trac #24958: py3: fix str -> Integer bug in sage.libs.gap
> 0bd76b7bb4 Trac #24926: add names to some strongly regular graphs
> 3649debe5f Trac #24887: use https in stopgap links
> fb8f165b09 Trac #24875: make difference distribution matrix immutable
> 6a2050b73e Trac #24825: py3: fix sage.misc.banner
> d81ba7d5b5 Trac #24816: Sums of products of arb balls
> ea111474ed Trac #24791: py3: fix tests in
> sage.structure.unique_representation
> f0b54a8a56 Trac #24996: pathlib2 depends on scandir
> 395daf1a9a Trac #24993: py3: get rid of an import from sagenb in misc/latex
> d9d700aca9 Trac #24991: acyclic_edge_coloring(G, value_only=True) always
> gives 0.0
> 1d3e21b1ea Trac #24987: Cython packages are not installed
> f02dab54d4 Trac #24983: py3: fix the repr of Set
> 315748ae1e Trac #24982: adding one missing hash in crystal
> 9e5b2d72bc Trac #24980: py3: remove some __cmp__
> 239a10740f Trac #24979: add parameter solver to method
> Hilbert_coefficients of cone
> 8eb52ee9e2 Trac #24978: use parameter solver in SatLP
> aa174a0c4b Trac #24977: add parameter solver to method flat_cover of
> matroids
> 0cce529301 Trac #24972: Package sphinxcontrib_websupport
> 3b4d25bfe2 Trac #24968: Do not compare types in coercion model richcmp()
> 9eea8153c3 Trac #24967: py3: fix comparison of pivots
> 58fb35883d Trac #24964: KeyError in DiGraph.is_isomorphic when
> certificate=True
> eac8f65cf6 Trac #24946: py3: details in numerical folder
> e93efbbdd0 Trac #24945: Use lazy attribute for _Karatsuba_threshold
> e55581b87f Trac #24936: sage_getdoc_original() finds wrong doc
> 245c41619c Trac #24931: py3: get rid of __cmp__ in real_mpfr.pyx
> f0abe5edd4 Trac #24930: py3: some cmp removal in pyx files
> 485291c3f8 Trac #24923: sparse6 encoding and decoding of graphs with a
> single vertex
> edc2db9171 Trac #24922: Use restore_atexit in doctest framework
> 2343f21743 Trac #24915: Minor fixes for Cython 0.28
> 30e573db1a Trac #24873: some new methods for Tamari interval-posets
> 236cd50488 Trac #24853: substitution into polynomials over SR broken
> 25902c412b Trac #24826: Fix _latex_ of ChainComplex with grading_group !=
> ZZ
> 3d65cf93d2 Trac #24754: Clean up EvaluationMethods
> 9c7e114a22 Trac #24746: py3 fixes to integer_mod.pyx
> a89a12ad27 Trac #24647: Stricter locking around sage-rebase on Cygwin
> af3e3014a4 Trac #24630: Inconsistency in conversion from CIF and complex
> 962ac3743b Trac #24578: Sage Interact Quickstart - dead link.
> 5ba00af04b Trac #24412: wrap arb elliptic functions
> fe173f2d9b Trac #24343: py3: miscellaneous fixes to sage.doctest
> 5d1b969cae Trac #22589: typo fix
> 529449dab8 Trac #21509: Improve Cython debugging
> f7cabb2043 Trac #24864: bug in TorsionQuadraticForm.normal_form()
> b3d9e5d7e5 Trac #25001: gfortran breaks parallel build
> 4d498cc0b1 Trac #24963: Doctests write to /tmp
> dfe8cd2133 Trac #24947: meataxe doctest failure on 8.2.beta8
> 054833f99b Trac #24769: make download-for-sdist race
> eb3433e2c9 Trac #24907: GCC is installed multiple times
> c810dd8776 Trac #24961: Followup to #21524 -- upgrade broken when gcc spkg
> is installed
> 0632db4c2d Trac #23856: Remove
> src/sage/ext/notes/lenard_lindstrom-richcmp.txt
> d763106aff Trac #24940: adding more cases of the arxiv role
> 6b96ae5d53 Trac #24892: Relabelled non-crystallographic finite types
> should not have an ambient space (yet)
> ace16ce0d7 Trac #24819: sbox linear approximation matrix scaling
> 49f0a7e066 Trac #24916: Fix __richcmp__ calls with reversed operands
> cd83cfa1f6 Trac #24828: Length-checking iterator
> 5b2058ef1e Trac #24775: py3: miscellaneous minor bytes/str fixes
> 764df4c0fd Trac #24622: Pseudo-Riemannian manifods
> 6365745b4c Trac #23852: libgap is wrongly dealing with vectors
> 62706a73eb Trac #24929: Fix q_binomial
> cb32ae937a Trac #17251: Incomplete multivariate factorization
> 5909f9c2ed Trac #24918: Failing doctest in test_jupyter.rst when running
> patchbot
> e77142c8d6 Trac #24901: optional package notedown fail to install
> 9bf9f05f1f (tag: 8.2.beta8, sagemath/develop) Updated SageMath version to
>

Re: [sage-release] Re: Sage 8.2.beta8 released

2018-03-13 Thread Ralf Stephan

It would be good to have a final review on #21828, as OpenSuSE systems
still fail doctests and so cannot participate as patchbots.

On Tue, 13 Mar 2018, 11:26 Ralf Stephan, <gtrw...@gmail.com> wrote:

> This is #24918 that was too late to be merged, apparently.
>
> On Tue, 13 Mar 2018, 11:19 Eric Gourgoulhon, <egourgoul...@gmail.com>
> wrote:
>
>> On Ubuntu 16.04 x86_64 Xeon E5-2623 + 16 GB RAM, from a fresh git clone +
>> pull develop, parallel (-j16) build OK and make ptestlong failed with one
>> doctest in
>> src/sage/interacts/test_jupyter.rst
>> as already reported for 8.2.beta7.
>> The doctest is passed when run standalone.
>>
>> Eric.
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "sage-release" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to sage-release+unsubscr...@googlegroups.com.
>> To post to this group, send email to sage-release@googlegroups.com.
>> Visit this group at https://groups.google.com/group/sage-release.
>> For more options, visit https://groups.google.com/d/optout.
>>
>

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

Re: [sage-release] Re: Sage 8.2.beta8 released

2018-03-13 Thread Ralf Stephan

This is #24918 that was too late to be merged, apparently.

On Tue, 13 Mar 2018, 11:19 Eric Gourgoulhon,  wrote:

> On Ubuntu 16.04 x86_64 Xeon E5-2623 + 16 GB RAM, from a fresh git clone +
> pull develop, parallel (-j16) build OK and make ptestlong failed with one
> doctest in
> src/sage/interacts/test_jupyter.rst
> as already reported for 8.2.beta7.
> The doctest is passed when run standalone.
>
> Eric.
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-release" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-release+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-release@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-release.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [sage-release] Re: Sage 8.2.beta7 released

2018-03-07 Thread Ralf Stephan

Builds fine using clang-5.0.1 on OpenSuSE Linux.

On Tue, Mar 6, 2018 at 4:08 PM Ralf Stephan <gtrw...@gmail.com> wrote:

> The test_jupyter.rst fail is now https://trac.sagemath.org/ticket/24918
>
> On Tue, Mar 6, 2018 at 10:46 AM Emmanuel Charpentier <
> emanuel.charpent...@gmail.com> wrote:
>
>> FWIW, same result onDeian testing running on Core i5 + 8 GB RAM.
>>
>> --
>> Emmanuel Charpentier
>>
>> Le samedi 3 mars 2018 12:09:52 UTC+1, Emmanuel Charpentier a écrit :
>>>
>>> FWIW, builds and passes ptestlong without any failure on Debian testing
>>> running on Core i7 + 16 GB RAM
>>>
>>> HTH,
>>>
>>> --
>>> Emmanuel Charpentier
>>>
>>> Le samedi 3 mars 2018 01:50:39 UTC+1, Volker Braun a écrit :
>>>>
>>>> As always, you can get the latest beta version from the "develop" git
>>>> branch. Alternatively, the self-contained source tarball is at
>>>> http://www.sagemath.org/download-latest.html
>>>>
>>>> 3750eaa411 (tag: 8.2.beta7) Updated SageMath version to 8.2.beta7
>>>> c6fc4193d4 Trac #24703: Everything should be rebuilt after GCC upgrade
>>>> 2e2a69c75c Trac #24772: Encoding fixes to the doctest module
>>>> 6e3e9d6c11 Trac #24813: py3: Miscellaneous small fixes for sage.arith
>>>> a990a92f51 Trac #24810: _mul_ for IntegralLattices
>>>> 3796ed7999 Trac #24831: py3: remove __cmp__ in categories/functor
>>>> 87d791e0aa Trac #24829: zero_matrix() should pass the correct zero
>>>> 9734864877 <(973)%20486-4877> Trac #24818: Bug in genus of a quadratic
>>>> form
>>>> 7c12eda717 Trac #24814: Don't abuse prepare_dict() in ChainComplex
>>>> 11ba8c5297 Trac #24773: Delayed/Conditional Substitution
>>>> d906dc42d8 Trac #24588: py3: several long/int related fixes
>>>> 5442f6226d Trac #24827: Doctest failures in fricas interface
>>>> c191117f78 Trac #24635: make vertex_connectivity faster if only a lower
>>>> bound is required.
>>>> f1e208372b Trac #24799: Raising NotImplemented
>>>> deaa572ec5 Trac #24803: fixing some bad use of raise
>>>> 8e985ebea4 Trac #24789: py3: updates to sage.interfaces.qsieve
>>>> 58bc11397d Trac #24573: bug in creating graphic matroid with explicit
>>>> groundset labels
>>>> 196d3cc383 Trac #24391: DynkinDiagram.marked_nodes doesn't work
>>>> b0d74897a9 Trac #19628: lazy_import breaks CachedRepresentation
>>>> 7640d68cb6 Trac #24702: Intersections and saturations of
>>>> FreeQuadraticModules have the wrong ambient module
>>>> 76ae35b3b1 Trac #24787: Fix indentation in sage.misc.randstate
>>>> 0fb74a8f7e Trac #24794: py3: remove some commented __cmp__ (for cleanup)
>>>> a77a2f0bd8 Trac #24781: another branch of typos
>>>> d61e7dedd5 Trac #24777: Chromatic number of the empty graph by MILP
>>>> 884072c50c Trac #24796: py3: sort repr of OrlikSolomonAlgebra
>>>> 44c25dc927 Trac #24795: py3: fix pickling of
>>>> sage.symbolic.function.SymbolicFunction
>>>> 6c18344f3e Trac #24720: Totally silent mode for cython()
>>>> e67f4fbd16 Trac #23701: new standard package libatomic_ops
>>>> 88dc0cfa59 Trac #24780: py3: convert a few more classes to new-style
>>>> classes
>>>> 186207a5d8 Trac #24778: py3: fix some minor doctest failures in
>>>> sage.libs.mpmath
>>>> 6ad7c8a7e2 Trac #24759: Sort the repr of PolyDict by its dict keys
>>>> f75e7b6bc8 Trac #24771: Miscellaneous fixes to the doctest module
>>>> e32b57a4c5 Trac #24770: Doctest: use new-style classes
>>>> 3d5cc7aed2 Trac #24729: Add --with-python=3 configure flag to replace
>>>> SAGE_PYTHON3=yes
>>>> ba0d124149 Trac #24724: Capture warning/errors messages in
>>>> sage.misc.cython
>>>> d87395f04c Trac #24686: Integration of piecewise analytic complex
>>>> functions using arb
>>>> c8015d7a71 Trac #24531: Replace ratpoints by PARI
>>>> 50a97b3777 Trac #24763: Run scripts with sage-python23
>>>> 43a39f6c1b Trac #24744: implementation of boomerang connectivity table
>>>> 93020a4eb1 (tag: 8.2.beta6) Updated SageMath version to 8.2.beta6
>>>>
>>>> --
>> You received this message because you are subscribed to the Google Groups
>> "sage-release" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to sage-release+unsubscr...@googlegroups.com.
>> To post to this group, send email to sage-release@googlegroups.com.
>> Visit this group at https://groups.google.com/group/sage-release.
>> For more options, visit https://groups.google.com/d/optout.
>>
>

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

Re: [sage-release] Re: Sage 8.2.beta7 released

2018-03-06 Thread Ralf Stephan

The test_jupyter.rst fail is now https://trac.sagemath.org/ticket/24918

On Tue, Mar 6, 2018 at 10:46 AM Emmanuel Charpentier <
emanuel.charpent...@gmail.com> wrote:

> FWIW, same result onDeian testing running on Core i5 + 8 GB RAM.
>
> --
> Emmanuel Charpentier
>
> Le samedi 3 mars 2018 12:09:52 UTC+1, Emmanuel Charpentier a écrit :
>>
>> FWIW, builds and passes ptestlong without any failure on Debian testing
>> running on Core i7 + 16 GB RAM
>>
>> HTH,
>>
>> --
>> Emmanuel Charpentier
>>
>> Le samedi 3 mars 2018 01:50:39 UTC+1, Volker Braun a écrit :
>>>
>>> As always, you can get the latest beta version from the "develop" git
>>> branch. Alternatively, the self-contained source tarball is at
>>> http://www.sagemath.org/download-latest.html
>>>
>>> 3750eaa411 (tag: 8.2.beta7) Updated SageMath version to 8.2.beta7
>>> c6fc4193d4 Trac #24703: Everything should be rebuilt after GCC upgrade
>>> 2e2a69c75c Trac #24772: Encoding fixes to the doctest module
>>> 6e3e9d6c11 Trac #24813: py3: Miscellaneous small fixes for sage.arith
>>> a990a92f51 Trac #24810: _mul_ for IntegralLattices
>>> 3796ed7999 Trac #24831: py3: remove __cmp__ in categories/functor
>>> 87d791e0aa Trac #24829: zero_matrix() should pass the correct zero
>>> 9734864877 <(973)%20486-4877> Trac #24818: Bug in genus of a quadratic
>>> form
>>> 7c12eda717 Trac #24814: Don't abuse prepare_dict() in ChainComplex
>>> 11ba8c5297 Trac #24773: Delayed/Conditional Substitution
>>> d906dc42d8 Trac #24588: py3: several long/int related fixes
>>> 5442f6226d Trac #24827: Doctest failures in fricas interface
>>> c191117f78 Trac #24635: make vertex_connectivity faster if only a lower
>>> bound is required.
>>> f1e208372b Trac #24799: Raising NotImplemented
>>> deaa572ec5 Trac #24803: fixing some bad use of raise
>>> 8e985ebea4 Trac #24789: py3: updates to sage.interfaces.qsieve
>>> 58bc11397d Trac #24573: bug in creating graphic matroid with explicit
>>> groundset labels
>>> 196d3cc383 Trac #24391: DynkinDiagram.marked_nodes doesn't work
>>> b0d74897a9 Trac #19628: lazy_import breaks CachedRepresentation
>>> 7640d68cb6 Trac #24702: Intersections and saturations of
>>> FreeQuadraticModules have the wrong ambient module
>>> 76ae35b3b1 Trac #24787: Fix indentation in sage.misc.randstate
>>> 0fb74a8f7e Trac #24794: py3: remove some commented __cmp__ (for cleanup)
>>> a77a2f0bd8 Trac #24781: another branch of typos
>>> d61e7dedd5 Trac #24777: Chromatic number of the empty graph by MILP
>>> 884072c50c Trac #24796: py3: sort repr of OrlikSolomonAlgebra
>>> 44c25dc927 Trac #24795: py3: fix pickling of
>>> sage.symbolic.function.SymbolicFunction
>>> 6c18344f3e Trac #24720: Totally silent mode for cython()
>>> e67f4fbd16 Trac #23701: new standard package libatomic_ops
>>> 88dc0cfa59 Trac #24780: py3: convert a few more classes to new-style
>>> classes
>>> 186207a5d8 Trac #24778: py3: fix some minor doctest failures in
>>> sage.libs.mpmath
>>> 6ad7c8a7e2 Trac #24759: Sort the repr of PolyDict by its dict keys
>>> f75e7b6bc8 Trac #24771: Miscellaneous fixes to the doctest module
>>> e32b57a4c5 Trac #24770: Doctest: use new-style classes
>>> 3d5cc7aed2 Trac #24729: Add --with-python=3 configure flag to replace
>>> SAGE_PYTHON3=yes
>>> ba0d124149 Trac #24724: Capture warning/errors messages in
>>> sage.misc.cython
>>> d87395f04c Trac #24686: Integration of piecewise analytic complex
>>> functions using arb
>>> c8015d7a71 Trac #24531: Replace ratpoints by PARI
>>> 50a97b3777 Trac #24763: Run scripts with sage-python23
>>> 43a39f6c1b Trac #24744: implementation of boomerang connectivity table
>>> 93020a4eb1 (tag: 8.2.beta6) Updated SageMath version to 8.2.beta6
>>>
>>> --
> You received this message because you are subscribed to the Google Groups
> "sage-release" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-release+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-release@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-release.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [sage-release] Sage 8.2.beta7 released

2018-03-05 Thread Ralf Stephan

As to the test_jupyter.rst fail, I cannot confirm it manually, can someone?
I checked the dates where patchbots started to fail on tickets that passed
previously, and in every case the change was between Mar-01 and Mar-03.
So the problem was introduced with this release. Any ideas?

On Sun, Mar 4, 2018 at 3:43 PM Ralf Stephan <gtrw...@gmail.com> wrote:

> Note that (from patchbot page 0) most patchbots fail on
>
> sage -t--long src/sage/interacts/test_jupyter.rst
>
>
> On Sat, Mar 3, 2018 at 11:17 PM Justin C. Walker <jus...@mac.com> wrote:
>
>>
>> > On Mar 2, 2018, at 16:50 , Volker Braun <vbraun.n...@gmail.com> wrote:
>> >
>> > As always, you can get the latest beta version from the "develop" git
>> branch. Alternatively, the self-contained source tarball is at
>> http://www.sagemath.org/download-latest.html
>>
>> Built on macOS 10.11.6 (Quad-core Core i7).  Built w/o problems, and all
>> tests (‘ptestlong’) passed!
>>
>> Justin
>>
>> --
>> Justin C. Walker
>> Curmudgeon-at-large
>> Director
>> Institute for the Absorption of Federal Funds
>> 
>> 186,000 Miles per Second
>> Not just a good idea:
>>   it's the law!
>> 
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "sage-release" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to sage-release+unsubscr...@googlegroups.com.
>> To post to this group, send email to sage-release@googlegroups.com.
>> Visit this group at https://groups.google.com/group/sage-release.
>> For more options, visit https://groups.google.com/d/optout.
>>
>

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

Re: [sage-release] Sage 8.2.beta7 released

2018-03-04 Thread Ralf Stephan

Note that (from patchbot page 0) most patchbots fail on

sage -t--long src/sage/interacts/test_jupyter.rst


On Sat, Mar 3, 2018 at 11:17 PM Justin C. Walker  wrote:

>
> > On Mar 2, 2018, at 16:50 , Volker Braun  wrote:
> >
> > As always, you can get the latest beta version from the "develop" git
> branch. Alternatively, the self-contained source tarball is at
> http://www.sagemath.org/download-latest.html
>
> Built on macOS 10.11.6 (Quad-core Core i7).  Built w/o problems, and all
> tests (‘ptestlong’) passed!
>
> Justin
>
> --
> Justin C. Walker
> Curmudgeon-at-large
> Director
> Institute for the Absorption of Federal Funds
> 
> 186,000 Miles per Second
> Not just a good idea:
>   it's the law!
> 
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-release" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-release+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-release@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-release.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [sage-release] Sage 8.2.beta6 released

2018-02-18 Thread Ralf Stephan

beta6 builds fine from scratch with clang-4 on OpenSuSE, without needing
patches. Testing later.

On Mon, Feb 19, 2018 at 7:38 AM François Bissey 
wrote:

>
>
> > On 19/02/2018, at 19:36, Justin C. Walker  wrote:
> >
> >>
> >> On Feb 18, 2018, at 12:09 , Volker Braun  wrote:
> >>
> >> As always, you can get the latest beta version from the "develop" git
> branch. Alternatively, the self-contained source tarball is at
> http://www.sagemath.org/download-latest.html
> >
> > Built on macOS 10.11.6 (Quad-core Core i7), from a fresh clone/checkout
> of develop.
> >
> > All tests (‘testlong’) passed!
> >
> > Total time dropped from ~2 1/4 hrs to 1 3/4 hrs, thanks to switch to
> clang!
>
> Not doing a full build of gcc anymore does that for you.
> Its hours saved on my laptop.
>
> François
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-release" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-release+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-release@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-release.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [sage-release] Sage 8.2.beta5 released

2018-02-14 Thread Ralf Stephan

Finally it turns out for a major Linux distro build with clang no
other flags than CC=clang CXX=clang++ are needed, and the #24696 ticket
merged. clang-3.8 will result in a crash in linbox (#24701, #24716) so
clang-4 is recommended because there are problems with clang-5 as reported
in #24704 and #24712.

On Tue, Feb 13, 2018 at 1:00 AM François Bissey 
wrote:

>
>
> > On 13/02/2018, at 12:42, Justin C. Walker  wrote:
> >
> >
> >> On Feb 12, 2018, at 14:45, François Bissey 
> wrote:
> >>
> >> Can you test the branch at https://trac.sagemath.org/ticket/24721
> >> and see if that helps with this particular machine.
> >
> > Sure will.  I have yet to update to Xcode 8.  Should I try the ticket
> before or after updating?
> >
>
> Before :)
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-release" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-release+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-release@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-release.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [sage-release] Re: Sage 8.2.beta5 released

2018-02-12 Thread Ralf Stephan

https://stackoverflow.com/questions/19901128/enable-libc-libcxx-by-default-when-using-clang

On Mon, Feb 12, 2018 at 9:16 AM François Bissey <frp.bis...@gmail.com>
wrote:

>
>
> > On 12/02/2018, at 20:06, Ralf Stephan <gtrw...@gmail.com> wrote:
> >
> > Finally here is the recommended set of flags for clang on Linux:
> >
> > export CC="clang"
> > export CXX="clang++"
> > export CLANG_DEFAULT_CXX_STDLIB="libc++"
> >
>
> Where did you find about this variable? I’d like to know if there are
> other for some other aspects of clang.
>
> François
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-release" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-release+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-release@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-release.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [sage-release] Re: Sage 8.2.beta5 released

2018-02-11 Thread Ralf Stephan

make ptestlong passes on OpenSuSE 42.3 with clang-4.0.1 on top of #24696
with only the usual failures in R and that one reported in #21828.

On Mon, Feb 12, 2018 at 8:06 AM Ralf Stephan <gtrw...@gmail.com> wrote:

> Finally here is the recommended set of flags for clang on Linux:
>
> export CC="clang"
> export CXX="clang++"
> export CLANG_DEFAULT_CXX_STDLIB="libc++"
>
> Thanks to François for the hint. You'll need #24696 if giac doesn't
> install, which seems to occur with clang < 5.
>
> Best,
>
> On Sun, Feb 11, 2018 at 5:53 PM Ralf Stephan <gtrw...@gmail.com> wrote:
>
>> See https://trac.sagemath.org/ticket/24701#comment:5 for the current
>> state of clang on Linux.
>>
>> On Sun, Feb 11, 2018 at 3:39 PM Ralf Stephan <gtrw...@gmail.com> wrote:
>>
>>> Another bug uncovered. With CXXFLAGS='stdlib=libc++' scipy build fails
>>> with, of all things
>>> gfortran: error: unrecognized command line option '--stdlib=libc++'
>>>
>>> Huh?
>>>
>>> On Sun, Feb 11, 2018 at 11:40 AM Simon King <simon.k...@uni-jena.de>
>>> wrote:
>>>
>>>> Hi!
>>>>
>>>> On 2018-02-11, Ralf Stephan <gtrw...@gmail.com> wrote:
>>>> > Update with clang on Linux: sagelib ignores the --stdlib in CXX
>>>> (#24705)
>>>> > and fpylll apparently ignores the --stdlib in CXX and if you give it
>>>> in the
>>>> > CXXFLAGS it uses it only for C not C++ (#24707). So the former is a
>>>> build
>>>> > blocker, the latter a critical because fpylll cannot be imported. I
>>>> think
>>>> > that's it all.
>>>>
>>>> I also get an error at build time, in ratpoints. See #24708.
>>>>
>>>> Best regards,
>>>> Simon
>>>>
>>>> --
>>>> You received this message because you are subscribed to the Google
>>>> Groups "sage-release" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>> an email to sage-release+unsubscr...@googlegroups.com.
>>>> To post to this group, send email to sage-release@googlegroups.com.
>>>> Visit this group at https://groups.google.com/group/sage-release.
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>

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

Re: [sage-release] Re: Sage 8.2.beta5 released

2018-02-11 Thread Ralf Stephan

Finally here is the recommended set of flags for clang on Linux:

export CC="clang"
export CXX="clang++"
export CLANG_DEFAULT_CXX_STDLIB="libc++"

Thanks to François for the hint. You'll need #24696 if giac doesn't
install, which seems to occur with clang < 5.

Best,

On Sun, Feb 11, 2018 at 5:53 PM Ralf Stephan <gtrw...@gmail.com> wrote:

> See https://trac.sagemath.org/ticket/24701#comment:5 for the current
> state of clang on Linux.
>
> On Sun, Feb 11, 2018 at 3:39 PM Ralf Stephan <gtrw...@gmail.com> wrote:
>
>> Another bug uncovered. With CXXFLAGS='stdlib=libc++' scipy build fails
>> with, of all things
>> gfortran: error: unrecognized command line option '--stdlib=libc++'
>>
>> Huh?
>>
>> On Sun, Feb 11, 2018 at 11:40 AM Simon King <simon.k...@uni-jena.de>
>> wrote:
>>
>>> Hi!
>>>
>>> On 2018-02-11, Ralf Stephan <gtrw...@gmail.com> wrote:
>>> > Update with clang on Linux: sagelib ignores the --stdlib in CXX
>>> (#24705)
>>> > and fpylll apparently ignores the --stdlib in CXX and if you give it
>>> in the
>>> > CXXFLAGS it uses it only for C not C++ (#24707). So the former is a
>>> build
>>> > blocker, the latter a critical because fpylll cannot be imported. I
>>> think
>>> > that's it all.
>>>
>>> I also get an error at build time, in ratpoints. See #24708.
>>>
>>> Best regards,
>>> Simon
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "sage-release" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to sage-release+unsubscr...@googlegroups.com.
>>> To post to this group, send email to sage-release@googlegroups.com.
>>> Visit this group at https://groups.google.com/group/sage-release.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>

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

Re: [sage-release] Re: Sage 8.2.beta5 released

2018-02-11 Thread Ralf Stephan

See https://trac.sagemath.org/ticket/24701#comment:5 for the current state
of clang on Linux.

On Sun, Feb 11, 2018 at 3:39 PM Ralf Stephan <gtrw...@gmail.com> wrote:

> Another bug uncovered. With CXXFLAGS='stdlib=libc++' scipy build fails
> with, of all things
> gfortran: error: unrecognized command line option '--stdlib=libc++'
>
> Huh?
>
> On Sun, Feb 11, 2018 at 11:40 AM Simon King <simon.k...@uni-jena.de>
> wrote:
>
>> Hi!
>>
>> On 2018-02-11, Ralf Stephan <gtrw...@gmail.com> wrote:
>> > Update with clang on Linux: sagelib ignores the --stdlib in CXX (#24705)
>> > and fpylll apparently ignores the --stdlib in CXX and if you give it in
>> the
>> > CXXFLAGS it uses it only for C not C++ (#24707). So the former is a
>> build
>> > blocker, the latter a critical because fpylll cannot be imported. I
>> think
>> > that's it all.
>>
>> I also get an error at build time, in ratpoints. See #24708.
>>
>> Best regards,
>> Simon
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "sage-release" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to sage-release+unsubscr...@googlegroups.com.
>> To post to this group, send email to sage-release@googlegroups.com.
>> Visit this group at https://groups.google.com/group/sage-release.
>> For more options, visit https://groups.google.com/d/optout.
>>
>

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

Re: [sage-release] Re: Sage 8.2.beta5 released

2018-02-11 Thread Ralf Stephan

Another bug uncovered. With CXXFLAGS='stdlib=libc++' scipy build fails
with, of all things
gfortran: error: unrecognized command line option '--stdlib=libc++'

Huh?

On Sun, Feb 11, 2018 at 11:40 AM Simon King <simon.k...@uni-jena.de> wrote:

> Hi!
>
> On 2018-02-11, Ralf Stephan <gtrw...@gmail.com> wrote:
> > Update with clang on Linux: sagelib ignores the --stdlib in CXX (#24705)
> > and fpylll apparently ignores the --stdlib in CXX and if you give it in
> the
> > CXXFLAGS it uses it only for C not C++ (#24707). So the former is a build
> > blocker, the latter a critical because fpylll cannot be imported. I think
> > that's it all.
>
> I also get an error at build time, in ratpoints. See #24708.
>
> Best regards,
> Simon
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-release" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-release+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-release@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-release.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [sage-release] Sage 8.2.beta5 released

2018-02-11 Thread Ralf Stephan

Update with clang on Linux: sagelib ignores the --stdlib in CXX (#24705)
and fpylll apparently ignores the --stdlib in CXX and if you give it in the
CXXFLAGS it uses it only for C not C++ (#24707). So the former is a build
blocker, the latter a critical because fpylll cannot be imported. I think
that's it all.

On Sun, Feb 11, 2018 at 8:17 AM François Bissey 
wrote:

>
>
> > On 11/02/2018, at 19:57, François Bissey  wrote:
> >
> >
> >
> >> On 10/02/2018, at 12:07, Justin C. Walker  wrote:
> >>
> >>>
> >>> On Feb 9, 2018, at 00:25 , Volker Braun  wrote:
> >>>
> >>> As always, you can get the latest beta version from the "develop" git
> branch. Alternatively, the self-contained source tarball is at
> http://www.sagemath.org/download-latest.html
> >>
> >> Yay for using clang!
> >>
> >> Built from a fresh clone/checkout of the develop tree.
> >>
> >> The build (macOS 10.11.6, MBP Quad-core Core i7) blows chunks on sqlite:
> >>
> >> ==
> >> libtool: compile:  gcc -DPACKAGE_NAME=\"sqlite\"
> -DPACKAGE_TARNAME=\"sqlite\" -DPACKAGE_VERSION=\"3.17.0\"
> "-DPACKAGE_STRING=\"sqlite 3.17.0\
> >> \"" -DPACKAGE_BUGREPORT=\"http://www.sqlite.org\; -DPACKAGE_URL=\"\"
> -DPACKAGE=\"sqlite\" -DVERSION=\"3.17.0\" -DSTDC_HEADERS=1 -DHAVE_SYS_T\
> >> YPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1
> -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 \
> >> -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\"
> -DHAVE_FDATASYNC=1 -DHAVE_USLEEP=1 -DHAVE_LOCALTIME_R=1 -DHAVE_GMTIME_R=1
> -DHAVE_D\
> >> ECL_STRERROR_R=1 -DHAVE_STRERROR_R=1 -DHAVE_EDITLINE_READLINE_H=1
> -DHAVE_EDITLINE=1 -I. -I/Users/Sage/sage-8.2.beta5/local/include -D_REENTR\
> >> ANT=1 -DSQLITE_THREADSAFE=1 -DSQLITE_ENABLE_FTS3 -DSQLITE_ENABLE_RTREE
> -g -O2 -MT sqlite3.lo -MD -MP -MF .deps/sqlite3.Tpo -c sqlite3.c  -fn\
> >> o-common -DPIC -o .libs/sqlite3.o
> >> sqlite3.c:28836:10: error: use of unknown builtin
> '__builtin_add_overflow' [-Wimplicit-function-declaration]
> >> return __builtin_add_overflow(*pA, iB, pA);
> >>^
> >> ==
> >>
> >> sqlite log attached.
> >
> >
> > Ok figured how that one occurred. Xcode version clang differently from
> linux.
> > sqlite macro evaluate the version with
> > #if defined(__clang__) && !defined(_WIN32) &&
> !defined(SQLITE_DISABLE_INTRINSIC)
> > # define CLANG_VERSION \
> >
> (__clang_major__*100+__clang_minor__*1000+__clang_patchlevel__)
> >
> > with clang 3.8 on linux __clang_major__ is 3 but in Xcode 3.8 it is 8.
> > You can imagine that a test designed to figure that you use clang 4 on
> linux
> > will pass with that version of Xcode.
> > Anyway it is all the wrong way to figure out if you should use the
> builtin.
> > Using
> >
> https://www.gnu.org/software/autoconf-archive/ax_gcc_builtin.html#ax_gcc_builtin
> > is a way better idea but that means touching quite a bit of sqlite3.c
>
> The latest version of sqlite doesn’t try to identify with version of clang
> support
> __builtin_* anymore. I guess they figured out that it was broken.
> I also noticed they figured out they needed to do something about icc.
> They still do it wrong in my opinion, but upgrading should fix the problem.
>
> François
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-release" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-release+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-release@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-release.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [sage-release] Re: Sage 8.2.beta5 released

2018-02-10 Thread Ralf Stephan

You're missing a devel system package. I have it in clang-devel and
libc++-devel.

On Sat, Feb 10, 2018 at 4:41 PM Simon King <simon.k...@uni-jena.de> wrote:

> On 2018-02-10, Ralf Stephan <gtrw...@gmail.com> wrote:
> > The linking error with --stdlib=libc++ persists. It appears ntl_ZZ.so is
> > built with both libstdc++ and libc++:
>
> At least while building, ntl did not complain, see
>   http://users.minet.uni-jena.de/cohomology/logs/ntl-10.3.0.log
>
> However, this time with
>   CC=clang CXX="clang++ --stdlib=libc++" make
> it is brial that's failing to build. See
>   http://users.minet.uni-jena.de/cohomology/logs/brial-1.0.1.p2.log
>
> Best regards,
> Simon
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-release" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-release+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-release@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-release.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [sage-release] Re: Sage 8.2.beta5 released

2018-02-10 Thread Ralf Stephan

The linking error with --stdlib=libc++ persists. It appears ntl_ZZ.so is
built with both libstdc++ and libc++:

ralf@ark:~/sage/pynac> ldd
/home/ralf/sage/local/lib/python2.7/site-packages/sage/libs/ntl/ntl_ZZ.so
linux-vdso.so.1 (0x7ffc8f3f1000)
libntl.so.33 => /home/ralf/sage/local/lib/libntl.so.33 (0x7f823f6d7000)
libgmp.so.23 => /home/ralf/sage/local/lib/libgmp.so.23 (0x7f823f448000)
libm.so.6 => /lib64/libm.so.6 (0x7f823f14b000)
libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x7f823edc2000)
libpython2.7.so.1.0 => /home/ralf/sage/local/lib/libpython2.7.so.1.0
(0x7f823e9d8000)
libpari-gmp-2.10.so.0 => /home/ralf/sage/local/lib/libpari-gmp-2.10.so.0
(0x7f823def9000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x7f823dce2000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x7f823dac5000)
libc.so.6 => /lib64/libc.so.6 (0x7f823d724000)
libgf2x.so.1 => /home/ralf/sage/local/lib/libgf2x.so.1 (0x7f823d501000)
libc++.so.1 => /usr/lib64/libc++.so.1 (0x7f823ff05000)
libc++abi.so.1 => /usr/lib64/libc++abi.so.1 (0x7f823fec2000)
/lib64/ld-linux-x86-64.so.2 (0x7f823fdd6000)
libdl.so.2 => /lib64/libdl.so.2 (0x7f823d2fd000)
libutil.so.1 => /lib64/libutil.so.1 (0x7f823d0fa000)

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

On Sat, Feb 10, 2018 at 3:43 PM Ralf Stephan <gtrw...@gmail.com> wrote:

> Welcome to the bleeding edge. I'm afraid it won't work without
> --stdlib=libc++. Also with that I get a linking error:
>
> Done cleaning.
> Traceback (most recent call last):
>   File "/home/ralf/sage/src/bin/sage-eval", line 4, in 
> from sage.all import *
>   File "/home/ralf/sage/local/lib/python2.7/site-packages/sage/all.py",
> line 93, in 
> from sage.libs.all   import *
>   File
> "/home/ralf/sage/local/lib/python2.7/site-packages/sage/libs/all.py", line
> 3, in 
> import sage.libs.ntl.all as ntl
>   File
> "/home/ralf/sage/local/lib/python2.7/site-packages/sage/libs/ntl/all.py",
> line 24, in 
> from sage.libs.ntl.ntl_ZZ import (
> ImportError:
> /home/ralf/sage/local/lib/python2.7/site-packages/sage/libs/ntl/ntl_ZZ.so:
> undefined symbol: _ZN3NTLlsERSoRKNS_2ZZE
> Sage failed to start up.
>
>
> On Sat, Feb 10, 2018 at 3:23 PM Simon King <simon.k...@uni-jena.de> wrote:
>
>> Hi Ralf,
>>
>> On 2018-02-10, Ralf Stephan <gtrw...@gmail.com> wrote:
>> > Simon do you have libc++ system-installed and given CXX='clang++
>> > --stdlib=libc++' ?
>>
>> No, I followed the previous advice to give CC=clan CXX=clan++.
>>
>> Does that mean I should make distclean and start again from scratch?
>>
>> Best regards,
>> Simon
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "sage-release" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to sage-release+unsubscr...@googlegroups.com.
>> To post to this group, send email to sage-release@googlegroups.com.
>> Visit this group at https://groups.google.com/group/sage-release.
>> For more options, visit https://groups.google.com/d/optout.
>>
>

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

Re: [sage-release] Re: Sage 8.2.beta5 released

2018-02-10 Thread Ralf Stephan

Welcome to the bleeding edge. I'm afraid it won't work without
--stdlib=libc++. Also with that I get a linking error:

Done cleaning.
Traceback (most recent call last):
  File "/home/ralf/sage/src/bin/sage-eval", line 4, in 
from sage.all import *
  File "/home/ralf/sage/local/lib/python2.7/site-packages/sage/all.py",
line 93, in 
from sage.libs.all   import *
  File
"/home/ralf/sage/local/lib/python2.7/site-packages/sage/libs/all.py", line
3, in 
import sage.libs.ntl.all as ntl
  File
"/home/ralf/sage/local/lib/python2.7/site-packages/sage/libs/ntl/all.py",
line 24, in 
from sage.libs.ntl.ntl_ZZ import (
ImportError:
/home/ralf/sage/local/lib/python2.7/site-packages/sage/libs/ntl/ntl_ZZ.so:
undefined symbol: _ZN3NTLlsERSoRKNS_2ZZE
Sage failed to start up.

On Sat, Feb 10, 2018 at 3:23 PM Simon King <simon.k...@uni-jena.de> wrote:

> Hi Ralf,
>
> On 2018-02-10, Ralf Stephan <gtrw...@gmail.com> wrote:
> > Simon do you have libc++ system-installed and given CXX='clang++
> > --stdlib=libc++' ?
>
> No, I followed the previous advice to give CC=clan CXX=clan++.
>
> Does that mean I should make distclean and start again from scratch?
>
> Best regards,
> Simon
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-release" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-release+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-release@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-release.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [sage-release] Re: Sage 8.2.beta5 released

2018-02-10 Thread Ralf Stephan

Simon do you have libc++ system-installed and given CXX='clang++
--stdlib=libc++' ?

On Sat, Feb 10, 2018 at 1:15 PM Simon King  wrote:

> On 2018-02-10, Simon King  wrote:
> > On 2018-02-10, Simon King  wrote:
> >> Hi François,
> >>
> >> On 2018-02-10, François Bissey  wrote:
> >>> I’d recommend to work on a separate clone. It is what I have done
> >>> on my Gentoo linux box.
> >>
> >> This is what I did now. It is still in the process of building.
> >
> > While it was building, I noticed lines such as
> >   [python_openid-2.2.5.p0] Found candidate GCC installation:
> /usr/bin/../lib/gcc/i686-linux-gnu/5.4.0
> >
> > Does that mean python_openid will in fact not be build with clang?
> > Wouldn't that create a mess?
>
> giac fails to build. Log is at
> http://users.minet.uni-jena.de/cohomology/logs/giac-1.4.9.45.p1.log
>
> I also copied the python_openid log, so that you can investigate the
> "candidate GCC installation" thingy:
> http://users.minet.uni-jena.de/cohomology/logs/python_openid-2.2.5.p0.log
> If I understand the log correctly, it is in fact using clang for
> compilation, though.
>
> Best regards,
> Simon
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-release" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-release+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-release@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-release.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [sage-release] Re: Sage 8.2.beta5 released

2018-02-10 Thread Ralf Stephan

FWIW for me as Pynac dev clang has far superior diagnostics and refactoring
tools. From other programs I can confirm a speedup of compiled source of at
least 5%.

On Sat, Feb 10, 2018 at 9:55 AM François Bissey 
wrote:

>
>
> > On 10/02/2018, at 21:44, Simon King  wrote:
> >
> > Hi François,
> >
> > On 2018-02-10, François Bissey  wrote:
> >> Linux support is a side effect. But it helps code portability, while
> >> working on this we found quite a few GNUism here and there.
> >
> > OK, portability is an argument that I understand.
> >
> > What would you recommend me to do in order to give it a try on my ubuntu
> > laptop, so that I can also see how my spkgs (meataxe and
> > p_group_cohomology) are doing with clang? Probably it'd be easiest to
> > create a clone of my current git repository, and thus work with two
> > different installations of Sage, right?
> >
>
> I’d recommend to work on a separate clone. It is what I have done
> on my Gentoo linux box. I don’t know the state of clang on ubuntu
> but it is better to have it configured to use libc++ instead of
> libstdc++ from gcc.
>
> I haven’t build sage’s gcc on my mac laptop on the other hand :)
> It is the other thing, on this little machine it saves a few _hours_
> spent on compiling gcc.
>
> François
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-release" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-release+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-release@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-release.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [sage-release] Sage 8.2.beta5 released

2018-02-09 Thread Ralf Stephan

After building with clang on OpenSuSE two dozen doctests fail, all due to
segfault in linbox:

File "sage/matrix/matrix_modn_sparse.pyx", line 730, in
sage.matrix.matrix_modn_sparse.Matrix_modn_sparse._rank_linbox
(build/cythonized/sage/matrix/matrix_modn_sparse.c:9008)
sig_on()
SignalError: Segmentation fault

The linbox build log is attached but I can see no compile problem. This is
now
https://trac.sagemath.org/ticket/24701

>
>

--
You received this message because you are subscribed to the Google Groups
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.
Found local metadata for linbox-1.5.2
Using cached file /home/ralf/sage/upstream/linbox-1.5.2.tar.gz
linbox-1.5.2

Setting up build directory for linbox-1.5.2
Finished extraction
Applying patches from ../patches...
Applying ../patches/linbox_charpoly_fullCRA.patch
patching file linbox/solutions/charpoly.h

Host system:
Linux ark 4.4.104-39-default #1 SMP Thu Jan 4 08:11:03 UTC 2018 (7db1912) x86_64 x86_64 x86_64 GNU/Linux

C compiler: clang
C compiler version:
clang version 3.8.0 (tags/RELEASE_380/final 262553)
Target: x86_64-unknown-linux-gnu
Thread model: posix
InstalledDir: /usr/bin
Found candidate GCC installation: /usr/bin/../lib64/gcc/x86_64-suse-linux/4.8
Found candidate GCC installation: /usr/bin/../lib64/gcc/x86_64-suse-linux/5
Found candidate GCC installation: /usr/bin/../lib64/gcc/x86_64-suse-linux/6
Found candidate GCC installation: /usr/lib64/gcc/x86_64-suse-linux/4.8
Found candidate GCC installation: /usr/lib64/gcc/x86_64-suse-linux/5
Found candidate GCC installation: /usr/lib64/gcc/x86_64-suse-linux/6
Selected GCC installation: /usr/bin/../lib64/gcc/x86_64-suse-linux/4.8
Candidate multilib: .;@m64
Selected multilib: .;@m64

Configuring linbox-1.5.2
configure: loading site script /usr/share/site/x86_64-unknown-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking for style of include used by make... GNU
checking for gcc... clang
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether clang accepts -g... yes
checking for clang option to accept ISO C89... none needed
checking whether clang understands -c and -o together... yes
checking dependency style of clang... gcc3
checking the archiver (ar) interface... ar
---
checking whether to enable debugging options in the library... no
checking whether to enable profiling everything in the library... no
checking whether to enable warnings when compiling the library... no
---
checking whether we are using the GNU C++ compiler... yes
checking whether clang++ accepts -g... yes
checking dependency style of clang++... gcc3
checking for family name of compiler... clang38
checking whether clang++ supports C++11 features by default... no
checking whether clang++ supports C++11 features with -std=c++11... yes
checking how to run the C++ preprocessor... clang++ -E
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for ANSI C header files... yes
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking how to print strings... printf
checking for a sed that does not truncate output... /usr/bin/sed
checking for fgrep... /usr/bin/grep -F
checking for ld used by clang... ld
checking if the linker (ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking how to convert x86_64-pc-linux-gnu file names to x86_64-pc-linux-gnu format... func_convert_file_noop
checking how to convert x86_64-pc-linux-gnu file names to toolchain format... func_convert_file_noop
checking for ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for

Re: [sage-release] Sage 8.2.beta5 released

2018-02-09 Thread Ralf Stephan

This is now https://trac.sagemath.org/ticket/24696

On Fri, Feb 9, 2018 at 3:35 PM Ralf Stephan <gtrw...@gmail.com> wrote:

> Trying clang on Linux, after make distclean fails in giac but I'm not sure
> if my installation is the reason. TLDR:
> ./index.h:571:11: error: no template named 'hash_map' in namespace 'std';
> did you mean '__gnu_cxx::hash_map'?
>
> giac compile log is attached
>

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

Re: [sage-release] Sage 8.2.beta5 released

2018-02-09 Thread Ralf Stephan

Trying clang on Linux, after make distclean fails in giac but I'm not sure
if my installation is the reason. TLDR:
./index.h:571:11: error: no template named 'hash_map' in namespace 'std';
did you mean '__gnu_cxx::hash_map'?

giac compile log is attached

--
You received this message because you are subscribed to the Google Groups
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.
Found local metadata for giac-1.4.9.45.p1
Using cached file /home/ralf/sage/upstream/giac-1.4.9.45.tar.bz2
giac-1.4.9.45.p1

Setting up build directory for giac-1.4.9.45.p1
Finished extraction
Applying patches from ../patches...
Applying ../patches/alloca.patch
patching file src/gen.cc
patching file src/gen.h
Applying ../patches/dirent.patch
patching file src/help.cc
Applying ../patches/macos-ifactor.patch
patching file src/ifactor.cc
Hunk #1 succeeded at 3746 (offset 9 lines).
Applying ../patches/nofltk-check.patch
patching file check/testgeo
patching file check/TP00-sol.cas
patching file check/TP00-sol.cas.out1
patching file check/TP02-sol.cas
patching file check/TP09-sol.cas
patching file check/TP19-sol.cas
Applying ../patches/sunos_abs.patch
patching file src/rpn.h

Host system:
Linux ark 4.4.104-39-default #1 SMP Thu Jan 4 08:11:03 UTC 2018 (7db1912) x86_64 x86_64 x86_64 GNU/Linux

Configuring giac...
Configuring giac-1.4.9.45.p1
configure: WARNING: you should use --build, --host, --target
configure: loading site script /usr/share/site/x86_64-unknown-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for gcc... clang
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether clang accepts -g... yes
checking for clang option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of clang... gcc3
checking whether ln -s works... yes
checking whether we are using the GNU C++ compiler... yes
checking whether clang++ accepts -g... yes
checking dependency style of clang++... gcc3
checking how to run the C++ preprocessor... clang++ -E
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking for a sed that does not truncate output... /usr/bin/sed
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for fgrep... /usr/bin/grep -F
checking for ld used by clang... ld
checking if the linker (ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking the maximum length of command line arguments... 1572864
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking for ld option to reload object files... -r
checking how to recognize dependent libraries... pass_all
checking for ar... ar
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from clang object... ok
checking how to run the C preprocessor... clang -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h...

Re: [sage-release] Sage 8.2.beta5 released

2018-02-09 Thread Ralf Stephan

So how to use clang on Linux?

On Fri, Feb 9, 2018 at 9:36 AM François Bissey  wrote:

> Note that from this release a fresh build on OS X will use clang.
> Building gcc and using it can be triggered with SAGE_INSTALL_GCC=yes
> as usual.
> Incremental upgrade will continue to use the previously configured
> compiler.
> Feedback on optional packages that are broken by the move appreciated.
>
> François
>
> > On 9/02/2018, at 21:25, Volker Braun  wrote:
> >
> > As always, you can get the latest beta version from the "develop" git
> branch. Alternatively, the self-contained source tarball is at
> http://www.sagemath.org/download-latest.html
> >
> > e6cae6d88d (tag: 8.2.beta5, trac/develop) Updated SageMath version to
> 8.2.beta5
> > 9dd4282d36 Trac #24660: Memory leak in SubgraphSearch
> > b9aa268ecd Trac #24639: Enumerating greedy linear extensions
> > c795e950c9 Trac #24636: Rivin's test for circumcribability and
> inscribability
> > d70b6a253a Trac #24629: fix R build on Solaris 11
> > 4f53f24d1f Trac #24628: Build PCRE without JIT if needed
> > 867f4c9761 Trac #24618: fplll fails to build on SunOS
> > 92ac632d04 Trac #24611: Singular fails to build on SunOS
> > ac14d82c6f Trac #24590: bug in inverse_image of module homomorphism
> > 38e8a65eec Trac #24313: py3: fixes to sage.misc.temporary_file
> > b899601826 Trac #24239: Implement soliton cellular automata
> > 7d0ca44142 Trac #24139: Allow baseline to be given as part of ascii_art
> and unicode_art
> > 94da5b67c1 Trac #24656: Fix bug in type E bijection from cythonizing
> RiggedPartition
> > e8c626f7da Trac #24615: interface libgap floats
> > 9c146ffcb2 Trac #24608: Remove deprecated PowerSeries._floordiv_
> > 6b689d3bfa Trac #23978: Rich comparison for Modules
> > 70c254125d Trac #24634: add .is_polyhedral method to graphs
> > 2d1615636e Trac #24175: Optimizations to generating rigged configurations
> > 7be8a667e9 Trac #24141: Optimizations to Kleber tree
> > 8a2e3ed425 Trac #24035: Normal forms for TorsionQuadraticModules
> > 9b223d74de Trac #24633: Add jump count for a linear extension
> > 0da6392254 Trac #24632: Add is_greedy() to linear extension.
> > e185837226 Trac #24631: Faster jump number for posets
> > 4387613c32 Trac #24619: giac fails to build on SunOS
> > 58fdd676a4 Trac #24516: Cygwin test failures in lseries_ell
> > ab3c1c8da7 Trac #24411: Move gamma functions into their own file
> > 79f648c706 Trac #23714: GAP matrices
> > 295b129a35 Trac #22921: Implementation of shifted tableaux
> > c5248314f7 Trac #24625: Some small improvements to polynomial_complex_arb
> > d842b25062 Trac #24624: Stop using new_t_POL_from_int_star from cypari2
> > 75e3f2960a Trac #24617: Infinite process recursion with Solaris make
> > bb2b730403 Trac #24614: Deprecate args of Parent_old.__init__
> > 505af6e57c Trac #24613: Remove actions from old coercion model
> > b200dbae27 Trac #24610: Change richcmp() to a cpdef inline function
> > 2a71f44dae Trac #24607: Add abstract _add_ and _mul_ methods to
> RingElement
> > 6296a31f22 Trac #24606: Forgotten check_error in maxima spkg-install
> > f5259142ff Trac #24602: upgrade iconv to 1.15
> > e7fe097bf3 Trac #24597: Properly set LD_LIBRARY_PATH in spkg-build for
> python2/3 on SunOS
> > 69951df4c2 Trac #24584: Add the power poset
> > 8e3fde343d Trac #24431: Fix coercions and pushout for Laurent series
> > f313460743 Trac #24381: New Parent method _convert_method_map
> > 9f2efaef78 Trac #24357: Two bugs in NumberField.composite_fields()
> > 56c322343a Trac #24223: py3: several string conversion fixes
> > b79f27f2c6 Trac #24071: Improve docstring of
> MPolynomial_libsingular.reduce()
> > 950bdd8145 Trac #23696: Update matplotlib to 2.1.0
> > 36849d6c3e Trac #22928: Conversion between gmpy2 and sage objects
> > 5473d304bb Trac #5574: Implement QQbar^QQ as action
> > 129faa0c39 Trac #24599: Internal compiler error when compiling
> giac-1.4.9.45 with gcc-7.2.0
> > 07f53b23c4 Trac #24600: another typo ticket
> > 52cd6b86d0 Trac #24563: Workaround for small race condition in parallel
> doctest runner
> > 80fecaaf95 Trac #24418: Doctest: bug
> numerical_approx(2^(450232897/4888643760))
> > 919ef40bb8 Trac #21092: Unhandled case in EllipticCurve_from_cubic
> > a3ee07f891 Trac #12426: Make Sage build with clang (3.7+) and make it
> the default on OS X
> > ed50684b29 Trac #24517: random failure in sage/geometry/cone.py
> > 0a674fd488 (tag: 8.2.beta4) Updated SageMath version to 8.2.beta4
> >
> >
> > --
> > You received this message because you are subscribed to the Google
> Groups "sage-release" group.
> > To unsubscribe from this group and stop receiving emails from it, send
> an email to sage-release+unsubscr...@googlegroups.com.
> > To post to this group, send email to sage-release@googlegroups.com.
> > Visit this group at https://groups.google.com/group/sage-release.
> > For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are

Re: [sage-release] Sage 8.2.beta4 released

2018-01-28 Thread Ralf Stephan

I confirm that reinstalling internal gcc with 'sage -f gcc' makes giac
compile without error.

On Sun, Jan 28, 2018 at 8:53 AM Ralf Stephan <gtrw...@gmail.com> wrote:

> That rather points to mpfr as the culprit IMHO.
>
> On Sun, Jan 28, 2018 at 8:43 AM François Bissey <frp.bis...@gmail.com>
> wrote:
>
>> Interesting question and I don’t know. I only know that the failure comes
>> from mpfr_assert_fail in mpfr-3 code as indicated by your log.
>> What else, there was a change of soname which means that there are
>> incompatibilities
>> between mpfr-3 and mpfr-4 and that is probably at play here.
>> None of the other standard packages using mpfr trigger an ICE under the
>> same condition
>> (the only package for which I don’t know for sure is sage itself because
>> you have to
>> rebuild giac first). So I think giac may be using some mpfr construct
>> improperly or some
>> that should be private.
>>
>> François
>>
>> > On 28/01/2018, at 20:32, Ralf Stephan <gtrw...@gmail.com> wrote:
>> >
>> > How can an internal compiler error have some other source code as root
>> cause?
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "sage-release" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to sage-release+unsubscr...@googlegroups.com.
>> To post to this group, send email to sage-release@googlegroups.com.
>> Visit this group at https://groups.google.com/group/sage-release.
>> For more options, visit https://groups.google.com/d/optout.
>>
>

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

Re: [sage-release] Sage 8.2.beta4 released

2018-01-27 Thread Ralf Stephan

That rather points to mpfr as the culprit IMHO.

On Sun, Jan 28, 2018 at 8:43 AM François Bissey <frp.bis...@gmail.com>
wrote:

> Interesting question and I don’t know. I only know that the failure comes
> from mpfr_assert_fail in mpfr-3 code as indicated by your log.
> What else, there was a change of soname which means that there are
> incompatibilities
> between mpfr-3 and mpfr-4 and that is probably at play here.
> None of the other standard packages using mpfr trigger an ICE under the
> same condition
> (the only package for which I don’t know for sure is sage itself because
> you have to
> rebuild giac first). So I think giac may be using some mpfr construct
> improperly or some
> that should be private.
>
> François
>
> > On 28/01/2018, at 20:32, Ralf Stephan <gtrw...@gmail.com> wrote:
> >
> > How can an internal compiler error have some other source code as root
> cause?
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-release" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-release+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-release@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-release.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [sage-release] Sage 8.2.beta4 released

2018-01-27 Thread Ralf Stephan

How can an internal compiler error have some other source code as root
cause?

On Sun, Jan 28, 2018 at 8:30 AM François Bissey <frp.bis...@gmail.com>
wrote:

> I made some comments in the ticket. In my initial answer I assumed you were
> using the host gcc rather than sage’s one. But I wouldn’t be surprised if
> there
> was a problem when using a host gcc compiled against mpfr-3.x.
> This needs to be tested.
> While rebuilding gcc get rid of the ICE, I think the root cause of the
> problem is
> in giac. It is the only package that gives ICE after mpfr upgrade as far
> as I know.
> All the other packages that depend on mpfr in sage don’t give rise to that
> error.
>
> François
>
> > On 28/01/2018, at 20:19, Ralf Stephan <gtrw...@gmail.com> wrote:
> >
> > Doesn't this simply make internal gcc a dependency? If so then is it
> enough to change that for the above ticket?
> >
> > On Sun, Jan 28, 2018 at 8:17 AM Ralf Stephan <gtrw...@gmail.com> wrote:
> > This is https://trac.sagemath.org/ticket/24599
> > I'm trying now with the system gcc.
> >
> > On Sun, Jan 28, 2018 at 8:09 AM François Bissey <frp.bis...@gmail.com>
> wrote:
> > I was going to warn sage-on-gentoo users on this interesting fact that I
> experienced
> > on the experimental branch where I track stuff that Volker merges.
> > It is probably an issue in giac, but at the end of the day gcc needs to
> be rebuilt
> > after mpfr/mpc. I didn’t think about the problem of what happens when
> you use
> > the host gcc in vanilla sage though.
> > You may have to build sage’s gcc - or use clang once support is merged :)
> >
> > François
> >
> > > On 28/01/2018, at 20:02, Ralf Stephan <gtrw...@gmail.com> wrote:
> > >
> > > Compiling giac with the gcc installed by Sage (7.2.0) gives an
> internal compiler error:
> > > libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I.. -DIN_GIAC -I. -I.. -I.
> -I.. -I/h
> > > ome/ralf/sage/local/include -g -O2 -I/home/ralf/sage/local/include
> -I/home/ralf/
> > > sage/local/include -fno-strict-aliasing -DGIAC_GENERIC_CONSTANTS -MT
> solve.lo -M
> > > D -MP -MF .deps/solve.Tpo -c solve.cc  -fPIC -DPIC -o .libs/solve.o
> > > libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I.. -DIN_GIAC -I. -I.. -I.
> -I.. -I/h
> > > ome/ralf/sage/local/include -g -O2 -I/home/ralf/sage/local/include
> -I/home/ralf/
> > > sage/local/include -fno-strict-aliasing -DGIAC_GENERIC_CONSTANTS -MT
> derive.lo -
> > > MD -MP -MF .deps/derive.Tpo -c derive.cc -o derive.o >/dev/null 2>&1
> > > init2.c:52: MPFR assertion failed: p >= 2 && p <=
> ((mpfr_prec_t)((mpfr_uprec_t)(
> > > ~(mpfr_uprec_t)0)>>1))
> > > modpoly.cc: In function 'std::complex
> giac::horner_newton(const vecteur&
> > > , const std::complex&, const giac::context*)':
> > > modpoly.cc:5035:19: internal compiler error: Aborted
> > >complex horner_newton(const vecteur & p,const
> std::complex 
> > > ,GIAC_CONTEXT){
> > >^
> > > 0xafbc6f crash_signal
> > > ../../src/gcc/toplev.c:337
> > > 0x7f3e0cfeedd3 mpfr_assert_fail
> > >
>  /home/ralf/sage/local/var/tmp/sage/build/mpfr-3.1.5.p0/src/src/mpfr-gmp.
> > > c:305
> > > 0x7f3e0cfe59c1 mpfr_init2
> > >
>  /home/ralf/sage/local/var/tmp/sage/build/mpfr-3.1.5.p0/src/src/init2.c:5
> > > 2
> > > 0x7f3e0d21b472 mpc_div_zero
> > >
>  /home/ralf/sage/local/var/tmp/sage/build/mpc-1.1.0/src/src/div.c:31
> > > 0x7f3e0d21b472 mpc_div
> > >
>  /home/ralf/sage/local/var/tmp/sage/build/mpc-1.1.0/src/src/div.c:257
> > > 0x77b6b9 do_mpc_arg2(tree_node*, tree_node*, tree_node*, int, int
> (*)(__mpc_stru
> > > ct*, __mpc_struct const*, __mpc_struct const*, int))
> > > ../../src/gcc/builtins.c:10179
> > > 0x8afa0a const_binop
> > > ../../src/gcc/fold-const.c:1316
> > > 0x8b0c5e const_binop(tree_code, tree_node*, tree_node*, tree_node*)
> > > ../../src/gcc/fold-const.c:1565
> > > 0xdb4962 gimple_resimplify2(gimple**, code_helper*, tree_node*,
> tree_node**, tre
> > > e_node* (*)(tree_node*))
> > > ../../src/gcc/gimple-match-head.c:132
> > > 0xe384b0 gimple_simplify(gimple*, code_helper*, tree_node**, gimple**,
> tree_node
> > > * (*)(tree_node*), tree_node* (*)(tree_node*))
> > > ../../src/gcc/gimple-match-head.c:642
> > > 0x8e4306 fold_stmt_1
> > > ../../src/gcc/gimple-fold.c:4362
> > &

Re: [sage-release] Sage 8.2.beta4 released

2018-01-27 Thread Ralf Stephan

Doesn't this simply make internal gcc a dependency? If so then is it enough
to change that for the above ticket?

On Sun, Jan 28, 2018 at 8:17 AM Ralf Stephan <gtrw...@gmail.com> wrote:

> This is https://trac.sagemath.org/ticket/24599
> I'm trying now with the system gcc.
>
> On Sun, Jan 28, 2018 at 8:09 AM François Bissey <frp.bis...@gmail.com>
> wrote:
>
>> I was going to warn sage-on-gentoo users on this interesting fact that I
>> experienced
>> on the experimental branch where I track stuff that Volker merges.
>> It is probably an issue in giac, but at the end of the day gcc needs to
>> be rebuilt
>> after mpfr/mpc. I didn’t think about the problem of what happens when you
>> use
>> the host gcc in vanilla sage though.
>> You may have to build sage’s gcc - or use clang once support is merged :)
>>
>> François
>>
>> > On 28/01/2018, at 20:02, Ralf Stephan <gtrw...@gmail.com> wrote:
>> >
>> > Compiling giac with the gcc installed by Sage (7.2.0) gives an internal
>> compiler error:
>> > libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I.. -DIN_GIAC -I. -I.. -I.
>> -I.. -I/h
>> > ome/ralf/sage/local/include -g -O2 -I/home/ralf/sage/local/include
>> -I/home/ralf/
>> > sage/local/include -fno-strict-aliasing -DGIAC_GENERIC_CONSTANTS -MT
>> solve.lo -M
>> > D -MP -MF .deps/solve.Tpo -c solve.cc  -fPIC -DPIC -o .libs/solve.o
>> > libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I.. -DIN_GIAC -I. -I.. -I.
>> -I.. -I/h
>> > ome/ralf/sage/local/include -g -O2 -I/home/ralf/sage/local/include
>> -I/home/ralf/
>> > sage/local/include -fno-strict-aliasing -DGIAC_GENERIC_CONSTANTS -MT
>> derive.lo -
>> > MD -MP -MF .deps/derive.Tpo -c derive.cc -o derive.o >/dev/null 2>&1
>> > init2.c:52: MPFR assertion failed: p >= 2 && p <=
>> ((mpfr_prec_t)((mpfr_uprec_t)(
>> > ~(mpfr_uprec_t)0)>>1))
>> > modpoly.cc: In function 'std::complex giac::horner_newton(const
>> vecteur&
>> > , const std::complex&, const giac::context*)':
>> > modpoly.cc:5035:19: internal compiler error: Aborted
>> >complex horner_newton(const vecteur & p,const
>> std::complex 
>> > ,GIAC_CONTEXT){
>> >^
>> > 0xafbc6f crash_signal
>> > ../../src/gcc/toplev.c:337
>> > 0x7f3e0cfeedd3 mpfr_assert_fail
>> >
>>  /home/ralf/sage/local/var/tmp/sage/build/mpfr-3.1.5.p0/src/src/mpfr-gmp.
>> > c:305
>> > 0x7f3e0cfe59c1 mpfr_init2
>> >
>>  /home/ralf/sage/local/var/tmp/sage/build/mpfr-3.1.5.p0/src/src/init2.c:5
>> > 2
>> > 0x7f3e0d21b472 mpc_div_zero
>> >
>>  /home/ralf/sage/local/var/tmp/sage/build/mpc-1.1.0/src/src/div.c:31
>> > 0x7f3e0d21b472 mpc_div
>> >
>>  /home/ralf/sage/local/var/tmp/sage/build/mpc-1.1.0/src/src/div.c:257
>> > 0x77b6b9 do_mpc_arg2(tree_node*, tree_node*, tree_node*, int, int
>> (*)(__mpc_stru
>> > ct*, __mpc_struct const*, __mpc_struct const*, int))
>> > ../../src/gcc/builtins.c:10179
>> > 0x8afa0a const_binop
>> > ../../src/gcc/fold-const.c:1316
>> > 0x8b0c5e const_binop(tree_code, tree_node*, tree_node*, tree_node*)
>> > ../../src/gcc/fold-const.c:1565
>> > 0xdb4962 gimple_resimplify2(gimple**, code_helper*, tree_node*,
>> tree_node**, tre
>> > e_node* (*)(tree_node*))
>> > ../../src/gcc/gimple-match-head.c:132
>> > 0xe384b0 gimple_simplify(gimple*, code_helper*, tree_node**, gimple**,
>> tree_node
>> > * (*)(tree_node*), tree_node* (*)(tree_node*))
>> > ../../src/gcc/gimple-match-head.c:642
>> > 0x8e4306 fold_stmt_1
>> > ../../src/gcc/gimple-fold.c:4362
>> > 0xbdb5ff execute
>> > ../../src/gcc/tree-ssa-forwprop.c:2391
>> > Please submit a full bug report,
>> > with preprocessed source if appropriate
>> >
>> > The complete log is attached. System is OpenSuSE 42.3.
>> >
>> > On Sun, Jan 28, 2018 at 1:08 AM Volker Braun <vbraun.n...@gmail.com>
>> wrote:
>> > As always, you can get the latest beta version from the "develop" git
>> branch. Alternatively, the self-contained source tarball is at
>> http://www.sagemath.org/download-latest.html
>> >
>> > 0a674fd488 (tag: 8.2.beta4, trac/develop) Updated SageMath version to
>> 8.2.beta4
>> > 4d966299d9 Trac #24581: more typos
>> > 59b6f2aff8 Trac #24580: some typos (various)
>> > 3e3b72af47

Re: [sage-release] Sage 8.2.beta4 released

2018-01-27 Thread Ralf Stephan

This is https://trac.sagemath.org/ticket/24599
I'm trying now with the system gcc.

On Sun, Jan 28, 2018 at 8:09 AM François Bissey <frp.bis...@gmail.com>
wrote:

> I was going to warn sage-on-gentoo users on this interesting fact that I
> experienced
> on the experimental branch where I track stuff that Volker merges.
> It is probably an issue in giac, but at the end of the day gcc needs to be
> rebuilt
> after mpfr/mpc. I didn’t think about the problem of what happens when you
> use
> the host gcc in vanilla sage though.
> You may have to build sage’s gcc - or use clang once support is merged :)
>
> François
>
> > On 28/01/2018, at 20:02, Ralf Stephan <gtrw...@gmail.com> wrote:
> >
> > Compiling giac with the gcc installed by Sage (7.2.0) gives an internal
> compiler error:
> > libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I.. -DIN_GIAC -I. -I.. -I.
> -I.. -I/h
> > ome/ralf/sage/local/include -g -O2 -I/home/ralf/sage/local/include
> -I/home/ralf/
> > sage/local/include -fno-strict-aliasing -DGIAC_GENERIC_CONSTANTS -MT
> solve.lo -M
> > D -MP -MF .deps/solve.Tpo -c solve.cc  -fPIC -DPIC -o .libs/solve.o
> > libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I.. -DIN_GIAC -I. -I.. -I.
> -I.. -I/h
> > ome/ralf/sage/local/include -g -O2 -I/home/ralf/sage/local/include
> -I/home/ralf/
> > sage/local/include -fno-strict-aliasing -DGIAC_GENERIC_CONSTANTS -MT
> derive.lo -
> > MD -MP -MF .deps/derive.Tpo -c derive.cc -o derive.o >/dev/null 2>&1
> > init2.c:52: MPFR assertion failed: p >= 2 && p <=
> ((mpfr_prec_t)((mpfr_uprec_t)(
> > ~(mpfr_uprec_t)0)>>1))
> > modpoly.cc: In function 'std::complex giac::horner_newton(const
> vecteur&
> > , const std::complex&, const giac::context*)':
> > modpoly.cc:5035:19: internal compiler error: Aborted
> >complex horner_newton(const vecteur & p,const
> std::complex 
> > ,GIAC_CONTEXT){
> >^
> > 0xafbc6f crash_signal
> > ../../src/gcc/toplev.c:337
> > 0x7f3e0cfeedd3 mpfr_assert_fail
> >
>  /home/ralf/sage/local/var/tmp/sage/build/mpfr-3.1.5.p0/src/src/mpfr-gmp.
> > c:305
> > 0x7f3e0cfe59c1 mpfr_init2
> >
>  /home/ralf/sage/local/var/tmp/sage/build/mpfr-3.1.5.p0/src/src/init2.c:5
> > 2
> > 0x7f3e0d21b472 mpc_div_zero
> >
>  /home/ralf/sage/local/var/tmp/sage/build/mpc-1.1.0/src/src/div.c:31
> > 0x7f3e0d21b472 mpc_div
> >
>  /home/ralf/sage/local/var/tmp/sage/build/mpc-1.1.0/src/src/div.c:257
> > 0x77b6b9 do_mpc_arg2(tree_node*, tree_node*, tree_node*, int, int
> (*)(__mpc_stru
> > ct*, __mpc_struct const*, __mpc_struct const*, int))
> > ../../src/gcc/builtins.c:10179
> > 0x8afa0a const_binop
> > ../../src/gcc/fold-const.c:1316
> > 0x8b0c5e const_binop(tree_code, tree_node*, tree_node*, tree_node*)
> > ../../src/gcc/fold-const.c:1565
> > 0xdb4962 gimple_resimplify2(gimple**, code_helper*, tree_node*,
> tree_node**, tre
> > e_node* (*)(tree_node*))
> > ../../src/gcc/gimple-match-head.c:132
> > 0xe384b0 gimple_simplify(gimple*, code_helper*, tree_node**, gimple**,
> tree_node
> > * (*)(tree_node*), tree_node* (*)(tree_node*))
> > ../../src/gcc/gimple-match-head.c:642
> > 0x8e4306 fold_stmt_1
> > ../../src/gcc/gimple-fold.c:4362
> > 0xbdb5ff execute
> > ../../src/gcc/tree-ssa-forwprop.c:2391
> > Please submit a full bug report,
> > with preprocessed source if appropriate
> >
> > The complete log is attached. System is OpenSuSE 42.3.
> >
> > On Sun, Jan 28, 2018 at 1:08 AM Volker Braun <vbraun.n...@gmail.com>
> wrote:
> > As always, you can get the latest beta version from the "develop" git
> branch. Alternatively, the self-contained source tarball is at
> http://www.sagemath.org/download-latest.html
> >
> > 0a674fd488 (tag: 8.2.beta4, trac/develop) Updated SageMath version to
> 8.2.beta4
> > 4d966299d9 Trac #24581: more typos
> > 59b6f2aff8 Trac #24580: some typos (various)
> > 3e3b72af47 Trac #24592: "./sage -f" should clean first before building
> the toolchain
> > e486b8d5b7 Trac #24586: packages whose type is "script" must have
> executable spkg-install
> > dfa00046c8 Trac #24579: Don't install gfortran by default
> > 9396336c09 Trac #24570: py3: using the new tags py3 and py2 in some rst
> files
> > d6c9aed908 Trac #24566: BooleanFunction evaluated on Integer computes
> IndexError wrongly
> > cb4e6a68ce Trac #24548: py3: various details
> > d54fe681fd Trac #24487: add one example with picture to

Re: [sage-release] Re: Sage 8.2.beta3 released

2018-01-20 Thread Ralf Stephan

Never mind, there was an isympy process taking it all, sorry for the noise.

On Sat, Jan 20, 2018 at 5:25 PM Ralf Stephan <gtrw...@gmail.com> wrote:

> I'm getting this on startup:
>   ***   Warning: not enough memory, new stack 4470525952
>   ***   Warning: not enough memory, new stack 2235265024
>   ***   Warning: not enough memory, new stack 1117634560
>   ***   Warning: not enough memory, new stack 558817280
>
> Everything else is normal. I have 32GB of memory and top shows chromium as
> my biggest process with 1% of mem. Anyone seen that too?
>
> On Fri, Jan 19, 2018 at 1:23 PM Eric Gourgoulhon <egourgoul...@gmail.com>
> wrote:
>
>> On Ubuntu 16.04 running on Intel Core i7-6700HQ + 16 GB RAM, from a fresh
>> git clone + pull develop, parallel (-j8) build OK but make ptestlong failed
>> with
>>
>> --
>> sage -t --long --warn-long 75.5 src/sage/coding/linear_code.py  # Timed
>> out
>> --
>>
>> However, the test is passed when run standalone.
>>
>>
>> Eric.
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "sage-release" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to sage-release+unsubscr...@googlegroups.com.
>> To post to this group, send email to sage-release@googlegroups.com.
>> Visit this group at https://groups.google.com/group/sage-release.
>> For more options, visit https://groups.google.com/d/optout.
>>
>

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

Re: [sage-release] Re: Sage 8.2.beta3 released

2018-01-20 Thread Ralf Stephan

I'm getting this on startup:
  ***   Warning: not enough memory, new stack 4470525952
  ***   Warning: not enough memory, new stack 2235265024
  ***   Warning: not enough memory, new stack 1117634560
  ***   Warning: not enough memory, new stack 558817280

Everything else is normal. I have 32GB of memory and top shows chromium as
my biggest process with 1% of mem. Anyone seen that too?

On Fri, Jan 19, 2018 at 1:23 PM Eric Gourgoulhon 
wrote:

> On Ubuntu 16.04 running on Intel Core i7-6700HQ + 16 GB RAM, from a fresh
> git clone + pull develop, parallel (-j8) build OK but make ptestlong failed
> with
>
> --
> sage -t --long --warn-long 75.5 src/sage/coding/linear_code.py  # Timed out
> --
>
> However, the test is passed when run standalone.
>
>
> Eric.
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-release" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-release+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-release@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-release.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [sage-release] Re: Sage 8.2.beta1 released

2017-12-29 Thread Ralf Stephan

I get

sage: Matrix(ZZ, sys.maxsize, sys.maxsize)
Exception (FLINT memory_manager). Unable to allocate memory.
RuntimeError: FLINT exception

Seems signals are not caught on your system?

On Sat, Dec 30, 2017 at 7:11 AM Dima Pasechnik  wrote:

> I am getting a segfault in sage/matrix/matrix_integer_dense.pyx
> namely, at line 222. This also crashes at the console:
>
> sage: Matrix(ZZ, sys.maxsize, sys.maxsize)
> *** Error in `python': free(): invalid size: 0x04888190 ***
> 
> Segmentation fault
>
> (sometimes it just hands, after printing "*** Error in...")
>
> So this looks like a python problem, perhaps due to a new glibc - version
> 2.26
> or relatively new Linux kernel: Linux hilbert 4.14.3-gentoo #3 SMP Thu Dec
> 7 14:37:12 GMT 2017 x86_64 Intel(R) Core(TM) i7-6600U CPU @ 2.60GHz
> GenuineIntel GNU/Linux
>
>
>
>
> On Friday, December 22, 2017 at 11:52:36 PM UTC, Volker Braun wrote:
>>
>> As always, you can get the latest beta version from the "develop" git
>> branch. Alternatively, the self-contained source tarball is at
>> http://www.sagemath.org/download-latest.html
>>
>> d3b9b396c1 (tag: 8.2.beta1, trac/develop) Updated SageMath version to
>> 8.2.beta1
>> 348432f726 Trac #24372: Map._extra_slots(): do not pass dict
>> 67c266feea Trac #24364: Perfectness of B^{r,s} in type
>> A_{2n}^{(2)\dagger} is wrong
>> 900d9bcb86 Trac #24348: Don't initialize _element_constructor in
>> Parent.__call__
>> f1a9b2212f Trac #24344: Implement twisted Q-systems
>> fe483df6c3 Trac #24292: py3: minor fixes to sage.misc.cachefunc
>> bbc77a7199 Trac #24115: Remove ContinuedFractionField
>> 11a039e01a Trac #23008: floor of NumberFieldElement_quadratic broken
>> 8ea1468403 Trac #13552: finite_class.py derived from deprecated
>> Combinatorial Class has no comment
>> 09881fd01d Trac #7302: Nowhere zero flow
>> 7beb97cb97 Trac #24396: test failure in
>> manifolds/differentiable/tensorfield.py (8.2.beta0)
>> 4fce8f1130 Trac #24376: Upgrade notedown
>> f08412d9cf Trac #24284: Exclude some functions with arg restrictions from
>> random testing
>> 88293a407b Trac #24380: sympy misbehavoir
>> ccfe402386 Trac #24363: Deprecate
>> _populate_coercion_lists_(element_constructor=...)
>> 199fa3cc1a Trac #24350: SageObject.__repr__(): fall back to base class
>> 3d8fadbf20 Trac #24337: Remove the pickle jar
>> e6fb1cf2a4 Trac #24329: Upgrade to pynac-0.7.14
>> 23afee8381 Trac #24326: TamariIntervalPosets: failing tests in options
>> b56f7ede5c Trac #24315: dancing links: find all solutions using given
>> rows + find first solution in parallel + doc
>> 63b1669f17 Trac #24028: Held definite integrals don't translate to SymPy
>> e70eba2aa2 Trac #23706: allow several implementations of matrices in
>> MatrixSpace
>> d18747bbdf Trac #24375: Fix deprecation of sage.matrix.matrix
>> a9c87d528c Trac #23568: Improve crochemore factorization for word
>> 0d77e218d3 Trac #24164: adding two links to pari documentation
>> 72232615a8 Trac #22312: Eulerian numbers versus Euler numbers in
>> documentation.
>> e9d3f60263 Trac #24342: minor tweaks on dyck words
>> 3077080046 <(307)%20708-0046> Trac #24305: add some missing blank lines
>> after EXAMPLES::
>> 212f470b4d Trac #24294: py3: minor fix to sage.categories.additive_magmas
>> 5ded0966d7 Trac #24291: py3: minor fixes to sage.misc.sage_timeit
>> 78fae1a6d5 Trac #24273: some care for blocks
>> 0b89094818 Trac #24272: py3: replace various instances of deprecated
>> TestCase methods.
>> 20a302b62c Trac #22976: Characteristic polynomial documentation
>> 36b819af36 Trac #24266: some care for broken links to references
>> acbee6d683 Trac #24226: various typos in the word initial
>> b9a28d7f2f Trac #24195: Construction of an extension of a finite field
>> should also create a coercion map
>> ebdee7af02 Trac #24170: Extend vector_space method to arbitrary subfields
>> aee4d262e0 Trac #24163: blocks_and_cut_vertices() for disconnected graphs
>> d82ce2dd35 Trac #24158: Remove function deprecated in #17449
>> 0cfe9fdac9 Trac #24157: Remove a deprecation from graphs
>> 73e046c100 Trac #19169: Create has_cm() function for modular forms
>> 6ce5d49e1e Trac #8550: Infinite matrix groups over QQ fail for is_finite()
>> 79e580fe96 Trac #24366: fix issue with graph orientations
>> 4ad53ce6a0 Trac #24277: Define one() as alias of identity() in homsets
>> d669628cf8 Trac #24260: Deprecate str ^ Integer
>> 02da33a404 Trac #23891: Permutation.descents does not take an index_set
>> argument
>> e014beab61 Trac #22264: Improve Sandpiles thematic tutorial
>> fe77339278 Trac #20584: Regular partitions: 1-regular partitions are
>> mishandled on occasion
>> 036db7311d Trac #24362: numpy fails to build when MKLROOT environment
>> variable is set
>> 8d9c008a75 (tag: 8.2.beta0) Updated SageMath version to 8.2.beta0
>>
>> --
> You received this message because you are subscribed to the Google Groups
> "sage-release" group.
> To

[sage-release] Re: Sage 8.1.rc4 released

2017-12-03 Thread Ralf Stephan

What could be the reason that for me the mirror search shows >5s ping for 
many mirrors, also for switch.ch which is always 20ms from here (and a 
manual ping confirms this)?

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

Re: [sage-release] Sage 8.1.beta8 released

2017-10-17 Thread Ralf Stephan

The package can be downloaded manually at
http://webusers.imj-prg.fr/~frederic.han/xcas/giacpy/sage/giacpy_sage-0.6.6.tar.gz
That's the link given in https://trac.sagemath.org/ticket/23976

On Tue, Oct 17, 2017 at 3:32 PM Ralf Stephan <gtrw...@gmail.com> wrote:

> Error downloading giacpy_sage-0.6.6.tar.gz
> The servers only have the previous 0.6 version.
>
> On Tue, Oct 17, 2017 at 8:56 AM Volker Braun <vbraun.n...@gmail.com>
> wrote:
>
>> As always, you can get the latest beta version from the "develop" git
>> branch. Alternatively, the self-contained source tarball is at
>> http://www.sagemath.org/download-latest.html
>>
>> a2e82e15a2 (HEAD -> develop, tag: 8.1.beta8, trac/develop) Updated
>> SageMath version to 8.1.beta8
>> 7dc7c74d76 Trac #23872: Singular expansion for implicitly defined function
>> 71c53d6efc Trac #23844: GapElement.__contains__ (from libgap) should use
>> the infix `in` from gap
>> 03398aa3f4 Trac #23818: py3: hash for complex interval fields
>> 756c0ec447 Trac #23671: hypergeometric motives
>> e7b4f77db7 Trac #22922: Faster implementation of LLT polynomials
>> 8d71436074 Trac #20762: Several additional methods for SimplicialComplex
>> 37b5b2cfd2 Trac #18236: support xz compressed tarballs
>> 202fa8dd8c Trac #24020: Cygwin: misc test failures
>> a56746c985 Trac #23922: Upgrade eclib to compile with xcode 9
>> 1472db0a6b Trac #23985: rst2ipynb causes doctest failures if pandoc is
>> not installed
>> 067b87c610 Trac #23983: dot2tex breaks docbuild
>> 11c3bcca4e Trac #23979: Ignore failure in setrlimit on Cygwin
>> e96397a071 Trac #23973: doc build hangs on Cygwin
>> c249d236cb Trac #22461: Implement cython() using cythonize()
>> 50670a7181 Trac #7516: bug in pickling quotient module over pid
>> fce8fd00d4 Trac #23997: installed_packages(False) gives wrong version for
>> Python packages with patches
>> cc5307 Trac #23976: giacpy_sage causes doctest failures due to
>> threading
>> a22a806a2d Trac #23975: sage-location: do not remove .pyc files
>> 2c6ac6c343 Trac #23970: Simpler caching in ell_rational_field
>> cda826dfaf Trac #23966: Conversion from ZpFM to its fraction field
>> incorrect
>> 4bce0bfd2d Trac #23965: Coercion to fraction field is injective
>> c3b1b7780a Trac #23862: speed_up_left_and_right_key
>> a1b45bb7c4 Trac #23839: Fix reference manual index for partn_ref
>> 1b74aa24b0 Trac #23634: A base class for integral quadratic forms seen as
>> modules with a bilinear form.
>> 9659a399eb Trac #18395: (moderate) Speedup in layout_spring
>> c4aef0e21f Trac #23962: rank() of elliptic curves should always consult
>> Cremona database
>> 78a2ebd287 Trac #23957: gmpy2 causes doctest failures
>> 7d5784f2a9 Trac #23947: Reciprocal transformation and trace polynomial
>> e5cb49e05c Trac #23800: Add O method for Laurent series rings
>> 0e98d937dc Trac #23963: py3: richcmp for function field ideals
>> 380c526205 Trac #23951: fix rotate and conjugate in growth diagrams
>> 639646985c Trac #23905: Avoid _element_constructor in Homset
>> a5eeff69d2 Trac #23949: py3 : some work on __cmp__ and richcmp
>> b580a4c279 Trac #23929: Upgrade to cypari2 version 1.1.3
>> 894facd65a Trac #23912: parent() is slow for non-Elements
>> bda5b4d10b Trac #23925: Bulk fix of signal handling in symbolics
>> 68cb85abe9 Trac #23713: Support SAGE_NUM_THREADS everywhere for
>> parallellism
>> 3c684b65ed Trac #23944: Q/Z
>> 0d96592852 Trac #23932: differences in construction of PolynomialRing and
>> LaurentPolynomialRing
>> 35ffe56528 Trac #23915: include the inner_product_matrix in module
>> comparison
>> da6237b58e Trac #23883: InheritComparisonClasscallMetaclass.__new__()
>> does not work
>> 2e522cf00a Trac #23865: disable a very long doctest in omega.py
>> b198ad5d04 Trac #23857: Implement conversion C++ <-> str
>> 1a06cd5dd1 Trac #23815: Upgrade to Python 2.7.14
>> 26a96021b2 Trac #23734: Implement iterator for generic permutations in
>> Cython
>> 5455b1ce78 Trac #23642: Factorization over some quotient rings incorrect
>> 82260ab4ad Trac #23565: update arb to version 2.11.1
>> c3f620e7b7 Trac #23544: Upgrade PARI/GP to git master version
>> 75daefe5ed Trac #23510: Fraction field of fixed modulus p-adic rings
>> should have floating point type
>> f8b263fb53 Trac #23376: Equality testing of genera of quadratic forms
>> over ZZ changes the genus and produces false results
>> b0c0f6749a Trac #22886: fix pxd header files
>> 54ba5948be Trac #23429: Multivector fields and the Schouten-Nijenhuis
>> bracket
>> c24da43be9 T

Re: [sage-release] Sage 8.1.beta8 released

2017-10-17 Thread Ralf Stephan

Error downloading giacpy_sage-0.6.6.tar.gz
The servers only have the previous 0.6 version.

On Tue, Oct 17, 2017 at 8:56 AM Volker Braun  wrote:

> As always, you can get the latest beta version from the "develop" git
> branch. Alternatively, the self-contained source tarball is at
> http://www.sagemath.org/download-latest.html
>
> a2e82e15a2 (HEAD -> develop, tag: 8.1.beta8, trac/develop) Updated
> SageMath version to 8.1.beta8
> 7dc7c74d76 Trac #23872: Singular expansion for implicitly defined function
> 71c53d6efc Trac #23844: GapElement.__contains__ (from libgap) should use
> the infix `in` from gap
> 03398aa3f4 Trac #23818: py3: hash for complex interval fields
> 756c0ec447 Trac #23671: hypergeometric motives
> e7b4f77db7 Trac #22922: Faster implementation of LLT polynomials
> 8d71436074 Trac #20762: Several additional methods for SimplicialComplex
> 37b5b2cfd2 Trac #18236: support xz compressed tarballs
> 202fa8dd8c Trac #24020: Cygwin: misc test failures
> a56746c985 Trac #23922: Upgrade eclib to compile with xcode 9
> 1472db0a6b Trac #23985: rst2ipynb causes doctest failures if pandoc is not
> installed
> 067b87c610 Trac #23983: dot2tex breaks docbuild
> 11c3bcca4e Trac #23979: Ignore failure in setrlimit on Cygwin
> e96397a071 Trac #23973: doc build hangs on Cygwin
> c249d236cb Trac #22461: Implement cython() using cythonize()
> 50670a7181 Trac #7516: bug in pickling quotient module over pid
> fce8fd00d4 Trac #23997: installed_packages(False) gives wrong version for
> Python packages with patches
> cc5307 Trac #23976: giacpy_sage causes doctest failures due to
> threading
> a22a806a2d Trac #23975: sage-location: do not remove .pyc files
> 2c6ac6c343 Trac #23970: Simpler caching in ell_rational_field
> cda826dfaf Trac #23966: Conversion from ZpFM to its fraction field
> incorrect
> 4bce0bfd2d Trac #23965: Coercion to fraction field is injective
> c3b1b7780a Trac #23862: speed_up_left_and_right_key
> a1b45bb7c4 Trac #23839: Fix reference manual index for partn_ref
> 1b74aa24b0 Trac #23634: A base class for integral quadratic forms seen as
> modules with a bilinear form.
> 9659a399eb Trac #18395: (moderate) Speedup in layout_spring
> c4aef0e21f Trac #23962: rank() of elliptic curves should always consult
> Cremona database
> 78a2ebd287 Trac #23957: gmpy2 causes doctest failures
> 7d5784f2a9 Trac #23947: Reciprocal transformation and trace polynomial
> e5cb49e05c Trac #23800: Add O method for Laurent series rings
> 0e98d937dc Trac #23963: py3: richcmp for function field ideals
> 380c526205 Trac #23951: fix rotate and conjugate in growth diagrams
> 639646985c Trac #23905: Avoid _element_constructor in Homset
> a5eeff69d2 Trac #23949: py3 : some work on __cmp__ and richcmp
> b580a4c279 Trac #23929: Upgrade to cypari2 version 1.1.3
> 894facd65a Trac #23912: parent() is slow for non-Elements
> bda5b4d10b Trac #23925: Bulk fix of signal handling in symbolics
> 68cb85abe9 Trac #23713: Support SAGE_NUM_THREADS everywhere for
> parallellism
> 3c684b65ed Trac #23944: Q/Z
> 0d96592852 Trac #23932: differences in construction of PolynomialRing and
> LaurentPolynomialRing
> 35ffe56528 Trac #23915: include the inner_product_matrix in module
> comparison
> da6237b58e Trac #23883: InheritComparisonClasscallMetaclass.__new__() does
> not work
> 2e522cf00a Trac #23865: disable a very long doctest in omega.py
> b198ad5d04 Trac #23857: Implement conversion C++ <-> str
> 1a06cd5dd1 Trac #23815: Upgrade to Python 2.7.14
> 26a96021b2 Trac #23734: Implement iterator for generic permutations in
> Cython
> 5455b1ce78 Trac #23642: Factorization over some quotient rings incorrect
> 82260ab4ad Trac #23565: update arb to version 2.11.1
> c3f620e7b7 Trac #23544: Upgrade PARI/GP to git master version
> 75daefe5ed Trac #23510: Fraction field of fixed modulus p-adic rings
> should have floating point type
> f8b263fb53 Trac #23376: Equality testing of genera of quadratic forms over
> ZZ changes the genus and produces false results
> b0c0f6749a Trac #22886: fix pxd header files
> 54ba5948be Trac #23429: Multivector fields and the Schouten-Nijenhuis
> bracket
> c24da43be9 Trac #23131: Add computation of longest commons extensions in a
> word
> c1c3197fc3 Trac #22720: AdditiveAbelianGroup([]).annihilator() fails.
> 294c389e84 Trac #18386: Doctests for: fix polylog evalf
> cc613b1e98 (tag: 8.1.beta7) Updated SageMath version to 8.1.beta7
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-release" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-release+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-release@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-release.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop

[sage-release] Re: Sage 8.1.beta2 released

2017-08-16 Thread Ralf Stephan

On Wednesday, August 16, 2017 at 3:15:26 AM UTC+2, rich...@lozestech.com 
wrote:
>
> Under openSUSE LEAP 42.2, fresh git-clone + pull develop, all today, got 
> the following error during ptest (-j4):
>

Cannot confirm on openSUSE LEAP 42.2 using ten attempts of sage -tp 
src/sage/schemes/elliptic_curves/ell_rational_field.py

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

Re: [sage-release] Re: Sage 8.0.rc0 released

2017-07-04 Thread Ralf Stephan

It's not a patchbot problem if you can reproduce it. Just check out the
branch, start Sage.

On Mon, Jul 3, 2017 at 10:29 PM Emmanuel Charpentier <
emanuel.charpent...@gmail.com> wrote:

> Thkis I understood. But to me, it meas that, as proposed, the patch can't
> compile, and therefore, needs work. But I'm not sure of this interpretation
> (I do not (yet) understand) what the patchbot is supposed to do ;
> therefore, I do not jnow if this is a patchbot error or a real problem with
> the patch).
>
> --
> Emmanuel Charpentier
>
>
> Le lundi 3 juillet 2017 17:08:52 UTC+2, Ralf Stephan a écrit :
>
>> ImportError: cannot import name ContainChildren
>>
>>
>>
>> On Mon, Jul 3, 2017 at 4:56 PM Emmanuel Charpentier <
>> emanuel.c...@gmail.com> wrote:
>>
>
>>>
>>> Le lundi 3 juillet 2017 15:58:31 UTC+2, Jeroen Demeyer a écrit :
>>>>
>>>> On 2017-07-02 10:38, Sébastien Labbé wrote:
>>>> > See
>>>> > https://trac.sagemath.org/ticket/15585
>>>> > for the first one.
>>>>
>>>> Which is possibly fixed by https://trac.sagemath.org/ticket/22462
>>>> (needs
>>>> review).
>>>>
>>>
>>> According to the patchbots <https://patchbot.sagemath.org/ticket/22462/>,
>>> Trac#22462 <https://trac.sagemath.org/ticket/22462> fails to build.
>>> What does that mean exactly ?
>>>
>>> --
>>> Emmanuel Charpentier
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "sage-release" group.
>>>
>> To unsubscribe from this group and stop receiving emails from it, send an
>>> email to sage-release...@googlegroups.com.
>>> To post to this group, send email to sage-r...@googlegroups.com.
>>
>>
>>> Visit this group at https://groups.google.com/group/sage-release.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "sage-release" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-release+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-release@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-release.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [sage-release] Re: Sage 8.0.rc0 released

2017-07-03 Thread Ralf Stephan

ImportError: cannot import name ContainChildren



On Mon, Jul 3, 2017 at 4:56 PM Emmanuel Charpentier <
emanuel.charpent...@gmail.com> wrote:

>
>
> Le lundi 3 juillet 2017 15:58:31 UTC+2, Jeroen Demeyer a écrit :
>>
>> On 2017-07-02 10:38, Sébastien Labbé wrote:
>> > See
>> > https://trac.sagemath.org/ticket/15585
>> > for the first one.
>>
>> Which is possibly fixed by https://trac.sagemath.org/ticket/22462 (needs
>> review).
>>
>
> According to the patchbots ,
> Trac#22462  fails to build. What
> does that mean exactly ?
>
> --
> Emmanuel Charpentier
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-release" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-release+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-release@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-release.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [sage-release] Sage 8.0.beta4 released

2017-04-28 Thread Ralf Stephan

Ah ok there is still a -lmcheck somewhere from debugging, sry

On Fri, Apr 28, 2017 at 8:33 AM Ralf Stephan <gtrw...@gmail.com> wrote:

> I get this but maybe I messed up myself somewhere when switching between
> debug yes/no:
>
> gcc version 5.4.0 (GCC)
> 
> NOTE: Set SAGE_MATPLOTLIB_GUI to anything but 'no' to try to build the
> Matplotlib GUI.
> Not building any matplotlib graphical backends.
> memory clobbered before allocated block
> Error: could not determine package name
> Error installing matplotlib package.
>
> What could be the cause?
>
> On Fri, Apr 28, 2017 at 8:19 AM Francois Bissey <
> francois.bis...@canterbury.ac.nz> wrote:
>
>> Thanks!
>>
>> > On 28/04/2017, at 18:08, Volker Braun <vbraun.n...@gmail.com> wrote:
>> >
>> > Now its there...
>>
>>
>> This email may be confidential and subject to legal privilege, it may
>> not reflect the views of the University of Canterbury, and it is not
>> guaranteed to be virus free. If you are not an intended recipient,
>> please notify the sender immediately and erase all copies of the message
>> and any attachments.
>>
>> Please refer to http://www.canterbury.ac.nz/emaildisclaimer for more
>> information.
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "sage-release" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to sage-release+unsubscr...@googlegroups.com.
>> To post to this group, send email to sage-release@googlegroups.com.
>> Visit this group at https://groups.google.com/group/sage-release.
>> For more options, visit https://groups.google.com/d/optout.
>>
>

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

Re: [sage-release] Sage 8.0.beta4 released

2017-04-28 Thread Ralf Stephan

I get this but maybe I messed up myself somewhere when switching between
debug yes/no:

gcc version 5.4.0 (GCC)

NOTE: Set SAGE_MATPLOTLIB_GUI to anything but 'no' to try to build the
Matplotlib GUI.
Not building any matplotlib graphical backends.
memory clobbered before allocated block
Error: could not determine package name
Error installing matplotlib package.

What could be the cause?

On Fri, Apr 28, 2017 at 8:19 AM Francois Bissey <
francois.bis...@canterbury.ac.nz> wrote:

> Thanks!
>
> > On 28/04/2017, at 18:08, Volker Braun  wrote:
> >
> > Now its there...
>
>
> This email may be confidential and subject to legal privilege, it may
> not reflect the views of the University of Canterbury, and it is not
> guaranteed to be virus free. If you are not an intended recipient,
> please notify the sender immediately and erase all copies of the message
> and any attachments.
>
> Please refer to http://www.canterbury.ac.nz/emaildisclaimer for more
> information.
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-release" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-release+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-release@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-release.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [sage-release] Re: Sage 8.0.beta3 released

2017-04-24 Thread Ralf Stephan

Passes tests on OpenSuSE except the usual #21828, #22862, and some R fails
I haven't reported yet.

On Mon, Apr 24, 2017 at 6:03 AM Francois Bissey <
francois.bis...@canterbury.ac.nz> wrote:

> This is now https://trac.sagemath.org/ticket/22860 I should
> have something ready in a few hours.
>
> François
>
> > On 24/04/2017, at 14:01, Henri Girard  wrote:
> >
> > same problem here :ubuntu 16.04.4 lcalc failed
> >
> >
> > Le 24/04/2017 à 02:43, François Bissey a écrit :
> >> On 24/04/17 12:18, tsc...@ucdavis.edu wrote:
> >>> Does this help?
> >>>
> >>> |
> >>> ld -v
> >>> GNU ld (GNU BinutilsforUbuntu)2.26.1
> >>> |
> >>>
> >>> Let me know what else I can get or do to help debug this.
> >>
> >> I am not sure how to find the incriminating info. But we
> >> should support your configuration, so lcalc will have to be
> >> fixed. Are gfan and tachyon behaving? We did a similar manipulation
> >> on them.
> >>
> >> Francois
> >>
> >
> > --
> > You received this message because you are subscribed to the Google
> Groups "sage-release" group.
> > To unsubscribe from this group and stop receiving emails from it, send
> an email to sage-release+unsubscr...@googlegroups.com.
> > To post to this group, send email to sage-release@googlegroups.com.
> > Visit this group at https://groups.google.com/group/sage-release.
> > For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-release" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-release+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-release@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-release.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [sage-release] Re: Sage 8.0.beta2 released

2017-04-13 Thread Ralf Stephan

Confirmed. It was not there in the 8.0beta1 patchbot run:
https://patchbot.sagemath.org/ticket/22090/

On Thu, Apr 13, 2017 at 2:22 PM Eric Gourgoulhon 
wrote:

> From a fresh git clone + pull develop on Ubuntu 16.04 x86_64 i7-6700HQ +
> 16 MB RAM, parallel (-j8) build OK.
>
> make ptestlong failed with one error:
>
> File "src/sage/calculus/calculus.py", line 1406, in
> sage.calculus.calculus.laplace
> Failed example:
> laplace(t^n, t, s, algorithm='giac')
> Expected:
> Traceback (most recent call last):
> ...
> NotImplementedError: Unable to parse Giac output:
> integrate(t^n*exp(-s*t),t,0,+infinity)
> Got:
> integration(t^n*e^(-s*t), t, 0, +Infinity)
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-release" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-release+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-release@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-release.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [sage-release] Sage 7.6.beta4 released

2017-02-22 Thread Ralf Stephan

Please followup at https://github.com/pynac/pynac/issues/231

On Wed, Feb 22, 2017 at 9:46 AM Jeroen Demeyer 
wrote:

> I just noticed that this doctest was actually introduced in 7.6.beta4 in
> #22174, so bisecting will not help...
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-release" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-release+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-release@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-release.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [sage-release] Re: Sage 7.5.rc2 released

2017-01-06 Thread Ralf Stephan

So gcc-6 is needed? I'm puzzled on what code change can trigger this.

On Sat, Jan 7, 2017, 03:31 Francois Bissey 
wrote:

> Looks like https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71767
>
> François
>
> > On 7/01/2017, at 15:23, Justin C. Walker  wrote:
> >
> >
> > On Jan 6, 2017, at 18:15 , John H Palmieri wrote:
> >
> >> No, it's not related to gcc 4.9.3: with a fresh Sage 7.5.rc2 tarball,
> pynac
> >> fails to build for me, both on OS X 10.11 and 10.12.
> >
> > I see the same failure: mac OS, 10.11.6.  I checked "gcc -v" in two
> enviornments, my normal shell (bash) environment, and after "./sage -sh" in
> $SAGE_ROOT for rc2:
> >
> > Normal:
> > 
> > Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr
> --with-gxx-include-dir=/usr/include/c++/4.2.1
> > Apple LLVM version 7.0.2 (clang-700.1.81)
> > Target: x86_64-apple-darwin15.6.0
> > Thread model: posix
> > 
> >
> > "./sage -sh":
> > 
> > Using built-in specs.
> > COLLECT_GCC=gcc
> >
> COLLECT_LTO_WRAPPER=/Users/Sage/sage-7.5.rc2/local/libexec/gcc/x86_64-apple-darwin15.6.0/5.4.0/lto-wrapper
> > Target: x86_64-apple-darwin15.6.0
> > Configured with: ../src/configure
> --prefix=/Users/Sage/sage-7.5.rc2/local
> --with-local-prefix=/Users/Sage/sage-7.5.rc2/local
> --with-gmp=/Users/Sage/sage-7.5.rc2/local
> --with-mpfr=/Users/Sage/sage-7.5.rc2/local
> --with-mpc=/Users/Sage/sage-7.5.rc2/local --with-system-zlib
> --disable-multilib --disable-nls --enable-languages=c,c++,fortran
> --disable-libitm --with-build-config=bootstrap-debug --without-isl
> --without-cloog
> > Thread model: posix
> > gcc version 5.4.0 (GCC)
> > 
> >
> > Not sure what to make of that.
> >
> > Justin
> >
> > --
> > Justin C. Walker, Curmudgeon at Large
> > Institute for the Absorption of Federal Funds
> > ---
> > If it weren't for carbon-14, I wouldn't date at all.
> > ---
> >
> >
> > --
> > You received this message because you are subscribed to the Google
> Groups "sage-release" group.
> > To unsubscribe from this group and stop receiving emails from it, send
> an email to sage-release+unsubscr...@googlegroups.com.
> > To post to this group, send email to sage-release@googlegroups.com.
> > Visit this group at https://groups.google.com/group/sage-release.
> > For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-release" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-release+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-release@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-release.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [sage-release] Sage 7.5.rc0 released

2016-12-20 Thread Ralf Stephan

Builds with 'make' upgrading from previous beta on OpenSuSE with
SAGE_INSTALL_GCC=yes and passes 'make ptestlong' except for the apparently
OpenSuSE-specific #21828.

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

Re: [sage-release] Re: Sage 7.5.beta2 released

2016-11-13 Thread Ralf Stephan

On Fri, Nov 11, 2016 at 11:15 AM Emmanuel Charpentier <
emanuel.charpent...@gmail.com> wrote:

> On anothe machine (core17, 16 GB RAM, Debian testing) where I installed
> giac in order to explore this
> , I get
> a failure of all tests involving giac, even after forced reinstallation (+
> the usual transient error on simplicial_complex.py).
>

Cannot confirm. After sage -i giac the optional giac tests in symbolic and
calculus do pass.


> I tried (to no avail) to create a "small script" allowing to start giac
> from the command line. This fails :
>
> charpent@asus16-ec:/usr/local/sage-7$ giac
> sage-run received unknown option: --giac
> usage: sage [options]
> Try 'sage -h' for more information.
>

Starting giac from within sage -sh does work here.

Regards,

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

Re: [sage-release] Sage 7.5.beta2 released

2016-11-10 Thread Ralf Stephan

Right, that's it. Thanks, will recompile Singular.

On Thu, Nov 10, 2016 at 5:15 PM Volker Braun <vbraun.n...@gmail.com> wrote:

> Thats a SAGE_DEBUG=yes build of Singular, I presume. This is
> https://trac.sagemath.org/ticket/21624
>
>
> On Thursday, November 10, 2016 at 5:00:52 PM UTC+1, Ralf Stephan wrote:
>
> Hi,
> I get reproducible doctest fails like this:
> File "src/sage/symbolic/relation.py", line 911, in
> sage.symbolic.relation.solve_mod
> Failed example:
> solve_mod([x^2 == 1, 4*x  == 11], 15)
> Expected:
> [(14,)]
> Got:
> 
> // ***dError: assume violation at numbers.cc:426 condition:
> n->cfCoeffName!=ndCoeffName
> // ***dError: assume violation at numbers.cc:426 condition:
> n->cfCoeffName!=ndCoeffName[(14,)]
>
> The result is fine, only Singular is spewing unwanted diagnostics. This
> can surely be turned off?
>
> On Thu, Nov 10, 2016 at 3:23 PM Daniel Krenn <kr...@aon.at> wrote:
>
> On 2016-11-10 00:23, Volker Braun wrote:
> > As always, you can get the latest beta version from the "develop" git
> > branch.
>
> Fresh build from git with
>   MAKE="make -j4" nice -17 make ptestlong
> is fine, except the failing doctest below. A second try
>   ./sage -t --long src/sage/libs/gap/assigned_names.py
> passed successfully.
>
>
> sage -t --long src/sage/libs/gap/assigned_names.py
> **
> File "src/sage/libs/gap/assigned_names.py", line 59, in
> sage.libs.gap.assigned_names.load_or_compute
> Failed example:
> workspace(name='globals')
> Expected:
> ('...', True)
> Got:
> ('/home/sci/dakrenn/.sage/gap/libgap-globals-4270978088606630785',
> False)
> **
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-release" group.
>
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-release...@googlegroups.com.
> To post to this group, send email to sage-r...@googlegroups.com.
>
>
> Visit this group at https://groups.google.com/group/sage-release.
> For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-release" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-release+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-release@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-release.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [sage-release] Sage 7.5.beta2 released

2016-11-10 Thread Ralf Stephan

Hi,
I get reproducible doctest fails like this:
File "src/sage/symbolic/relation.py", line 911, in
sage.symbolic.relation.solve_mod
Failed example:
solve_mod([x^2 == 1, 4*x  == 11], 15)
Expected:
[(14,)]
Got:

// ***dError: assume violation at numbers.cc:426 condition:
n->cfCoeffName!=ndCoeffName
// ***dError: assume violation at numbers.cc:426 condition:
n->cfCoeffName!=ndCoeffName[(14,)]

The result is fine, only Singular is spewing unwanted diagnostics. This can
surely be turned off?

On Thu, Nov 10, 2016 at 3:23 PM Daniel Krenn  wrote:

> On 2016-11-10 00:23, Volker Braun wrote:
> > As always, you can get the latest beta version from the "develop" git
> > branch.
>
> Fresh build from git with
>   MAKE="make -j4" nice -17 make ptestlong
> is fine, except the failing doctest below. A second try
>   ./sage -t --long src/sage/libs/gap/assigned_names.py
> passed successfully.
>
>
> sage -t --long src/sage/libs/gap/assigned_names.py
> **
> File "src/sage/libs/gap/assigned_names.py", line 59, in
> sage.libs.gap.assigned_names.load_or_compute
> Failed example:
> workspace(name='globals')
> Expected:
> ('...', True)
> Got:
> ('/home/sci/dakrenn/.sage/gap/libgap-globals-4270978088606630785',
> False)
> **
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-release" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-release+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-release@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-release.
> For more options, visit https://groups.google.com/d/optout.
>

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

[sage-release] Re: Sage 7.5.beta1 released

2016-11-05 Thread Ralf Stephan

Hi,

Regardless of the gcc used (Sage internal or not) both git master
and develop crash in make ptestlong in combinat/posets/posets.py.
Crash log is attached.

The crash can be provoked interactively with:
sage:  Poset().is_incomparable_chain_free(1,1)
...

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.
GNU gdb (GDB; openSUSE Leap 42.2) 7.11.1
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-suse-linux".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word".
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
To enable execution of this file add
add-auto-load-safe-path 
/home/ralf/sage/local/lib/libstdc++.so.6.0.20-gdb.py
line to your configuration file "/home/ralf/.gdbinit".
To completely disable this security protection add
set auto-load safe-path /
line to your configuration file "/home/ralf/.gdbinit".
For more information about this security protection see the
"Auto-loading safe path" section in the GDB manual.  E.g., run from the shell:
info "(gdb)Auto-loading safe path"
0x7f213d014726 in waitpid () from /lib64/libpthread.so.0
Missing separate debuginfos, use: zypper install glibc-debuginfo-2.22-3.7.x86_64

Stack backtrace
---
No symbol table info available.
#1  0x7f2138703fe2 in print_enhanced_backtrace ()
at build/src/cysignals/implementation.c:401
parent_pid = 5922
pid = 
#2  0x7f21387045aa in sigdie (sig=sig@entry=6, 
s=s@entry=0x7f213870d360 "Unhandled SIGABRT: An abort() occurred.")
at build/src/cysignals/implementation.c:420
No locals.
#3  0x7f213870730a in cysigs_signal_handler (sig=6)
at build/src/cysignals/implementation.c:204
inside = 
#4  
No symbol table info available.
#5  0x7f213c5918d7 in raise () from /lib64/libc.so.6
No symbol table info available.
#6  0x7f213c592caa in abort () from /lib64/libc.so.6
No symbol table info available.
#7  0x7f213c5cf1b4 in __libc_message () from /lib64/libc.so.6
No symbol table info available.
#8  0x7f213c5d49d6 in malloc_printerr () from /lib64/libc.so.6
No symbol table info available.
#9  0x7f1ee8efa8c3 in sig_free (__pyx_v_ptr=)
at build/cythonized/sage/graphs/generic_graph_pyx.c:19830
No locals.
#10 __pyx_pf_4sage_6graphs_17generic_graph_pyx_14SubgraphSearch_12__dealloc__ (
__pyx_v_self=0x7f1ecf30d808)
at build/cythonized/sage/graphs/generic_graph_pyx.c:14108
__pyx_t_1 = 
#11 __pyx_pw_4sage_6graphs_17generic_graph_pyx_14SubgraphSearch_13__dealloc__ (
__pyx_v_self=0x7f1ecf30d808)
at build/cythonized/sage/graphs/generic_graph_pyx.c:14034
No locals.
#12 __pyx_tp_dealloc_4sage_6graphs_17generic_graph_pyx_SubgraphSearch (
o=0x7f1ecf30d808) at build/cythonized/sage/graphs/generic_graph_pyx.c:20965
etype = 0x0
eval = 0x0
etb = 0x0
p = 0x7f1ecf30d808
#13 0x7f213d2a6459 in frame_dealloc (f=0x28f8300)
at Objects/frameobject.c:460
_py_tmp = 
_tstate = 0x19a60a0
p = 0x28f84a8
valuestack = 0x28f84c0
co = 
#14 0x7f213d32d4aa in PyEval_EvalCodeEx (co=, 
globals=, locals=locals@entry=0x0, args=, 
argcount=argcount@entry=2, kws=, kwcount=1, 
defs=0x7f1ee8553e28, defcount=1, closure=0x0) at Python/ceval.c:3278
f = 
retval = 0x7f213d5f17a0 <_Py_NoneStruct>
fastlocals = 
freevars = 
tstate = 
x = 
u = 
#15 0x7f213d32c256 in fast_function (nk=1, na=2, n=, 
pp_stack=0x7ffd170f1df0, func=0x7f1ee855c8c0) at Python/ceval.c:4131
co = 
nd = 
globals = 
argdefs = 
d = 
#16 call_function (oparg=, pp_stack=0x7ffd170f1df0)
at Python/ceval.c:4056
func = 0x7f1ee855c8c0
w = 
na = 2
nk = 1
n = 
pfunc = 0x682ccb0
x = 
#17 PyEval_EvalFrameEx (f=f@entry=0x682cb00, throwflag=throwflag@entry=0)
at Python/ceval.c:2681
sp = 0x682ccd0
stack_pointer = 
next_instr = 
opcode = 
oparg

Re: [sage-release] Sage 7.5.beta1 released

2016-11-03 Thread Ralf Stephan

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

On Wed, Nov 2, 2016 at 8:22 PM Volker Braun <vbraun.n...@gmail.com> wrote:

> open a ticket
>
>
> On Wednesday, November 2, 2016 at 4:32:36 PM UTC+1, Ralf Stephan wrote:
>
> With this patch it all compiles:
> diff --git a/src/sage/libs/singular/decl.pxd
> b/src/sage/libs/singular/decl.pxd
> index 8235e9d..8f355ba 100644
> --- a/src/sage/libs/singular/decl.pxd
> +++ b/src/sage/libs/singular/decl.pxd
> @@ -1,4 +1,4 @@
> -# distutils: extra_compile_args = SINGULAR_CFLAGS
> +# distutils: extra_compile_args = SINGULAR_CFLAGS -std=c++11
>  # distutils: libraries = SINGULAR_LIBRARIES
>  # distutils: library_dirs = SINGULAR_LIBDIR
>  # distutils: language = c++
> diff --git a/src/sage/rings/finite_rings/element_givaro.pxd
> b/src/sage/rings/finite_rings/element_givaro.pxd
> index 91c4ed7..b43f7ad 100644
> --- a/src/sage/rings/finite_rings/element_givaro.pxd
> +++ b/src/sage/rings/finite_rings/element_givaro.pxd
> @@ -1,4 +1,4 @@
> -# distutils: extra_compile_args = GIVARO_CFLAGS
> +# distutils: extra_compile_args = GIVARO_CFLAGS -std=c++11
>
>  from libcpp.vector cimport vector
>  ctypedef vector[int] intvec
>
> Is this known? Open ticket with it?
>
> On Wed, Nov 2, 2016 at 3:40 PM Ralf Stephan <gtr...@gmail.com> wrote:
>
> Again me with the gcc5 error on OpenSuSE, this time with serial log ;-)
>
> Thanks for any opinion,
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-release" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-release+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-release@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-release.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [sage-release] Sage 7.5.beta1 released

2016-11-02 Thread Ralf Stephan

With this patch it all compiles:
diff --git a/src/sage/libs/singular/decl.pxd
b/src/sage/libs/singular/decl.pxd
index 8235e9d..8f355ba 100644
--- a/src/sage/libs/singular/decl.pxd
+++ b/src/sage/libs/singular/decl.pxd
@@ -1,4 +1,4 @@
-# distutils: extra_compile_args = SINGULAR_CFLAGS
+# distutils: extra_compile_args = SINGULAR_CFLAGS -std=c++11
 # distutils: libraries = SINGULAR_LIBRARIES
 # distutils: library_dirs = SINGULAR_LIBDIR
 # distutils: language = c++
diff --git a/src/sage/rings/finite_rings/element_givaro.pxd
b/src/sage/rings/finite_rings/element_givaro.pxd
index 91c4ed7..b43f7ad 100644
--- a/src/sage/rings/finite_rings/element_givaro.pxd
+++ b/src/sage/rings/finite_rings/element_givaro.pxd
@@ -1,4 +1,4 @@
-# distutils: extra_compile_args = GIVARO_CFLAGS
+# distutils: extra_compile_args = GIVARO_CFLAGS -std=c++11

 from libcpp.vector cimport vector
 ctypedef vector[int] intvec

Is this known? Open ticket with it?

On Wed, Nov 2, 2016 at 3:40 PM Ralf Stephan <gtrw...@gmail.com> wrote:

> Again me with the gcc5 error on OpenSuSE, this time with serial log ;-)
>
> Thanks for any opinion,
>

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

Re: [sage-release] Re: Sage 7.5.beta0 released

2016-10-21 Thread Ralf Stephan

I get
[sagelib-7.5.beta0] [  7/298] gcc -fno-strict-aliasing -g -O2 -DNDEBUG -g
-fwrap
v -O3 -Wall -Wno-unused -fPIC
-I/home/ralf/sage/local/lib/python2.7/site-package
s/cysignals -I/home/ralf/sage/local/include
-I/home/ralf/sage/local/include/pyth
on2.7
-I/home/ralf/sage/local/lib/python2.7/site-packages/numpy/core/include -I/
home/ralf/sage/src -I/home/ralf/sage/src/sage/ext
-I/home/ralf/sage/src/build/cy
thonized -I/home/ralf/sage/src/build/cythonized/sage/ext
-I/home/ralf/sage/local
/include/python2.7 -c
/home/ralf/sage/src/build/cythonized/sage/libs/symmetrica/
symmetrica.c -o
build/temp.linux-x86_64-2.7/home/ralf/sage/src/build/cythonized/
sage/libs/symmetrica/symmetrica.o -fno-strict-aliasing
[sagelib-7.5.beta0] In file included from /usr/include/c++/5/cstdint:35:0,
[sagelib-7.5.beta0]  from
/home/ralf/sage/local/include/givaro/u
dl.h:12,
[sagelib-7.5.beta0]  from
/home/ralf/sage/local/include/givaro/g
ivrandom.h:22,
[sagelib-7.5.beta0]  from
/home/ralf/sage/src/build/cythonized/s
age/libs/singular/polynomial.cpp:421:
[sagelib-7.5.beta0] /usr/include/c++/5/bits/c++0x_warning.h:32:2: error:
#error
This file requires compiler and library support for the ISO C++ 2011
standard. T
his support must be enabled with the -std=c++11 or -std=gnu++11 compiler
options
.
[sagelib-7.5.beta0]  #error This file requires compiler and library support
\
[sagelib-7.5.beta0]   ^
[sagelib-7.5.beta0] In file included from
/home/ralf/sage/local/include/givaro/g
ivrandom.h:22:0,
[sagelib-7.5.beta0]  from
/home/ralf/sage/src/build/cythonized/s
age/libs/singular/polynomial.cpp:421:
[sagelib-7.5.beta0] /home/ralf/sage/local/include/givaro/udl.h:18:1:
warning: id
entifier ‘constexpr’ is a keyword in C++11 [-Wc++0x-compat]
[sagelib-7.5.beta0]  constexpr uint64_t operator"" _ui64(unsigned long long
x)
[sagelib-7.5.beta0]  ^


On Fri, Oct 21, 2016 at 10:37 AM 'Martin R' via sage-release <
sage-release@googlegroups.com> wrote:

> Yippie!  Thank you!
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-release" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-release+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-release@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-release.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [sage-release] Re: Sage 7.4.rc2 released

2016-10-17 Thread Ralf Stephan

>So, a better question is: is there an estimate for how long a complete
build, excluding or including documentation I don't care) should take on my
machine (cpuinfo see above, using MAKE="make -j4").

My guess: more than two hours excluding documentation (where memory is
important which info I cannot see in your post).

On Mon, Oct 17, 2016 at 9:03 AM 'Martin R' via sage-release <
sage-release@googlegroups.com> wrote:

> complete from scratch.
>
> So, a better question is: is there an estimate for how long a complete
> build, excluding or including documentation I don't care) should take on my
> machine (cpuinfo see above, using MAKE="make -j4").
>
> Martin
>
> Am Montag, 17. Oktober 2016 08:16:22 UTC+2 schrieb Jeroen Demeyer:
>
> On 2016-10-16 20:20, 'Martin R' via sage-release wrote:
> > It seems that this made openblas build, thank you.
> >
> > However: the build takes so long that it makes me wonder.  Is it
> > possible that it takes much longer to build this release candidate than
> > some beta before?
>
> The build of *what* takes so long? The openblas build? Of an incremental
> Sage build? Of a complete from-scratch Sage build?
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-release" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-release+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-release@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-release.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [sage-release] Sage 7.4.rc1 released

2016-10-13 Thread Ralf Stephan

Fresh install on OpenSuSE-42.2beta. After switching from thir experimental
gcc6 to gcc5 this:

[sagelib-7.4.rc1] gcc -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3
-Wall
-Wno-unused -fPIC -I/home/ralf/sage/local/include
-I/home/ralf/sage/local/includ
e/python2.7
-I/home/ralf/sage/local/lib/python2.7/site-packages/numpy/core/inclu
de -I/home/ralf/sage/src -I/home/ralf/sage/src/sage/ext
-I/home/ralf/sage/src/bu
ild/cythonized -I/home/ralf/sage/src/build/cythonized/sage/ext
-I/home/ralf/sage
/local/include/python2.7 -c
/home/ralf/sage/src/build/cythonized/sage/libs/singu
lar/singular.cpp -o
build/temp.linux-x86_64-2.7/home/ralf/sage/src/build/cythoni
zed/sage/libs/singular/singular.o -fPIC -mmmx -mpopcnt -msse -msse2 -msse3
-msse
4.1 -msse4.2 -mavx -mavx2 -mfma -mbmi -mbmi2 -mfpmath=sse -fabi-version=6
-I/hom
e/ralf/sage/local/include -I/home/ralf/sage/local//include
-I/home/ralf/sage/local/include -fno-strict-aliasing
[sagelib-7.4.rc1] In file included from /usr/include/c++/5/cstdint:35:0,
[sagelib-7.4.rc1]  from
/home/ralf/sage/local/include/givaro/udl.h:12,
[sagelib-7.4.rc1]  from
/home/ralf/sage/local/include/givaro/givrandom.h:22,
[sagelib-7.4.rc1]  from
/home/ralf/sage/src/build/cythonized/sage/libs/singular/singular.cpp:386:
[sagelib-7.4.rc1] /usr/include/c++/5/bits/c++0x_warning.h:32:2: error:
#error This file requires compiler and library support for the ISO C++ 2011
standard. This support must be enabled with the -std=c++11 or -std=gnu++11
compiler options.
[sagelib-7.4.rc1]  #error This file requires compiler and library support \
[sagelib-7.4.rc1]   ^
[sagelib-7.4.rc1] In file included from
/home/ralf/sage/local/include/givaro/givrandom.h:22:0,
[sagelib-7.4.rc1]  from
/home/ralf/sage/src/build/cythonized/sage/libs/singular/singular.cpp:386:

Is it known?

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

Re: [sage-release] Re: Sage 7.4.beta0 released

2016-08-12 Thread Ralf Stephan

Starting sage -gdb then Ctrl-C previously gave the gdb prompt. Also
previously
in a session started using bare "sage" Ctrl-C showed KeyboardInterrupt
which it no longer does. I do not know when this changed, maybe even before
7.4

On Fri, Aug 12, 2016 at 9:49 AM Jeroen Demeyer <jdeme...@cage.ugent.be>
wrote:

> On 2016-08-12 07:55, Ralf Stephan wrote:
> > Not sure how new this is but I can no longer interrupt a Sage session
> > with Ctrl-C
>
> Can you tell me *more precisely* what you're doing and how it doesn't
> work anymore?
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-release" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-release+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-release@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-release.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [sage-release] Re: Sage 7.4.beta0 released

2016-08-11 Thread Ralf Stephan

Not sure how new this is but I can no longer interrupt a Sage session with
Ctrl-C
which is necessary to get a gdb prompt. If new then presumably IPython the
cause?
I can workaround with Ctrl-Z and fg however.

On Thu, Aug 11, 2016 at 10:55 PM Dima Pasechnik  wrote:

> After the update, on exit from Sage I get
>
> Exiting Sage (CPU time 0m0.17s, Wall time 0m44.15s).
> :0: UserWarning: You do not have a working installation of the
> service_identity module: 'No module named service_identity'.  Please
> install it from  and make
> sure all of its dependencies are satisfied.  Without the service_identity
> module and a recent enough pyOpenSSL to support it, Twisted can perform
> only rudimentary TLS client hostname verification.  Many valid
> certificate/hostname mappings may be rejected.
>
> After doing "sage --pip install service_identity"
> this warning goes away.
>
> Any idea what happens here?
>
> Dima
>
>
> On Thursday, August 11, 2016 at 7:45:06 AM UTC+1, Volker Braun wrote:
>>
>> As always, you can get the latest beta version from the "develop" git
>> branch. Alternatively, the self-contained source tarball is at
>> http://www.sagemath.org/download-latest.html
>>
>> 0a80508 Updated SageMath version to 7.4.beta0
>>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-release" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-release+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-release@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-release.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [sage-release] Sage 7.3 released

2016-08-05 Thread Ralf Stephan

On Fri, Aug 5, 2016 at 11:05 AM leif  wrote:

> No, the tombstones (or zombies?) are these:


Huh. I just started work on one of these half an hour ago.
So call me ghoul or ?

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

Re: [sage-release] 7.3.beta6

2016-07-01 Thread Ralf Stephan

I confirm this is a dependency IF you have giac installed on a Debian
system.

giac/src/debian/README.debian:Build-Depends: debhelper, libgmp-dev,
libreadline-dev, libgsl0-dev, libpng12-dev, libjpeg-dev, libpari-dev,
libntl-dev, libmpfr-dev, liblapack-dev, libfltk1.3-dev, libgl1-mesa-dev,
libxft-dev, libx11-dev, libxt-dev, libao-dev, libmpfi-dev, texlive,
texlive-math-extra, texlive-pstricks

Why it was not picked up when you installed giac, and why it is needed
only later when Pynac is installed is still unclear. I will set
--with-giac=no
as default in a Sage ticket (and you can do this too if it bothers you).

On Fri, Jul 1, 2016 at 9:08 AM Ralf Stephan <gtrw...@gmail.com> wrote:

> I don't get it. Why would the ao-devel pkg resolve the issue. Why don't
> I get libao if I do
> ralf@ark:~/sage> ldd local/lib/libgiac.so
> on OpenSuSE?
>
> On Fri, Jul 1, 2016 at 9:00 AM William Stein <wst...@gmail.com> wrote:
>
>> On Thu, Jun 30, 2016 at 11:56 PM, Ralf Stephan <gtrw...@gmail.com> wrote:
>> >> [pynac-0.6.7] /usr/bin/ld: cannot find -lao
>> >> [pynac-0.6.7] collect2: error: ld returned 1 exit status
>> >
>> > No idea where you get that library dependence from. What changed
>> > with beta5 was that if giac was installed that would be linked, so an
>> > experiment would be to uninstall giac and sage -p pynac after that.
>>
>> giac is definitely installed.   Maybe giac or something related now
>> has some new support for libao -- audio output?  It makes sense...
>>
>> For me, I'm fine: I just now consider libao-dev something I have to
>> install before Sage, given that I have also installed giac.I'm
>> sure this will cause great confusion to other people who like to
>> install lots of math software on the same system in the future though.
>>
>> William
>>
>> >
>> > On Fri, Jul 1, 2016 at 8:39 AM William Stein <wst...@gmail.com> wrote:
>> >>
>> >> Hi,
>> >>
>> >> On sagemathcloud (Ubuntu 16.04+lots) I've built all the betas up to
>> >> 7.3.beta4 fine.  7.3.beta5 (via upgrade) won't build, nor will
>> >> 7.3.beta6.  The complete failed at pynac build log for 7.3.beta6 is
>> >> attached.
>> >>
>> >> "I am unable to get 7.3.beta5 to compile on this project. I tried
>> >> updating from the developer version rsynced from
>> >> /projects/sage/sage-dev/ and then building with ./sage -b, but it
>> >> fails when compiling gen.pyx. Alternatively, when I run 'make', it
>> >> fails on building pynac. I've also tried wgetting the 7.3.beta5
>> >> tarball and making from scratch, but still get the same failure on
>> >> pynac. I feel like I must be missing something obvious. Thanks in
>> >> advance for any help! [...] FYI, 7.3.beta6 still fails to build on
>> >> pynac. For now, I'm just sticking with 7.3.beta4. Thank you both for
>> >> your help!"
>> >>
>> >> Build ends with:
>> >>
>> >> ---
>> >>
>> >> pynac-0.6.7]   CXX  libpynac_la-infoflagbase.lo
>> >>
>> >> [pynac-0.6.7]   CXX  libpynac_la-order.lo
>> >>
>> >> sage-logger -p 'sage-spkg speaklater-1.3'
>> >>
>> >>
>> '/projects/74fa0622-89a5-45b8-9451-eaaacd2ad12b/sage-git/logs/pkgs/speaklater-1.3.log'
>> >>
>> >> [speaklater-1.3] Found local metadata for speaklater-1.3
>> >>
>> >> [speaklater-1.3] Attempting to download package speaklater-1.3.tar.gz
>> >> from mirrors
>> >>
>> >> [speaklater-1.3]
>> >>
>> http://mirrors.mit.edu/sage/spkg/upstream/speaklater/speaklater-1.3.tar.gz
>> >>
>> >> [pynac-0.6.7]   CXXLDlibpynac.la
>> >>
>> >> [speaklater-1.3]
>> >>
>> [..]
>> >>
>> >> [speaklater-1.3] speaklater-1.3
>> >>
>> >> [speaklater-1.3] 
>> >>
>> >> [speaklater-1.3] Setting up build directory for speaklater-1.3
>> >>
>> >> [speaklater-1.3] Finished extraction
>> >>
>> >> [speaklater-1.3] 
>> >>
>> >> [speaklater-1.3] Host system:
>> >>
>> >> [speaklater-1.3] Linux compute6-us 4.2.0-30-generic #36-Ubuntu SMP Fri
>> >> Feb 26 00:58:07 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
>>

Re: [sage-release] 7.3.beta6

2016-07-01 Thread Ralf Stephan

Or even add --with-giac=no in the Pynac spkg-install script.

On Fri, Jul 1, 2016 at 8:55 AM Ralf Stephan <gtrw...@gmail.com> wrote:

> > [pynac-0.6.7] /usr/bin/ld: cannot find -lao
> > [pynac-0.6.7] collect2: error: ld returned 1 exit status
>
> No idea where you get that library dependence from. What changed
> with beta5 was that if giac was installed that would be linked, so an
> experiment would be to uninstall giac and sage -p pynac after that.
>
> On Fri, Jul 1, 2016 at 8:39 AM William Stein <wst...@gmail.com> wrote:
>
>> Hi,
>>
>> On sagemathcloud (Ubuntu 16.04+lots) I've built all the betas up to
>> 7.3.beta4 fine.  7.3.beta5 (via upgrade) won't build, nor will
>> 7.3.beta6.  The complete failed at pynac build log for 7.3.beta6 is
>> attached.
>>
>> "I am unable to get 7.3.beta5 to compile on this project. I tried
>> updating from the developer version rsynced from
>> /projects/sage/sage-dev/ and then building with ./sage -b, but it
>> fails when compiling gen.pyx. Alternatively, when I run 'make', it
>> fails on building pynac. I've also tried wgetting the 7.3.beta5
>> tarball and making from scratch, but still get the same failure on
>> pynac. I feel like I must be missing something obvious. Thanks in
>> advance for any help! [...] FYI, 7.3.beta6 still fails to build on
>> pynac. For now, I'm just sticking with 7.3.beta4. Thank you both for
>> your help!"
>>
>> Build ends with:
>>
>> ---
>>
>> pynac-0.6.7]   CXX  libpynac_la-infoflagbase.lo
>>
>> [pynac-0.6.7]   CXX  libpynac_la-order.lo
>>
>> sage-logger -p 'sage-spkg speaklater-1.3'
>>
>> '/projects/74fa0622-89a5-45b8-9451-eaaacd2ad12b/sage-git/logs/pkgs/speaklater-1.3.log'
>>
>> [speaklater-1.3] Found local metadata for speaklater-1.3
>>
>> [speaklater-1.3] Attempting to download package speaklater-1.3.tar.gz
>> from mirrors
>>
>> [speaklater-1.3]
>> http://mirrors.mit.edu/sage/spkg/upstream/speaklater/speaklater-1.3.tar.gz
>>
>> [pynac-0.6.7]   CXXLDlibpynac.la
>>
>> [speaklater-1.3]
>> [..]
>>
>> [speaklater-1.3] speaklater-1.3
>>
>> [speaklater-1.3] 
>>
>> [speaklater-1.3] Setting up build directory for speaklater-1.3
>>
>> [speaklater-1.3] Finished extraction
>>
>> [speaklater-1.3] 
>>
>> [speaklater-1.3] Host system:
>>
>> [speaklater-1.3] Linux compute6-us 4.2.0-30-generic #36-Ubuntu SMP Fri
>> Feb 26 00:58:07 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
>>
>> [speaklater-1.3] 
>>
>> [speaklater-1.3] C compiler: gcc
>>
>> [speaklater-1.3] C compiler version:
>>
>> [speaklater-1.3] Using built-in specs.
>>
>> [speaklater-1.3] COLLECT_GCC=gcc
>>
>> [speaklater-1.3]
>> COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/5/lto-wrapper
>>
>> [speaklater-1.3] Target: x86_64-linux-gnu
>>
>> [speaklater-1.3] Configured with: ../src/configure -v
>> --with-pkgversion='Ubuntu 5.2.1-22ubuntu2'
>> --with-bugurl=file:///usr/share/doc/gcc-5/README.Bugs
>> --enable-languages=c,ada,c++,java,go,d,fortran,objc,obj-c++
>> --prefix=/usr --program-suffix=-5 --enable-shared
>> --enable-linker-build-id --libexecdir=/usr/lib
>> --without-included-gettext --enable-threads=posix --libdir=/usr/lib
>> --enable-nls --with-sysroot=/ --enable-clocale=gnu
>> --enable-libstdcxx-debug --enable-libstdcxx-time=yes
>> --with-default-libstdcxx-abi=new --enable-gnu-unique-object
>> --disable-vtable-verify --enable-libmpx --enable-plugin
>> --with-system-zlib --disable-browser-plugin --enable-java-awt=gtk
>> --enable-gtk-cairo
>> --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-5-amd64/jre
>> --enable-java-home
>> --with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-5-amd64
>> --with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-5-amd64
>> --with-arch-directory=amd64
>> --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --enable-objc-gc
>> --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64
>> --with-multilib-list=m32,m64,mx32 --enable-multilib
>> --with-tune=generic --enable-checking=release --build=x86_64-linux-gnu
>> --host=x86_64-linux-gnu --target=x86_64-linux-gnu
>>
>> [speaklater-1.3] Thread model: posix
>>
>> [speaklater-1.3] gcc version 5.2.1 20151010 (Ubuntu 5.2.1-22ubuntu2)
>>
>>

Re: [sage-release] 7.3.beta6

2016-07-01 Thread Ralf Stephan

> [pynac-0.6.7] /usr/bin/ld: cannot find -lao
> [pynac-0.6.7] collect2: error: ld returned 1 exit status

No idea where you get that library dependence from. What changed
with beta5 was that if giac was installed that would be linked, so an
experiment would be to uninstall giac and sage -p pynac after that.

On Fri, Jul 1, 2016 at 8:39 AM William Stein  wrote:

> Hi,
>
> On sagemathcloud (Ubuntu 16.04+lots) I've built all the betas up to
> 7.3.beta4 fine.  7.3.beta5 (via upgrade) won't build, nor will
> 7.3.beta6.  The complete failed at pynac build log for 7.3.beta6 is
> attached.
>
> "I am unable to get 7.3.beta5 to compile on this project. I tried
> updating from the developer version rsynced from
> /projects/sage/sage-dev/ and then building with ./sage -b, but it
> fails when compiling gen.pyx. Alternatively, when I run 'make', it
> fails on building pynac. I've also tried wgetting the 7.3.beta5
> tarball and making from scratch, but still get the same failure on
> pynac. I feel like I must be missing something obvious. Thanks in
> advance for any help! [...] FYI, 7.3.beta6 still fails to build on
> pynac. For now, I'm just sticking with 7.3.beta4. Thank you both for
> your help!"
>
> Build ends with:
>
> ---
>
> pynac-0.6.7]   CXX  libpynac_la-infoflagbase.lo
>
> [pynac-0.6.7]   CXX  libpynac_la-order.lo
>
> sage-logger -p 'sage-spkg speaklater-1.3'
>
> '/projects/74fa0622-89a5-45b8-9451-eaaacd2ad12b/sage-git/logs/pkgs/speaklater-1.3.log'
>
> [speaklater-1.3] Found local metadata for speaklater-1.3
>
> [speaklater-1.3] Attempting to download package speaklater-1.3.tar.gz
> from mirrors
>
> [speaklater-1.3]
> http://mirrors.mit.edu/sage/spkg/upstream/speaklater/speaklater-1.3.tar.gz
>
> [pynac-0.6.7]   CXXLDlibpynac.la
>
> [speaklater-1.3]
> [..]
>
> [speaklater-1.3] speaklater-1.3
>
> [speaklater-1.3] 
>
> [speaklater-1.3] Setting up build directory for speaklater-1.3
>
> [speaklater-1.3] Finished extraction
>
> [speaklater-1.3] 
>
> [speaklater-1.3] Host system:
>
> [speaklater-1.3] Linux compute6-us 4.2.0-30-generic #36-Ubuntu SMP Fri
> Feb 26 00:58:07 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
>
> [speaklater-1.3] 
>
> [speaklater-1.3] C compiler: gcc
>
> [speaklater-1.3] C compiler version:
>
> [speaklater-1.3] Using built-in specs.
>
> [speaklater-1.3] COLLECT_GCC=gcc
>
> [speaklater-1.3]
> COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/5/lto-wrapper
>
> [speaklater-1.3] Target: x86_64-linux-gnu
>
> [speaklater-1.3] Configured with: ../src/configure -v
> --with-pkgversion='Ubuntu 5.2.1-22ubuntu2'
> --with-bugurl=file:///usr/share/doc/gcc-5/README.Bugs
> --enable-languages=c,ada,c++,java,go,d,fortran,objc,obj-c++
> --prefix=/usr --program-suffix=-5 --enable-shared
> --enable-linker-build-id --libexecdir=/usr/lib
> --without-included-gettext --enable-threads=posix --libdir=/usr/lib
> --enable-nls --with-sysroot=/ --enable-clocale=gnu
> --enable-libstdcxx-debug --enable-libstdcxx-time=yes
> --with-default-libstdcxx-abi=new --enable-gnu-unique-object
> --disable-vtable-verify --enable-libmpx --enable-plugin
> --with-system-zlib --disable-browser-plugin --enable-java-awt=gtk
> --enable-gtk-cairo
> --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-5-amd64/jre
> --enable-java-home
> --with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-5-amd64
> --with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-5-amd64
> --with-arch-directory=amd64
> --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --enable-objc-gc
> --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64
> --with-multilib-list=m32,m64,mx32 --enable-multilib
> --with-tune=generic --enable-checking=release --build=x86_64-linux-gnu
> --host=x86_64-linux-gnu --target=x86_64-linux-gnu
>
> [speaklater-1.3] Thread model: posix
>
> [speaklater-1.3] gcc version 5.2.1 20151010 (Ubuntu 5.2.1-22ubuntu2)
>
> [speaklater-1.3] 
>
> [speaklater-1.3] running install
>
> [pynac-0.6.7] /usr/bin/ld: cannot find -lao
>
> [pynac-0.6.7] collect2: error: ld returned 1 exit status
>
> [pynac-0.6.7] Makefile:493: recipe for target 'libpynac.la' failed
>
> [pynac-0.6.7] make[5]: *** [libpynac.la] Error 1
>
> [pynac-0.6.7] make[5]: Leaving directory
>
> '/projects/74fa0622-89a5-45b8-9451-eaaacd2ad12b/sage-git/local/var/tmp/sage/build/pynac-0.6.7/src/ginac'
>
> [pynac-0.6.7] Makefile:480: recipe for target 'all-recursive' failed
>
> [pynac-0.6.7] make[4]: *** [all-recursive] Error 1
>
> [pynac-0.6.7] make[4]: Leaving directory
>
> '/projects/74fa0622-89a5-45b8-9451-eaaacd2ad12b/sage-git/local/var/tmp/sage/build/pynac-0.6.7/src'
>
> [pynac-0.6.7] Makefile:386: recipe for target 'all' failed
>
> [pynac-0.6.7] make[3]: *** [all] Error 2
>
> [pynac-0.6.7] make[3]: Leaving

Re: [sage-release] Sage 7.2.rc1 released

2016-05-07 Thread Ralf Stephan

On OpenSuSE Leap it passes make ptestlong, with a few long test warnings.

On Sat, May 7, 2016 at 2:26 PM Volker Braun  wrote:

> As always, you can get the latest beta version from the "develop" git
> branch. Alternatively, the self-contained source tarball is at
> http://www.sagemath.org/download-latest.html
>
> abc779b Updated SageMath version to 7.2.rc1
> 0b99dcb Trac #20475: Upgrade to Pynac-0.6.5
> 67e4937 Trac #20312: parent of argument lost with Functions
> fddbe1f Trac #20558: Documentation depends on tachyon
> e08e584 Trac #20525: gap_packages badly broken
> 093e42f Updated SageMath version to 7.2.rc0
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-release" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-release+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-release@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-release.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [sage-release] Sage 7.0.beta0 released

2015-12-23 Thread Ralf Stephan

Wrong. Additional directories in the Sage root are removed too, but not git
repo directories.

On Wed, Dec 23, 2015 at 9:00 AM Ralf Stephan <gtrw...@gmail.com> wrote:

> On Tue, Dec 22, 2015 at 11:16 PM Volker Braun <vbraun.n...@gmail.com>
> wrote:
>
>> Thats because "make distclean" uses Sage's Python which doesn't work. Run
>> "git clean -f -d -x" which doesn't use any Sage internals.
>>
>
> Note that this does also delete ALL files not from Sage in the Sage root
> directory, not however such directories.
>

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

Re: [sage-release] sagedev error

2015-07-17 Thread Ralf Stephan

I did and Volker closed it already.
But now I know that rerere was the reason here too.

On Fri, Jul 17, 2015 at 10:16 AM Simon King simon.k...@uni-jena.de wrote:

 Hi!

 With rerere enabled in git (after a suggestion of Volker), I get
 Failed example:
 alice.pull()
 Expected:
 Merging the remote branch u/bob/ticket/1 into the local branch
 ticket/1.
 Automatic merge failed, there are conflicting commits.
 BLANKLINE
 Auto-merging alices_file
 CONFLICT (add/add): Merge conflict in alices_file
 BLANKLINE
 Please edit the affected files to resolve the conflicts. When you are
 finished,
 your resolution will be commited.
 Finished? [ok/Abort] abort
 Got:
 Merging the remote branch u/bob/ticket/1 into the local branch
 ticket/1.
 Automatic merge failed, there are conflicting commits.
 BLANKLINE
 Auto-merging alices_file
 CONFLICT (add/add): Merge conflict in alices_file
 Recorded preimage for 'alices_file'
 BLANKLINE
 Please edit the affected files to resolve the conflicts. When you are
 finished, your resolution will be commited.
 Finished? [ok/Abort] abort

 I think I reported that here before, but did not create a ticket. Did
 someone else open a ticket for it?

 Best regards,
 Simon

 --
 You received this message because you are subscribed to the Google Groups
 sage-release group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to sage-release+unsubscr...@googlegroups.com.
 To post to this group, send email to sage-release@googlegroups.com.
 Visit this group at http://groups.google.com/group/sage-release.
 For more options, visit https://groups.google.com/d/optout.


-- 
You received this message because you are subscribed to the Google Groups 
sage-release group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 6.8.rc0 released

2015-07-16 Thread Ralf Stephan

A minimal set of changes is in
http://trac.sagemath.org/ticket/18909

On Thu, Jul 16, 2015 at 9:53 AM Volker Braun vbraun.n...@gmail.com wrote:

 Probably due to #16124... Can you ellipsize the offending strings?



 On Thursday, July 16, 2015 at 9:42:39 AM UTC+2, Ralf Stephan wrote:

 make distclean; make; make ptestlong fails on OpenSuSE 13 with

 sage -t --long src/sage/dev/sagedev.py  # 2 doctests failed

 File src/sage/dev/sagedev.py, line 1145, in
 sage.dev.sagedev.SageDev.pull
 Failed example:
 alice.pull()
 Expected:
 Merging the remote branch u/bob/ticket/1 into the local branch
 ticket/1.
 Automatic merge failed, there are conflicting commits.
 BLANKLINE
 Auto-merging alices_file
 CONFLICT (add/add): Merge conflict in alices_file
 BLANKLINE
 Please edit the affected files to resolve the conflicts. When you are
 finished,
 your resolution will be commited.
 Finished? [ok/Abort] abort
 Got:
 Merging the remote branch u/bob/ticket/1 into the local branch
 ticket/1.
 Automatic merge failed, there are conflicting commits.
 BLANKLINE
 Auto-merging alices_file
 CONFLICT (add/add): Merge conflict in alices_file
 Recorded preimage for 'alices_file'
 BLANKLINE
 Please edit the affected files to resolve the conflicts. When you are
 finished, your resolution will be commited.
 Finished? [ok/Abort] abort

 They persist in manual invocation.
 Note the difference in the Please edit... line. I had these before but
 did not do a distclean. The other is in line 3130 and essentially the same.

  --
 You received this message because you are subscribed to the Google Groups
 sage-release group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to sage-release+unsubscr...@googlegroups.com.
 To post to this group, send email to sage-release@googlegroups.com.
 Visit this group at http://groups.google.com/group/sage-release.
 For more options, visit https://groups.google.com/d/optout.


-- 
You received this message because you are subscribed to the Google Groups 
sage-release group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 6.8.rc0 released

2015-07-16 Thread Ralf Stephan

make distclean; make; make ptestlong fails on OpenSuSE 13 with

sage -t --long src/sage/dev/sagedev.py  # 2 doctests failed

File src/sage/dev/sagedev.py, line 1145, in sage.dev.sagedev.SageDev.pull
Failed example:
alice.pull()
Expected:
Merging the remote branch u/bob/ticket/1 into the local branch
ticket/1.
Automatic merge failed, there are conflicting commits.
BLANKLINE
Auto-merging alices_file
CONFLICT (add/add): Merge conflict in alices_file
BLANKLINE
Please edit the affected files to resolve the conflicts. When you are
finished,
your resolution will be commited.
Finished? [ok/Abort] abort
Got:
Merging the remote branch u/bob/ticket/1 into the local branch
ticket/1.
Automatic merge failed, there are conflicting commits.
BLANKLINE
Auto-merging alices_file
CONFLICT (add/add): Merge conflict in alices_file
Recorded preimage for 'alices_file'
BLANKLINE
Please edit the affected files to resolve the conflicts. When you are
finished, your resolution will be commited.
Finished? [ok/Abort] abort

They persist in manual invocation.
Note the difference in the Please edit... line. I had these before but
did not do a distclean. The other is in line 3130 and essentially the same.

-- 
You received this message because you are subscribed to the Google Groups 
sage-release group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 6.8.beta3 released

2015-06-05 Thread Ralf Stephan

Ah no, never mind, sorry for spamming.

On Fri, Jun 5, 2015 at 8:23 AM Ralf Stephan gtrw...@gmail.com wrote:

 Something changed with package tarball handling. My development tarballs
 of pynac in upstream/ are no longer found by ./sage -sh
 sage-fix-pkg-checksums and consequently Sage tries to download them...



-- 
You received this message because you are subscribed to the Google Groups 
sage-release group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Sage 6.4.beta6 released

2014-10-15 Thread Ralf Stephan

Had to compile Atlas for three times in a row as well (beta4,5,6).
Something wrong with upgrading?

On Wed, Oct 15, 2014 at 8:47 AM, Emmanuel Charpentier 
emanuel.charpent...@gmail.com wrote:

 Did something change in Atlas ? On my fast machine (Core i7, 16 Gb RAM),
 going fro 6.4beta4 to 6.4beta6, I'm still on Atlas compilation about 10
 hours after 'export MAKE=make -j8 ; time make... This never happened on
 this machine.

 --
 Emmanuel Charpentier

 Le mardi 14 octobre 2014 22:09:23 UTC+2, Volker Braun a écrit :

 Quick update mainly to fix the Python compilation issue.

 Git develop branch or http://sage.sagedev.org/home/
 release/sage-6.4.beta6.tar.gz

 Mini-changelog:

 36c150e Updated Sage version to 6.4.beta6
 67235a8 Trac #17144: Update to flint-2.4.4
 7fd6e66 Trac #17145: Tornado depends on setuptools
 b999896 Trac #13679: Build sphinx docs for a single file
 104c68f Trac #17111: Sage is missing one letter
 86cbffe Trac #15987: Python 3 preparation: Change syntax of octal integer
 literals
 fecafe1 Trac #17094: Fix memleaks and brokenness of non-FLINT methods
 after #16803
 2fc399e Trac #16996: IPython notebook with Sage Extensions
 e828d1d Trac #17121: LatticePoset: Add meet_irreducibles, faster
 is_distributive
 d19f706 Trac #17137: IPython 2.3.0
 1f9b9ae Trac #17136: upgrade latte_int to 1.7.1, and fix the gmp config
 error
 5c75e58 Trac #17133: Partition().to_exp() should return Sage Integers
 c985399 Trac #17139: Installing local/share/sage/ext/valgrind/python.supp
 fails

  --
 You received this message because you are subscribed to the Google Groups
 sage-release group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to sage-release+unsubscr...@googlegroups.com.
 To post to this group, send email to sage-release@googlegroups.com.
 Visit this group at http://groups.google.com/group/sage-release.
 For more options, visit https://groups.google.com/d/optout.


-- 
You received this message because you are subscribed to the Google Groups 
sage-release group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 6.4.beta3 released

2014-09-11 Thread Ralf Stephan

sage -t --long src/sage/stats/distributions/discrete_gaussian_integer.pyx
**
File src/sage/stats/distributions/discrete_gaussian_integer.pyx,
line 262, in 
sage.stats.distributions.discrete_gaussian_integer.DiscreteGaussianDistributionIntegerSampler.__init__
Failed example:
min(l), max(l), abs(mean(l)-2.5)  0.01
Expected:
(-2, 7, True)
Got:
(-2, 6, True)

this is after sage -upgrade, make, make doc-clean, make doc, make ptestlong
on opensuse 12.3

Regards,

-- 
You received this message because you are subscribed to the Google Groups 
sage-release group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage-6.3.beta7 released

2014-07-29 Thread Ralf Stephan

Confirmed but for me it's (consistently)
sage -t src/sage/graphs/generators/smallgraphs.py  # 1 doctest failed
sage -t src/sage/graphs/generators/families.py  # 18 doctests failed
sage -t src/sage/graphs/base/c_graph.pyx  # 3 doctests failed
sage -t src/sage/graphs/generators/intersection.py  # 1 doctest failed
mostly because of

from sage.libs.gap.libgap import libgap
  File libgap.pyx, line 776, in init sage.libs.gap.libgap
(build/cythonized/sage/libs/gap/libgap.c:6772)
  File libgap.pyx, line 597, in sage.libs.gap.libgap.Gap.__init__
(build/cythonized/sage/libs/gap/libgap.c:4784)
  File util.pyx, line 245, in sage.libs.gap.util.initialize
(build/cythonized/sage/libs/gap/util.c:4395)
  File util.pyx, line 204, in sage.libs.gap.util.libgap_workspace
(build/cythonized/sage/libs/gap/util.c:4113)
ValueError: max() arg is an empty sequence

and I cannot make doc (after doc-clean):

[geometry ] reading sources... [ 27%] sage/geometry/lattice_polytope
Error building the documentation.
Traceback (most recent call last):
  File /home/ralf/sage/src/doc/common/builder.py, line 1490, in module
getattr(get_builder(name), type)()
  File /home/ralf/sage/src/doc/common/builder.py, line 291, in _wrapper
getattr(get_builder(document), 'inventory')(*args, **kwds)
  File /home/ralf/sage/src/doc/common/builder.py, line 502, in _wrapper
x.get(9)
  File /home/ralf/sage/local/lib/python/multiprocessing/pool.py, line
558, in get
raise self._value
ValueError: max() arg is an empty sequence



On Tue, Jul 29, 2014 at 2:30 PM, Justin C. Walker jus...@mac.com wrote:


 On Jul 28, 2014, at 19:40, Volker Braun vbraun.n...@gmail.com wrote:

 See the develop git branch or download the all-in-one tarball


 http://boxen.math.washington.edu/home/vbraun/tmp-release/sage-6.3.beta7.tar.gz


 Built w/o problems from tarball, on OS X, 10.9.4, Xcode 5.1.1.  Testing
 (‘ptestlong’) showed these failures:

 sage -t --long src/sage/graphs/generic_graph.py  # 4 doctests failed
 sage -t --long src/sage/graphs/graph.py  # 6 doctests failed
 sage -t --long src/sage/graphs/graph_list.py  # 4 doctests failed
 sage -t --long src/sage/graphs/isgci.py  # 44 doctests failed
 sage -t --long src/sage/databases/sql_db.py  # 14 doctests failed
 sage -t --long src/sage/graphs/graph_database.py  # 28 doctests failed

 Most appear to be related to “database” failures, i.e.,
   Database has no tablegraph_data.  (most failures due to this)

 Then there’s this:
  No such file or directory: '/Users/Sage/sage-6.3.beta7/lo
 cal/share/graphs/isgci_sage.xml’  (in isgci.py)

 The log file is in sage.math.washington.edu:~justin/logs/PT6.3b7.log

 Justin

 --
 Justin C. Walker, Curmudgeon-At-Large
 Institute for the Enhancement of the Director's Income
 
 Experience is what you get
   when you don't get what you want.
 



  --
 You received this message because you are subscribed to the Google Groups
 sage-release group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to sage-release+unsubscr...@googlegroups.com.
 To post to this group, send email to sage-release@googlegroups.com.
 Visit this group at http://groups.google.com/group/sage-release.
 For more options, visit https://groups.google.com/d/optout.


-- 
You received this message because you are subscribed to the Google Groups 
sage-release group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage-6.3.beta7 released

2014-07-29 Thread Ralf Stephan

On Tue, Jul 29, 2014 at 3:27 PM, Volker Braun vbraun.n...@gmail.com wrote:

 $SAGE_LOCAL/lib/libga
 p


ralf@ark:~/sage l local/lib/libgap
ls: cannot access local/lib/libgap: No such file or directory


-- 
You received this message because you are subscribed to the Google Groups 
sage-release group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Sage 6.3.beta6 released

2014-07-20 Thread Ralf Stephan


 Is there a posting/page that lists what is needed
 to get rid of the expect interface?

Wishful thinking at
http://trac.sagemath.org/ticket/16688

-- 
You received this message because you are subscribed to the Google Groups 
sage-release group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Sage 6.3.beta6 released

2014-07-19 Thread Ralf Stephan

On 19 Jul 2014 14:14, Emmanuel Charpentier emanuel.charpent...@gmail.com
wrote:

 make ptestlong got me one failure in src/sage/interfaces/expect.py at
line 796. Doctesting it standalone (./sage -t --long
src/sage/interfaces/expect.py ) was successful (All test passed!).

 Looks like a timeout due to heavy parallelism of tests.

Yes, that one is well known.
Is there a posting/page that lists what is needed
to get rid of the expect interface?

Regards,

-- 
You received this message because you are subscribed to the Google Groups 
sage-release group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 6.3.beta2 released

2014-05-29 Thread Ralf Stephan

On Thu, May 29, 2014 at 12:28 PM, Volker Braun vbraun.n...@gmail.comwrote:

 The reason is alarm() not working reliably. The failing test is from:

 5159542 Trac #16162: Cantor-Zassenhaus may enter infinite loop over
 GF(2**k) and cannot be interrupted

 but thats just the symptom not the cause.


So, should one be able to switch off those tests by giving a test option?
Or do you think it's solvable somehow to make it work in a VM? If neither,
patchbot should get some ignoring logic. What do you think best?

-- 
You received this message because you are subscribed to the Google Groups 
sage-release group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 6.3.beta2 released

2014-05-29 Thread Ralf Stephan

I have no idea about Un*x programming, has this to do with
http://trac.sagemath.org/ticket/13311 ?
Until something is done running patchbot in clouds is near useless.


On Thu, May 29, 2014 at 3:40 PM, Volker Braun vbraun.n...@gmail.com wrote:

 I think the best option is to fix the sigalarm delivery to be 100% reliable


 On Thursday, May 29, 2014 2:34:13 PM UTC+1, Ralf Stephan wrote:

 On Thu, May 29, 2014 at 12:28 PM, Volker Braun vbrau...@gmail.comwrote:

 The reason is alarm() not working reliably. The failing test is from:

 5159542 Trac #16162: Cantor-Zassenhaus may enter infinite loop over
 GF(2**k) and cannot be interrupted

 but thats just the symptom not the cause.


 So, should one be able to switch off those tests by giving a test
 option? Or do you think it's solvable somehow to make it work in a VM? If
 neither, patchbot should get some ignoring logic. What do you think best?

  --
 You received this message because you are subscribed to the Google Groups
 sage-release group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to sage-release+unsubscr...@googlegroups.com.
 To post to this group, send email to sage-release@googlegroups.com.
 Visit this group at http://groups.google.com/group/sage-release.
 For more options, visit https://groups.google.com/d/optout.


-- 
You received this message because you are subscribed to the Google Groups 
sage-release group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Sage 6.3.beta0

2014-05-13 Thread Ralf Stephan

ralf@ark:~/sage ls -l local/libexec/git-core
ls: cannot access local/libexec/git-core: No such file or directory



On Tue, May 13, 2014 at 5:27 PM, Peter Bruin pjbr...@gmail.com wrote:

 These look a lot like the failures I got after moving my Sage
 installation, and which were fixed by #15901, but that ticket was merged in
 6.3.beta0...

 Peter


 Op dinsdag 13 mei 2014 16:12:44 UTC+1 schreef Simon King:

 Hi Releasers,

 On 2014-05-11, Ralf Stephan gtr...@gmail.com wrote:
  I get doctest failures in dev/sagedev.py that go away when I switch to
  master and make, but won't go away in develop with make (at least not
  always 8-/).

 Just for the record, testing dev/sagedev.py with the sage-6.3.beta0
 branch results in
   sage -t src/sage/dev/sagedev_wrapper.py  # 1 doctest failed
   sage -t src/sage/dev/patch.py  # 8 doctests failed
   sage -t src/sage/dev/sagedev.py  # 272 doctests failed
   sage -t src/sage/dev/git_interface.py  # 2 doctests failed
   sage -t src/sage/dev/test/sagedev.py  # 3 doctests failed

 Cheers,
 Simon

  --
 You received this message because you are subscribed to the Google Groups
 sage-release group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to sage-release+unsubscr...@googlegroups.com.
 To post to this group, send email to sage-release@googlegroups.com.
 Visit this group at http://groups.google.com/group/sage-release.
 For more options, visit https://groups.google.com/d/optout.


-- 
You received this message because you are subscribed to the Google Groups 
sage-release group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Sage 6.3.beta1 released

2014-05-13 Thread Ralf Stephan

GIT_EXEC_PATH=/home/ralf/sage/local/libexec/git-core
but git is in local/bin/?


On Tue, May 13, 2014 at 5:46 PM, Simon King simon.k...@uni-jena.de wrote:

 Hi Volker,

 On 2014-05-13, Volker Braun vbraun.n...@gmail.com wrote:
  Get it from the updated develop git branch or the source tarball

 You mean I shall now pull from trac?

 Anyway, with commit fa885d90d609c8311d8fa52deac1340cd558b5a9 I get, for
 example:

 **
 File src/sage/dev/test/sagedev.py, line 189, in
 sage.dev.test.sagedev.two_user_setup
 Failed example:
 alice, alice_config, bob, bob_config, server = two_user_setup()
 Expected nothing
 Got:
 GitError: git exited with a non-zero exit code (1).
 This happened while executing git -c user.email=d...@test.test -c
 user.name=alice pull
 /home/king/.sage/temp/linux-etl7.site/9042/dir_mHgsA5/repo master.
 git printed nothing to STDOUT.
 git printed the following to STDERR:
 git: 'pull' is not a git command. See 'git --help'.
 BLANKLINE
 Did you mean this?
 shell
 GitError: git exited with a non-zero exit code (1).
 This happened while executing git -c user.email=d...@test.test -c
 user.name=bob pull
 /home/king/.sage/temp/linux-etl7.site/9042/dir_mHgsA5/repo master.
 git printed nothing to STDOUT.
 git printed the following to STDERR:
 git: 'pull' is not a git command. See 'git --help'.
 BLANKLINE
 Did you mean this?
 shell

 or

 **
 File src/sage/dev/git_interface.py, line 556, in
 sage.dev.git_interface.GitInterface.get_state
 Failed example:
 git.super_silent.rebase(abort=True)
 Exception raised:
 Traceback (most recent call last):
   File
 /home/king/Sage/git/sage/local/lib/python2.7/site-packages/sage/doctest/forker.py,
 line 480, in _run
 self.execute(example, compiled, test.globs)
   File
 /home/king/Sage/git/sage/local/lib/python2.7/site-packages/sage/doctest/forker.py,
 line 839, in execute
 exec compiled in globs
   File doctest sage.dev.git_interface.GitInterface.get_state[24],
 line 1, in module
 git.super_silent.rebase(abort=True)
   File
 /home/king/Sage/git/sage/local/lib/python2.7/site-packages/sage/dev/git_interface.py,
 line 1199, in meth
 return self(git_cmd, *args, **kwds)
   File
 /home/king/Sage/git/sage/local/lib/python2.7/site-packages/sage/dev/git_interface.py,
 line 299, in _execute_supersilent
 raise GitError(exit_code, cmd, stdout, stderr)
 GitError: git returned with non-zero exit code (1) for git -c
 user.email=d...@test.test -c user.name=doctest rebase --abort.
 output to stderr: git: 'rebase' is not a git command. See 'git --help'.

 or

 **
 File src/sage/dev/sagedev.py, line 5121, in
 sage.dev.sagedev.SageDev._current_ticket
 Failed example:
 dev.checkout(ticket=1)
 Exception raised:
 Traceback (most recent call last):
   File
 /home/king/Sage/git/sage/local/lib/python2.7/site-packages/sage/doctest/forker.py,
 line 480, in _run
 self.execute(example, compiled, test.globs)
   File
 /home/king/Sage/git/sage/local/lib/python2.7/site-packages/sage/doctest/forker.py,
 line 839, in execute
 exec compiled in globs
   File doctest sage.dev.sagedev.SageDev._current_ticket[7], line
 1, in module
 dev.checkout(ticket=Integer(1))
   File
 /home/king/Sage/git/sage/local/lib/python2.7/site-packages/sage/dev/sagedev.py,
 line 342, in checkout
 self.checkout_ticket(ticket=ticket, branch=branch, base=base)
   File
 /home/king/Sage/git/sage/local/lib/python2.7/site-packages/sage/dev/sagedev.py,
 line 765, in checkout_ticket
 self.git.silent.branch(branch, MASTER_BRANCH)
   File
 /home/king/Sage/git/sage/local/lib/python2.7/site-packages/sage/dev/git_interface.py,
 line 1199, in meth
 return self(git_cmd, *args, **kwds)
   File
 /home/king/Sage/git/sage/local/lib/python2.7/site-packages/sage/dev/git_interface.py,
 line 268, in _execute_silent
 raise GitError(exit_code, cmd, stdout, stderr)
 GitError: git returned with non-zero exit code (128) for git -c
 user.email=d...@test.test -c user.name=doctest branch ticket/1 master.
 output to stderr: fatal: Not a valid object name: 'master'.

 Will now try to pull from trac...

 Best regards,
 Simon


 --
 You received this message because you are subscribed to the Google Groups
 sage-release group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to sage-release+unsubscr...@googlegroups.com.
 To post to this group, send email to sage-release@googlegroups.com.
 Visit this group at http://groups.google.com/group/sage-release.
 For more options, visit https://groups.google.com/d/optout.


-- 
You received this message because you are subscribed to the Google

[sage-release] Re: Sage 6.2.beta7 released

2014-04-08 Thread Ralf Stephan

Barfs in make doc here (after make):

 -f local/etc/sage-started.txt ] || local/bin/sage-starts
build/pipestatus ./sage --docbuild --no-pdf-links all html  21 tee -a 
logs/dochtml.log
Traceback (most recent call last):
  File /home/ralf/sage/src/doc/common/builder.py, line 28, in module
from sage.misc.misc import sage_makedirs as mkdir
  File 
/home/ralf/sage/local/lib/python2.7/site-packages/sage/misc/misc.py, line 
39, in module
import sage.misc.prandom as random
  File 
/home/ralf/sage/local/lib/python2.7/site-packages/sage/misc/prandom.py, 
line 58, in module
from sage.misc.randstate import current_randstate
ImportError: libntl.so.2: cannot open shared object file: No such file or 
directory
make: *** [doc-html] Error 1

-- 
You received this message because you are subscribed to the Google Groups 
sage-release group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

81 matches

Mail list logo