giacpy_sage fails to install

[Markus Wageringel]

I have just tried to upgrade my main Sage install from 8.7 to 8.8, but the optional package Giacpy_sage fails to build. The logs mention several errors reported by gcc – the log file is attached. This is on OS X 10.13.6 with Clang 10.0.0, but I have observed this problem on a Linux machine as well (where I also tried a clean install, but the package still does not build). This is odd, as Giacpy_sage has not been changed since 8.7.

Best,

Markus

[Samuel Lelievre]

Fri 2019-06-28 16:27:59 UTC, Markus Wageringel:

Unless you depend critically on the few parts of Sage that have not

yet been made to work with Python 3, why not build Sage for Python 3?

To do that, instead of 'make', type

    make configure

    ./configure --with-python=3

    make

[Markus Wageringel]

Oh, I do that for developing. Yet, although I am looking forward to using Python 3, I prefer to have a reliable stable install as well. I had some trouble with compiling the betas a few times in the past when I ended up without a working copy of Sage. The full compilation process takes hours on my laptop, so I usually try to avoid it.

[François Bissey]

Fill a bug on the tracker. giacpy_sage is using CC when it should use CXX with c++11
standard options. This is why it is failing
1) compile with gcc instead g++
2) complaints about the use c++11 “extensions” which of course shouldn’t be available
from plain “gcc”.

> --
> You received this message because you are subscribed to the Google Groups "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+...@googlegroups.com.
> To post to this group, send email to sage-...@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-devel.
> To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/5f4ace6f-e0dd-46d5-81e4-750a2ed2800a%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
> <giacpy_sage-0.6.7.log>

[Markus Wageringel]

Thanks for the explanation. This is now #28082.