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

2018-02-15 Thread Justin C. Walker

> On Feb 14, 2018, at 16:10 , François Bissey  wrote:
> 
> 
> 
>> On 15/02/2018, at 12:21, 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.
>> 
>> With François’s help, I rebuilt Sage with #24721 added, and the result built 
>> w/o problems (Quad-core Core i7, macOS 10.11.6).  All tests (‘ptestlong’) 
>> passed!
>> 
> 
> Great! Can you positively review #24721, please?

I would have, but Jeroen beat me to it :-}

Justin

--
Justin C. Walker, Curmudgeon at Large
Institute for the Absorption of Federal Funds
---
I want to die, peacefully in my sleep, like my grandfather;
not screaming in terror, like his passengers.




-- 
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 François Bissey


> On 15/02/2018, at 12:21, 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.
> 
> With François’s help, I rebuilt Sage with #24721 added, and the result built 
> w/o problems (Quad-core Core i7, macOS 10.11.6).  All tests (‘ptestlong’) 
> passed!
> 

Great! Can you positively review #24721, please?
This means that we can support building as far back as
xcode 7 which I think is some achievement.
On the other hand it looks like the recommended minimal
version of clang on linux is 4.0.

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

2018-02-14 Thread Justin C. Walker

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

With François’s help, I rebuilt Sage with #24721 added, and the result built 
w/o problems (Quad-core Core i7, macOS 10.11.6).  All tests (‘ptestlong’) 
passed!

Justin

--
Justin C. Walker, Curmudgeon at Large
Institute for the Absorption of Federal Funds
--
Democracy is two wolves and a lamb
   voting on what to have for lunch.
Liberty is a well-armed lamb contesting
   the vote.



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

2018-02-12 Thread François Bissey


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


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

2018-02-12 Thread Justin C. Walker

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

Justin

--
Justin C. Walker, Curmudgeon-At-Large
Institute for the Absorption of Federal Funds

Men are from Earth.
Women are from Earth.
   Deal with it.




-- 
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-12 Thread François Bissey
Can you test the branch at https://trac.sagemath.org/ticket/24721
and see if that helps with this particular machine.

François

> On 10/02/2018, at 19:40, Justin C. Walker  wrote:
> 
> 
>> On Feb 9, 2018, at 19:32 , François Bissey  wrote:
>> 
>> We didn’t test clang 3.7 which is what your machine is using at OS X 10.11.
>> But I recognised the error as one I got in the same place when I tried a 
>> build
>> with icc on linux. Yes that’s a fun bit I haven’t mentioned yet.
>> You can technically try any compiler that pretends to be gcc - but only 
>> clang 3.8
>> forward have been tested and I haven’t put in place bits for dealing with 
>> icc’s fun
>> issues (over optimisation from icc kills pari).
>> sqlite wants to use some builtins that are in gcc but identifies the 
>> compiler supporting
>> the builtins by a series of pragma. Always risky and a bit porous in this 
>> case.
> 
> Thanks for this.  I have
> 
> Apple LLVM version 7.0.2 (clang-700.1.81)
> Target: x86_64-apple-darwin15.6.0
> Thread model: posix
> 
> Is there a fairly straight-forward way to get Apple’s clang at what you're 
> calling 3.8?  
> 
> Justin
> 
> --
> Justin C. Walker, Curmudgeon-At-Large
> Institute for the Enhancement of the Director's Income
> 
> When LuteFisk is outlawed,
> Only outlaws will have LuteFisk
> 
> 
> 
> 
> -- 
> 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] Sage 8.2.beta5 released

2018-02-10 Thread François Bissey


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


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

2018-02-10 Thread François Bissey


> 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

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

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

2018-02-09 Thread François Bissey


> On 10/02/2018, at 19:40, Justin C. Walker  wrote:
> 
> Thanks for this.  I have
> 
> Apple LLVM version 7.0.2 (clang-700.1.81)
> Target: x86_64-apple-darwin15.6.0
> Thread model: posix
> 
> Is there a fairly straight-forward way to get Apple’s clang at what you're 
> calling 3.8?  

