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

[François Bissey]

Thanks there was exactly what I was after - or almost
CLANG_DEFAULT_RTLIB
which may be needed for https://trac.sagemath.org/ticket/24712

> On 12/02/2018, at 21:22, Ralf Stephan  wrote:
> 
> 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  wrote:
> 
> 
> > On 12/02/2018, at 20:06, Ralf Stephan  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.

-- 
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

[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 
wrote:

>
>
> > On 12/02/2018, at 20:06, Ralf Stephan  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

[François Bissey]

> On 12/02/2018, at 20:06, Ralf Stephan  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.

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

[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  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  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  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 
>>> wrote:
>>>
 Hi!

 On 2018-02-11, Ralf Stephan  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

[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  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  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 
>> wrote:
>>
>>> Hi!
>>>
>>> On 2018-02-11, Ralf Stephan  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

[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  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 
> wrote:
>
>> Hi!
>>
>> On 2018-02-11, Ralf Stephan  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

[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  wrote:

> Hi!
>
> On 2018-02-11, Ralf Stephan  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

[François Bissey]

> On 11/02/2018, at 10:36, Simon King  wrote:
> 
>> 
>> Ubuntu is probably the most used distro if someone can wipe up some 
>> instructions
>> on what to install that would help greatly.
> 
> Well, so far I was installing clang, clang-dev and libc++abi-dev. The
> latter was in order to get __cxxabi_config.h. However, even after
> installing libc++abi-dev (which according to a duckduckgo search is
> providing the missing header), brial fails to build for the same reason,
> it cannot find __cxxabi_config.h.

It looks like you may have to provide the include path to __cxxabi_config.h.
I don’t know where ubuntu installs it. On Gentoo libcxx is configured at build
time with the right location with the “USE” variable I provided.
So you may have to have
CXX=“clang++ -I/path/to/cxxabi -stdlib=libc++”

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.

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

[Dima Pasechnik]

On Saturday, February 10, 2018 at 2:09:58 PM UTC, Ralf Stephan wrote:
>
> Also clang-5.0.0 cannot compile ppl. clang-3.8 and 4.0.1 are fine.
> https://trac.sagemath.org/ticket/24704
>

I think I reported this on PPL bug tracker some time ago...
  

>
>
> On Sat, Feb 10, 2018 at 2:52 PM Ralf Stephan  > wrote:
>
>> 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...@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.

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

[François Bissey]

I am sorry to have cause everyone who wanted to try it on linux so much
grief.
To summarise 
* you need to build from scratch
* clang using libstdc++ from gcc appears to have problems - at the moment
I don’t know if it is just because the gcc in question is too old or that’s
a no go.
* if you switch from clang+libstdc++ to clang+libc++ (or libcxx depending on
your distro) you have to do a distclean as they don’t mix.
* You may need to set CXX to “clang++ --stdlib=libc++” if your distro default
to using libstdc++.

Ubuntu is probably the most used distro if someone can wipe up some instructions
on what to install that would help greatly.

For gentoo setting USE="default-compiler-rt default-libcxx compiler-rt libcxx 
libcxxabi”
should get you something usable with libc++ as the default for clang++.

Can people copy me (fbissey) on bugs they have with clang-5.0 (or even 6.0)
and I’ll look at them.

François

> On 11/02/2018, at 07:52, Simon King  wrote:
> 
> In the failing compilation, we have
> 
> clang++ --stdlib=libc++ [which is what we want]
>... -std=c++11 [which comes from brial]
>... -c BlockDegLexOrder.cc  -fPIC -DPIC -o .libs/BlockDegLexOrder.o
> 
> And the error is then
>/usr/include/c++/v1/cxxabi.h:21:10: fatal error: '__cxxabi_config.h'
>file not found
>#include <__cxxabi_config.h>
> 
> So, it seems (after some duckduckgoing) that I also need to install
>libc++abi-dev
> 
> Hence, I had to install clang, clang-dev, libc++abi-dev so far. These
> things should (if clang is supposed to be a serious option for Sage) be
> mentioned in the documentation, as prerequisites.
> 
> Since I have enough time, I am starting over from scratch (i.e., make
> distclean)
> 
> Regards,
> Simon
> 
> 
> On 2018-02-10, Simon King  wrote:
>> Hi!
>> 
>> After installation of clang-dev, I tried again, but alas, brial failed
>> to build again.
>> 
>> Log is at
>> http://users.minet.uni-jena.de/cohomology/logs/brial-1.0.1.p2.log
>> 
>> So, I am giving up on it for now.
>> 
>> 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

[John Cremona]

I installed clang on my ubuntu laptop.  I use synaptic ( a front-end for
apt & co) for installing stuff as it's easier to search.  There's a package
"clang" and I have clang-3.8 installed as well as libclang-common-3.8-dev
(and there are others like tthat with 3.8 replaced by other versions), also
libclang1-3.8.

I have not tried to build Sage with all this but have been working on
getting eclib to build and pass tests with clang, which is part of what is
needed for Sage.  (Currently everything works expect a small number of
eclib's tests owing to numerical fuzz).

John

On 10 February 2018 at 16:43, Simon King  wrote:

> On 2018-02-10, Simon King  wrote:
> > I'll try to search for "clang-devel ubuntu".
>
> No real success, except for some very complicated procedures
> given at
> https://askubuntu.com/questions/309786/llvm-and-
> clang-installation-on-ubuntu
> and lots of stuff that isn't mentioning ubuntu.
>
> So, probably time to give up the idea of trying Sage with clang on my
> laptop.
>
> Best regards,
> Simovery complicated procedures
> given at
> https://askubuntu.com/questions/309786/llvm-and-
> clang-installation-on-ubuntu
> and lots of stuff that isn't mentioning ubuntu.
>
> So, probably time to give up the idea of trying Sage with clang on my
> laptop.
>
> 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

[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  wrote:

> On 2018-02-10, Ralf Stephan  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

[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  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  wrote:
>
>> Hi Ralf,
>>
>> On 2018-02-10, Ralf Stephan  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

[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  wrote:

> Hi Ralf,
>
> On 2018-02-10, Ralf Stephan  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

[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

[François Bissey]

> On 11/02/2018, at 00:02, Simon King  wrote:
> 
>> s 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
> 

OK, that’s a curiosity that will have to be investigated.

> Does that mean python_openid will in fact not be build with clang?
> Wouldn't that create a mess?

Depends. Pure C is totally ABI compatible so you can mix
stuff compiled with clang and gcc. C++ is a different beast,
While there is supposed to be some level of ABI compatibility
libstdc++ (GCC) and libcxx (clang) are not interchangeable.
Mixing clang++ and g++ libraries/executables will end up in a 
“total mess".

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.

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

[François Bissey]

> On 10/02/2018, at 23:49, 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.
> 
> Will the SageMath installation recall that it was installed with clang?
> By that, I mean: What will happen if I do further compilations later,
> either with `sage -b`, `sage -i meataxe` or `make build`? Will all three
> commands automatically use clang? Or would I still need to prepend
> everything with `CC=clang CXX=clang++`?

Sage remembers the compiler it was built with. I saw to that
some times ago as a pre-requisite for clang support.
So once you have configured sage, it will now the compiler it has to
use. And ./sage -i meataxe will just use clang/clang++ if sage
was built with it.

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.

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

[François Bissey]

> On 10/02/2018, at 22:02, Simon King  wrote:
> 
> 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. 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.
> 
> How? By doing
>  CC=clang CXX=clang++ make -stdlib=libc++
> or what?

It depends on how clang was built and packaged mostly, so hopefully 
just 
CC=clang CXX=clang++ make
is enough.

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.

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

[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] Re: Sage 8.2.beta5 released

[François Bissey]

> On 10/02/2018, at 21:25, Simon King  wrote:
> 
> Here are reports that with clang things won't work in different ways
> (e.g., IIUC, segfaults in linbox on openSuse). Does that mean clang is
> buggy resp. not mature enough, or does that mean clang uncovers real
> bugs that are silently ignored by gcc?
> 

Sometimes it uncovers GNUisms. Where you are relying on the behaviour of
the compiler rather than the standard. Bugs, quite possibly, I’d have to
go through the ticket for a memory refresh.
The segfault over linbox I think is because not all installation of clang 
are equal. You can have a full clang with clang’s libc++ for standard c++
library. Or has breed like opensuse where clang use libstdc++ from gcc -
in this case 4.8. I think what’s happening there is that linbox has gone
full c++11 but libstdc++ from gcc-4.8 has only partial support.

> And if I want to give it a try: Currently I have a SageMath installation
> compiled with gcc. Does it suffice to "make clean" before starting
> re-installation of SageMath with clang? Or "make distclean"?

make distclean
definitely.

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.

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

[fchapoton2]

This is way above my understanding of "make" matters. So help from Erik or 
Jeroen or whoever is knowledgeable in this kind of things, is required.



Le vendredi 9 février 2018 21:24:34 UTC+1, Volker Braun a écrit :
>
> Can you first set up a makefile target that is supposed to be tested? E.g. 
> "make test-python3" builds with py3 and eventually gets extended to test 
> things that already work? 
>
>
> On Friday, February 9, 2018 at 9:15:04 PM UTC+1, fchap...@gmail.com wrote:
>>
>> Volker, it would be great (and I would appreciate) if you could set up a 
>> buildbot that checks that sage builds with python3. One can not yet say 
>> that vanilla-sage builds and starts with "export SAGE_PYTHON3=yes", but at 
>> least it builds (since some time already). Starting is another matter, but 
>> maybe not so far.
>>
>> This would help to prevent any regression,as the one that just happened 
>> with subprocess32.
>>
>> Le vendredi 9 février 2018 20:15:13 UTC+1, Jeroen Demeyer a écrit :
>>>
>>> On 2018-02-09 17:55, fchap...@gmail.com wrote: 
>>> > I have a build failure in subprocess32 on a python3 build (using 
>>> export 
>>> > SAGE_PYTHON3=yes) 
>>>
>>> Fixed in https://trac.sagemath.org/ticket/24650 
>>>
>>

-- 
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

[Volker Braun]

Can you first set up a makefile target that is supposed to be tested? E.g. 
"make test-python3" builds with py3 and eventually gets extended to test 
things that already work? 


On Friday, February 9, 2018 at 9:15:04 PM UTC+1, fchap...@gmail.com wrote:
>
> Volker, it would be great (and I would appreciate) if you could set up a 
> buildbot that checks that sage builds with python3. One can not yet say 
> that vanilla-sage builds and starts with "export SAGE_PYTHON3=yes", but at 
> least it builds (since some time already). Starting is another matter, but 
> maybe not so far.
>
> This would help to prevent any regression,as the one that just happened 
> with subprocess32.
>
> Le vendredi 9 février 2018 20:15:13 UTC+1, Jeroen Demeyer a écrit :
>>
>> On 2018-02-09 17:55, fchap...@gmail.com wrote: 
>> > I have a build failure in subprocess32 on a python3 build (using export 
>> > SAGE_PYTHON3=yes) 
>>
>> Fixed in https://trac.sagemath.org/ticket/24650 
>>
>

-- 
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

[fchapoton2]

Volker, it would be great (and I would appreciate) if you could set up a 
buildbot that checks that sage builds with python3. One can not yet say 
that vanilla-sage builds and starts with "export SAGE_PYTHON3=yes", but at 
least it builds (since some time already). Starting is another matter, but 
maybe not so far.

This would help to prevent any regression,as the one that just happened 
with subprocess32.

Le vendredi 9 février 2018 20:15:13 UTC+1, Jeroen Demeyer a écrit :
>
> On 2018-02-09 17:55, fchap...@gmail.com  wrote: 
> > I have a build failure in subprocess32 on a python3 build (using export 
> > SAGE_PYTHON3=yes) 
>
> Fixed in https://trac.sagemath.org/ticket/24650 
>

-- 
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

[Jeroen Demeyer]

On 2018-02-09 17:55, fchapot...@gmail.com wrote:

I have a build failure in subprocess32 on a python3 build (using export
SAGE_PYTHON3=yes)


Fixed in https://trac.sagemath.org/ticket/24650

--
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

[François Bissey]

OK, that’s a slightly different issue. I didn’t think that would be a problem 
but this
package shouldn’t be needed with python3.2+ since it is a backport of 
functionality for
older python. So it would be best not to install it with python3.

> On 10/02/2018, at 05:55, fchapot...@gmail.com wrote:
> 
> I have a build failure in subprocess32 on a python3 build (using export 
> SAGE_PYTHON3=yes)
> 
> 
> [subprocess32-3.2.7] Found local metadata for subprocess32-3.2.7
> [subprocess32-3.2.7] Attempting to download package subprocess32-3.2.7.tar.gz 
> from mirrors
> [subprocess32-3.2.7] 
> http://www.mirrorservice.org/sites/www.sagemath.org/spkg/upstream/subprocess32/subprocess32-3.2.7.tar.gz
> [subprocess32-3.2.7] 
> [..]
> [subprocess32-3.2.7] subprocess32-3.2.7
> [subprocess32-3.2.7] 
> [subprocess32-3.2.7] Setting up build directory for subprocess32-3.2.7
> [subprocess32-3.2.7] Finished extraction
> [subprocess32-3.2.7] No patch files found in ../patches
> [subprocess32-3.2.7] 
> [subprocess32-3.2.7] Host system:
> [subprocess32-3.2.7] Linux pc-chapoton 4.13.0-32-generic #35-Ubuntu SMP Thu 
> Jan 25 09:13:46 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
> [subprocess32-3.2.7] 
> [subprocess32-3.2.7] C compiler: gcc
> [subprocess32-3.2.7] C compiler version:
> [subprocess32-3.2.7] Using built-in specs.
> [subprocess32-3.2.7] COLLECT_GCC=gcc
> [subprocess32-3.2.7] 
> COLLECT_LTO_WRAPPER=/home/chapoton/sage3/local/libexec/gcc/x86_64-pc-linux-gnu/7.2.0/lto-wrapper
> [subprocess32-3.2.7] Target: x86_64-pc-linux-gnu
> [subprocess32-3.2.7] Configured with: ../src/configure 
> --prefix=/home/chapoton/sage3/local 
> --with-local-prefix=/home/chapoton/sage3/local 
> --with-gmp=/home/chapoton/sage3/local --with-mpfr=/home/chapoton/sage3/local 
> --with-mpc=/home/chapoton/sage3/local --with-system-zlib --disable-multilib 
> --disable-nls --enable-languages=c,c++,fortran --disable-libitm  
> [subprocess32-3.2.7] Thread model: posix
> [subprocess32-3.2.7] gcc version 7.2.0 (GCC) 
> [subprocess32-3.2.7] 
> [subprocess32-3.2.7] Installing subprocess32-3.2.7
> [subprocess32-3.2.7] This backport is for Python 2.x only.
> [subprocess32-3.2.7] Error: could not determine package name
> [subprocess32-3.2.7] 
> 
> [subprocess32-3.2.7] Error installing subprocess32-3.2.7
> [subprocess32-3.2.7] 
> 
> [subprocess32-3.2.7] 
> [subprocess32-3.2.7] real 0m0.131s
> [subprocess32-3.2.7] user 0m0.056s
> [subprocess32-3.2.7] sys  0m0.001s
> [subprocess32-3.2.7] 
> 
> [subprocess32-3.2.7] Error installing package subprocess32-3.2.7
> [subprocess32-3.2.7] 
> 
> [subprocess32-3.2.7] Please email sage-devel 
> (http://groups.google.com/group/sage-devel)
> [subprocess32-3.2.7] explaining the problem and including the log file
> [subprocess32-3.2.7]   /home/chapoton/sage3/logs/pkgs/subprocess32-3.2.7.log
> [subprocess32-3.2.7] Describe your computer, operating system, etc.
> [subprocess32-3.2.7] If you want to try to fix the problem yourself, *don't* 
> just cd to
> [subprocess32-3.2.7] 
> /home/chapoton/sage3/local/var/tmp/sage/build/subprocess32-3.2.7 and type 
> 'make' or whatever is appropriate.
> [subprocess32-3.2.7] Instead, the following commands setup all environment 
> variables
> [subprocess32-3.2.7] correctly and load a subshell for you to debug the error:
> [subprocess32-3.2.7]   (cd 
> '/home/chapoton/sage3/local/var/tmp/sage/build/subprocess32-3.2.7' && 
> '/home/chapoton/sage3/sage' --sh)
> [subprocess32-3.2.7] When you are done debugging, you can type "exit" to 
> leave the subshell.
> [subprocess32-3.2.7] 
> 
> Makefile:2950 : la recette pour la cible « 
> /home/chapoton/sage3/local/var/lib/sage/installed/subprocess32-3.2.7 » a 
> échouée
> make[2]: *** 
> [/home/chapoton/sage3/local/var/lib/sage/installed/subprocess32-3.2.7] Erreur 
> 1
> 
> 
> 
> Le vendredi 9 février 2018 09:25:28 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
> 
> 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
> 

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

[Jeroen Demeyer]

On 2018-02-09 12:02, François Bissey wrote:

We have seen an instance of that problem during review
but we thought it was fixed.


That was a different issue. While the error message was the same, the 
underlying reason was different.


--
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

[Jeroen Demeyer]

I think I understand why this might happen:
https://trac.sagemath.org/ticket/24694

--
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

[fchapoton2]

I sent something at your lri adress.

Le vendredi 9 février 2018 13:52:24 UTC+1, Jeroen Demeyer a écrit :
>
> On 2018-02-09 11:56, fchap...@gmail.com  wrote: 
> > An incremental build from previous beta fails on gfortran : 
>
> Please do 
>
> touch configure.ac && make build 
>
> and send me the full output. 
>

-- 
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

[Jeroen Demeyer]

On 2018-02-09 11:56, fchapot...@gmail.com wrote:

An incremental build from previous beta fails on gfortran :


Please do

touch configure.ac && make build

and send me the full output.

--
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

[fchapoton2]

I did a make distclean and make. Everything built smoothly.

Le vendredi 9 février 2018 12:10:40 UTC+1, François Bissey a écrit :
>
> Actually if you have the autotools packages installed (from the system or 
> sage) 
> can you try 
> autoreconf -i 
> then re-run configure and see if that fix it. 
>
> > On 10/02/2018, at 00:02, François Bissey  > wrote: 
> > 
> > Which version of ubuntu? We have seen an instance of that problem during 
> review 
> > but we thought it was fixed. OK, there was something nagging me but it 
> looked 
> > fixed on the patchbot. 
> > 
> >> On 9/02/2018, at 23:56, fchap...@gmail.com  wrote: 
> >> 
> >> An incremental build from previous beta fails on gfortran : 
> >> 
> >> [gfortran-7.2.0] Found local metadata for gfortran-7.2.0 
> >> [gfortran-7.2.0] Using cached file 
> /home/chapoton/sage/upstream/gcc-7.2.0.tar.xz 
> >> [gfortran-7.2.0] gfortran-7.2.0 
> >> [gfortran-7.2.0]  
> >> [gfortran-7.2.0] Setting up build directory for gfortran-7.2.0 
> >> [gfortran-7.2.0] Finished extraction 
> >> [gfortran-7.2.0] No patch files found in ../patches 
> >> [gfortran-7.2.0]  
> >> [gfortran-7.2.0] Host system: 
> >> [gfortran-7.2.0] Linux pc-chapoton 4.13.0-32-generic #35-Ubuntu SMP Thu 
> Jan 25 09:13:46 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux 
> >> [gfortran-7.2.0]  
> >> [gfortran-7.2.0] C compiler: gcc 
> >> [gfortran-7.2.0] C compiler version: 
> >> [gfortran-7.2.0] Using built-in specs. 
> >> [gfortran-7.2.0] COLLECT_GCC=gcc 
> >> [gfortran-7.2.0] 
> COLLECT_LTO_WRAPPER=/home/chapoton/sage/local/libexec/gcc/x86_64-pc-linux-gnu/7.2.0/lto-wrapper
>  
>
> >> [gfortran-7.2.0] Target: x86_64-pc-linux-gnu 
> >> [gfortran-7.2.0] Configured with: ../src/configure 
> --prefix=/home/chapoton/sage/local 
> --with-local-prefix=/home/chapoton/sage/local 
> --with-gmp=/home/chapoton/sage/local --with-mpfr=/home/chapoton/sage/local 
> --with-mpc=/home/chapoton/sage/local --with-system-zlib --disable-multilib 
> --disable-nls --enable-languages=c,c++,fortran --disable-libitm   
> >> [gfortran-7.2.0] Thread model: posix 
> >> [gfortran-7.2.0] gcc version 7.2.0 (GCC) 
> >> [gfortran-7.2.0]  
> >> [gfortran-7.2.0] Error: gcc is already installed 
> >> [gfortran-7.2.0] 
> >> [gfortran-7.2.0] real0m0.003s 
> >> [gfortran-7.2.0] user0m0.004s 
> >> [gfortran-7.2.0] sys0m0.000s 
> >> [gfortran-7.2.0] 
>  
> >> [gfortran-7.2.0] Error installing package gfortran-7.2.0 
> >> [gfortran-7.2.0] 
>  
> >> 
> >> 
> >> Le vendredi 9 février 2018 09:25:28 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 
> >> 
> >> 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: 

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

[François Bissey]

Actually if you have the autotools packages installed (from the system or sage)
can you try 
autoreconf -i
then re-run configure and see if that fix it. 

> On 10/02/2018, at 00:02, François Bissey  wrote:
> 
> Which version of ubuntu? We have seen an instance of that problem during 
> review
> but we thought it was fixed. OK, there was something nagging me but it looked 
> fixed on the patchbot.
> 
>> On 9/02/2018, at 23:56, fchapot...@gmail.com wrote:
>> 
>> An incremental build from previous beta fails on gfortran :
>> 
>> [gfortran-7.2.0] Found local metadata for gfortran-7.2.0
>> [gfortran-7.2.0] Using cached file 
>> /home/chapoton/sage/upstream/gcc-7.2.0.tar.xz
>> [gfortran-7.2.0] gfortran-7.2.0
>> [gfortran-7.2.0] 
>> [gfortran-7.2.0] Setting up build directory for gfortran-7.2.0
>> [gfortran-7.2.0] Finished extraction
>> [gfortran-7.2.0] No patch files found in ../patches
>> [gfortran-7.2.0] 
>> [gfortran-7.2.0] Host system:
>> [gfortran-7.2.0] Linux pc-chapoton 4.13.0-32-generic #35-Ubuntu SMP Thu Jan 
>> 25 09:13:46 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
>> [gfortran-7.2.0] 
>> [gfortran-7.2.0] C compiler: gcc
>> [gfortran-7.2.0] C compiler version:
>> [gfortran-7.2.0] Using built-in specs.
>> [gfortran-7.2.0] COLLECT_GCC=gcc
>> [gfortran-7.2.0] 
>> COLLECT_LTO_WRAPPER=/home/chapoton/sage/local/libexec/gcc/x86_64-pc-linux-gnu/7.2.0/lto-wrapper
>> [gfortran-7.2.0] Target: x86_64-pc-linux-gnu
>> [gfortran-7.2.0] Configured with: ../src/configure 
>> --prefix=/home/chapoton/sage/local 
>> --with-local-prefix=/home/chapoton/sage/local 
>> --with-gmp=/home/chapoton/sage/local --with-mpfr=/home/chapoton/sage/local 
>> --with-mpc=/home/chapoton/sage/local --with-system-zlib --disable-multilib 
>> --disable-nls --enable-languages=c,c++,fortran --disable-libitm  
>> [gfortran-7.2.0] Thread model: posix
>> [gfortran-7.2.0] gcc version 7.2.0 (GCC) 
>> [gfortran-7.2.0] 
>> [gfortran-7.2.0] Error: gcc is already installed
>> [gfortran-7.2.0] 
>> [gfortran-7.2.0] real0m0.003s
>> [gfortran-7.2.0] user0m0.004s
>> [gfortran-7.2.0] sys 0m0.000s
>> [gfortran-7.2.0] 
>> 
>> [gfortran-7.2.0] Error installing package gfortran-7.2.0
>> [gfortran-7.2.0] 
>> 
>> 
>> 
>> Le vendredi 9 février 2018 09:25:28 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
>> 
>> 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 

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

[fchapoton2]

ubuntu 17.10. There is also at least one patchbot having the same issue, see

https://patchbot.sagemath.org/ticket/0/

Le vendredi 9 février 2018 12:02:28 UTC+1, François Bissey a écrit :
>
> Which version of ubuntu? We have seen an instance of that problem during 
> review 
> but we thought it was fixed. OK, there was something nagging me but it 
> looked 
> fixed on the patchbot. 
>
> > On 9/02/2018, at 23:56, fchap...@gmail.com  wrote: 
> > 
> > An incremental build from previous beta fails on gfortran : 
> > 
> > [gfortran-7.2.0] Found local metadata for gfortran-7.2.0 
> > [gfortran-7.2.0] Using cached file 
> /home/chapoton/sage/upstream/gcc-7.2.0.tar.xz 
> > [gfortran-7.2.0] gfortran-7.2.0 
> > [gfortran-7.2.0]  
> > [gfortran-7.2.0] Setting up build directory for gfortran-7.2.0 
> > [gfortran-7.2.0] Finished extraction 
> > [gfortran-7.2.0] No patch files found in ../patches 
> > [gfortran-7.2.0]  
> > [gfortran-7.2.0] Host system: 
> > [gfortran-7.2.0] Linux pc-chapoton 4.13.0-32-generic #35-Ubuntu SMP Thu 
> Jan 25 09:13:46 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux 
> > [gfortran-7.2.0]  
> > [gfortran-7.2.0] C compiler: gcc 
> > [gfortran-7.2.0] C compiler version: 
> > [gfortran-7.2.0] Using built-in specs. 
> > [gfortran-7.2.0] COLLECT_GCC=gcc 
> > [gfortran-7.2.0] 
> COLLECT_LTO_WRAPPER=/home/chapoton/sage/local/libexec/gcc/x86_64-pc-linux-gnu/7.2.0/lto-wrapper
>  
>
> > [gfortran-7.2.0] Target: x86_64-pc-linux-gnu 
> > [gfortran-7.2.0] Configured with: ../src/configure 
> --prefix=/home/chapoton/sage/local 
> --with-local-prefix=/home/chapoton/sage/local 
> --with-gmp=/home/chapoton/sage/local --with-mpfr=/home/chapoton/sage/local 
> --with-mpc=/home/chapoton/sage/local --with-system-zlib --disable-multilib 
> --disable-nls --enable-languages=c,c++,fortran --disable-libitm   
> > [gfortran-7.2.0] Thread model: posix 
> > [gfortran-7.2.0] gcc version 7.2.0 (GCC) 
> > [gfortran-7.2.0]  
> > [gfortran-7.2.0] Error: gcc is already installed 
> > [gfortran-7.2.0] 
> > [gfortran-7.2.0] real0m0.003s 
> > [gfortran-7.2.0] user0m0.004s 
> > [gfortran-7.2.0] sys0m0.000s 
> > [gfortran-7.2.0] 
>  
> > [gfortran-7.2.0] Error installing package gfortran-7.2.0 
> > [gfortran-7.2.0] 
>  
> > 
> > 
> > Le vendredi 9 février 2018 09:25:28 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 
> > 
> > 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 
> > 

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

[François Bissey]

Which version of ubuntu? We have seen an instance of that problem during review
but we thought it was fixed. OK, there was something nagging me but it looked 
fixed on the patchbot.

> On 9/02/2018, at 23:56, fchapot...@gmail.com wrote:
> 
> An incremental build from previous beta fails on gfortran :
> 
> [gfortran-7.2.0] Found local metadata for gfortran-7.2.0
> [gfortran-7.2.0] Using cached file 
> /home/chapoton/sage/upstream/gcc-7.2.0.tar.xz
> [gfortran-7.2.0] gfortran-7.2.0
> [gfortran-7.2.0] 
> [gfortran-7.2.0] Setting up build directory for gfortran-7.2.0
> [gfortran-7.2.0] Finished extraction
> [gfortran-7.2.0] No patch files found in ../patches
> [gfortran-7.2.0] 
> [gfortran-7.2.0] Host system:
> [gfortran-7.2.0] Linux pc-chapoton 4.13.0-32-generic #35-Ubuntu SMP Thu Jan 
> 25 09:13:46 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
> [gfortran-7.2.0] 
> [gfortran-7.2.0] C compiler: gcc
> [gfortran-7.2.0] C compiler version:
> [gfortran-7.2.0] Using built-in specs.
> [gfortran-7.2.0] COLLECT_GCC=gcc
> [gfortran-7.2.0] 
> COLLECT_LTO_WRAPPER=/home/chapoton/sage/local/libexec/gcc/x86_64-pc-linux-gnu/7.2.0/lto-wrapper
> [gfortran-7.2.0] Target: x86_64-pc-linux-gnu
> [gfortran-7.2.0] Configured with: ../src/configure 
> --prefix=/home/chapoton/sage/local 
> --with-local-prefix=/home/chapoton/sage/local 
> --with-gmp=/home/chapoton/sage/local --with-mpfr=/home/chapoton/sage/local 
> --with-mpc=/home/chapoton/sage/local --with-system-zlib --disable-multilib 
> --disable-nls --enable-languages=c,c++,fortran --disable-libitm  
> [gfortran-7.2.0] Thread model: posix
> [gfortran-7.2.0] gcc version 7.2.0 (GCC) 
> [gfortran-7.2.0] 
> [gfortran-7.2.0] Error: gcc is already installed
> [gfortran-7.2.0] 
> [gfortran-7.2.0] real 0m0.003s
> [gfortran-7.2.0] user 0m0.004s
> [gfortran-7.2.0] sys  0m0.000s
> [gfortran-7.2.0] 
> 
> [gfortran-7.2.0] Error installing package gfortran-7.2.0
> [gfortran-7.2.0] 
> 
> 
> 
> Le vendredi 9 février 2018 09:25:28 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
> 
> 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