I see a reproducible (since few previous betas, in fact) error:
(sometimes it's only one [Errno 2], sometimes two)
sage -t --warn-long 96.3 src/sage/homology/simplicial_complex.py
**
File
On several OS X machines, pynac-0.7.3 fails to build. Could this be because
gcc hasn't been updated? (I see that the current version is 5.4.0, but
running 'make' when I have 4.9.3.p1 installed does not trigger a rebuild of
gcc.) A snippet from the pynac log file:
In file included from
Thats https://trac.sagemath.org/ticket/15585
On Friday, January 6, 2017 at 12:11:01 PM UTC+1, Dima Pasechnik wrote:
>
> I see a reproducible (since few previous betas, in fact) error:
> (sometimes it's only one [Errno 2], sometimes two)
>
> sage -t --warn-long 96.3
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.
On Friday, January 6, 2017 at 1:35:16 PM UTC-8, John H Palmieri wrote:
>
> On several OS X machines, pynac-0.7.3 fails to build. Could this be
> because gcc hasn't
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)
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
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
I am not sure there is a released version with the stuff from that bug.
I am not sure that’s the whole story either, Looking at the first lines
of Justin’s log lead me to that bug.
But the bug is primarily about warnings although it mention problems
with weak symbols.
Because of problems with
OK the bug from bugzilla is orthogonal to the toupper/tolower issue
at hand which seems to be a clash between C++ methods and libc symbols.
May be a macro is throwing confusion. I’ll see if I can find something before
signing off for the next week.
> On 7/01/2017, at 19:34, Francois Bissey
In case anyone has time to look at it, I posted a link to my pynac log at
#22136.
John
On Friday, January 6, 2017 at 8:38:19 PM UTC-8, François wrote:
>
> I am not sure there is a released version with the stuff from that bug.
> I am not sure that’s the whole story either, Looking at the
Right! I said Justin but it was your log I inspected.
> On 7/01/2017, at 19:30, John H Palmieri wrote:
>
> In case anyone has time to look at it, I posted a link to my pynac log at
> #22136.
This email may be confidential and subject to legal privilege, it may
not
On Debian testing, with some patches (python2 2.7.13 + R 3.3.2), passes
ptestlong with three failures :
--
sage -t --long --warn-long 103.1 src/sage/tests/cmdline.py # 2 doctests
failed
sage -t --long --warn-long 103.1
>From a fresh git clone + pull develop on Ubuntu 16.04 x86_64 Xeon E5-2623 +
16 GB RAM: build OK + make ptestlong passed.
Besides, I confirm that the update to pynac-0.7.3 fixes the bug reported at
https://groups.google.com/d/msg/sage-devel/1cSEoYlVBZw/EkB77-vECwAJ
--
You received this
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
a6f8b9c Updated SageMath version to 7.5.rc2
d7bfc5b Trac #22136: Upgrade to pynac-0.7.3
e82c80c Updated SageMath
14 matches
Mail list logo