Can you install a newer xcode? Say xcode 8?

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

2018-02-09 Thread Justin C. Walker

> On Feb 9, 2018, at 19:32 , François Bissey  wrote:
> 
> We didn’t test clang 3.7 which is what your machine is using at OS X 10.11.
> But I recognised the error as one I got in the same place when I tried a build
> with icc on linux. Yes that’s a fun bit I haven’t mentioned yet.
> You can technically try any compiler that pretends to be gcc - but only clang 
> 3.8
> forward have been tested and I haven’t put in place bits for dealing with 
> icc’s fun
> issues (over optimisation from icc kills pari).
> sqlite wants to use some builtins that are in gcc but identifies the compiler 
> supporting
> the builtins by a series of pragma. Always risky and a bit porous in this 
> case.

Thanks for this.  I have

Apple LLVM version 7.0.2 (clang-700.1.81)
Target: x86_64-apple-darwin15.6.0
Thread model: posix

Is there a fairly straight-forward way to get Apple’s clang at what you're 
calling 3.8?  

Justin

--
Justin C. Walker, Curmudgeon-At-Large
Institute for the Enhancement of the Director's Income

When LuteFisk is outlawed,
Only outlaws will have LuteFisk




-- 
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 François Bissey


> On 10/02/2018, at 18:06, kcrisman  wrote:
> 
> On Friday, February 9, 2018 at 10:32:49 PM UTC-5, François Bissey wrote:
> We didn’t test clang 3.7 which is what your machine is using at OS X 10.11.
> 
> Would that be the same as this one?  I also have 10.11.
> 
> $ clang --version
> 
> Apple LLVM version 7.3.0 (clang-703.0.31)
> 
> Target: x86_64-apple-darwin15.6.0
> 
> Thread model: posix
> 
> InstalledDir: 
> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin
> 

I think so.
 
I know the problem with sqlite, there’s the band aid fix and
then there’s the proper fix which may require a bit of work.

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

2018-02-09 Thread kcrisman


On Friday, February 9, 2018 at 10:32:49 PM UTC-5, François Bissey wrote:
>
> We didn’t test clang 3.7 which is what your machine is using at OS X 
> 10.11. 


Would that be the same as this one?  I also have 10.11.

$ clang --version

Apple LLVM version 7.3.0 (clang-703.0.31)

Target: x86_64-apple-darwin15.6.0

Thread model: posix

InstalledDir: 
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin
 

-- 
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 François Bissey
We didn’t test clang 3.7 which is what your machine is using at OS X 10.11.
But I recognised the error as one I got in the same place when I tried a build
with icc on linux. Yes that’s a fun bit I haven’t mentioned yet.
You can technically try any compiler that pretends to be gcc - but only clang 
3.8
forward have been tested and I haven’t put in place bits for dealing with icc’s 
fun
issues (over optimisation from icc kills pari).
sqlite wants to use some builtins that are in gcc but identifies the compiler 
supporting
the builtins by a series of pragma. Always risky and a bit porous in this case.

François

> 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.
> 
> Justin
> 
> -- 
> 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.
> 
> 
> --
> Justin C. Walker
> Director
> Institute for the Enhancement of the Director's Income
> --
> Fame is fleeting, but obscurity
>   just drags on and on.  F&E
> 
> 
> 
> -- 
> 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 Justin C. Walker

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

Justin

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


sqlite-autoconf-317.p0.log
Description: Binary data


--
Justin C. Walker
Director
Institute for the Enhancement of the Director's Income
--
Fame is fleeting, but obscurity
   just drags on and on.  F&E



-- 
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
This is now https://trac.sagemath.org/ticket/24696

On Fri, Feb 9, 2018 at 3:35 PM Ralf Stephan  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

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

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

2018-02-09 Thread François Bissey


> On 9/02/2018, at 23:03, Ralf Stephan  wrote:
> 
> So how to use clang on Linux?

CC=clang CXX=clang++ make

Adjust to the peculiarity of your install in terms of PATH and compiler
names.

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] 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 subscribed to the Google Groups
> "sage-release" 

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

2018-02-09 Thread François Bissey
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 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://g