Re: [sage-devel] State of sage built with clang/clang++ on OS X - update

On 2017-02-26 08:27, Isuru Fernando wrote: Anybody know why some python extensions with C++ as the language are compiled with -std=c99? I'm using sage-7.5.1 Fix at https://trac.sagemath.org/ticket/22554 -- You received this message because you are subscribed to the Google Groups "sage-devel"

Re: [sage-devel] State of sage built with clang/clang++ on OS X - update

On 2017-02-26 10:57, Ralf Stephan wrote: The travis build failed. Usually git maintainers expect the PR submitter to check and fix all such failures. I know, but that's not the issue. They didn't say "yes we like your patch but you need to fix it". They said "why not do Y or Z instead" and I

Re: [sage-devel] State of sage built with clang/clang++ on OS X - update

The travis build failed. Usually git maintainers expect the PR submitter to check and fix all such failures. On Sun, Feb 26, 2017 at 10:38 AM Jeroen Demeyer wrote: > On 2017-02-26 08:39, Francois Bissey wrote: > > That’s because python doesn’t do c++ compilation properly

Re: [sage-devel] State of sage built with clang/clang++ on OS X - update

On 2017-02-26 08:39, Francois Bissey wrote: That’s because python doesn’t do c++ compilation properly out of the box. That's true but that has nothing to do with Sage using -std=c99 for C++ extensions. I know how to fix this but it needs https://github.com/cython/cython/pull/466 which

Re: [sage-devel] State of sage built with clang/clang++ on OS X - update

On Sunday, February 26, 2017 at 7:27:45 AM UTC, Isuru Fernando wrote: > > Anybody know why some python extensions with C++ as the language are > compiled with -std=c99? I'm using sage-7.5.1 > > Log is below > > https://travis-ci.org/isuruf/staged-recipes/builds/205439821#L6669 > wow, I didn't

Re: [sage-devel] State of sage built with clang/clang++ on OS X - update

Oh I see, so you will go with clang all the way because that’s the default. I guess you know the score at https://trac.sagemath.org/ticket/12426 it compiles but doctests are failing left and right. But I haven’t had time to touch the thing in 3 months. Francois > On 26/02/2017, at 20:49, Isuru

Re: [sage-devel] State of sage built with clang/clang++ on OS X - update

Thanks. This is using conda's python, so will have to patch that as well. Regards, Isuru Fernando On Sun, Feb 26, 2017 at 1:09 PM, Francois Bissey < francois.bis...@canterbury.ac.nz> wrote: > That’s because python doesn’t do c++ compilation properly out of the box. > That’s

Re: [sage-devel] State of sage built with clang/clang++ on OS X - update

That’s because python doesn’t do c++ compilation properly out of the box. That’s https://bugs.python.org/issue1222585 look it up. I will probably patch sage’s python in the near future - when I have time. François > On 26/02/2017, at 20:27, Isuru Fernando wrote: > > Anybody

Re: [sage-devel] State of sage built with clang/clang++ on OS X - update

Anybody know why some python extensions with C++ as the language are compiled with -std=c99? I'm using sage-7.5.1 Log is below https://travis-ci.org/isuruf/staged-recipes/builds/205439821#L6669 Regards, Isuru Fernando On Tue, Oct 4, 2016 at 1:14 PM, Francois Bissey <

Re: [sage-devel] State of sage built with clang/clang++ on OS X - update

> On 4/10/2016, at 20:39, Ralf Stephan wrote: > > Ah that would be a wrong libffi-devel version on OpenSuSE, shouldn't > this be tested by Sage configure? > That would explain. Note that I only tested the odd package on linux and most of what I have done has been on OS X.

Re: [sage-devel] State of sage built with clang/clang++ on OS X - update

Ah that would be a wrong libffi-devel version on OpenSuSE, shouldn't this be tested by Sage configure? Now I get this: [libgap-4.8.3] /usr/lib64/gcc/x86_64-suse-linux/4.8/../../../../x86_64-suse-linu x/bin/ld: .libs/libgap_la-ariths.o: relocation R_X86_64_32S against `libGAP_ZERO Op' can not be

Re: [sage-devel] State of sage built with clang/clang++ on OS X - update

I cannot find mention of ecl problems: [ecl-16.1.2.p2] /home/ralf/sage/local/var/tmp/sage/build/ecl-16.1.2.p2/src/src/c/ffi.d:148:44: error: use of undeclared identifier 'FFI_SYSV' [ecl-16.1.2.p2] {((cl_object)(cl_symbols+(1604))), FFI_SYSV}, [ecl-16.1.2.p2]

Re: [sage-devel] State of sage built with clang/clang++ on OS X - update

You need https://trac.sagemath.org/ticket/12473 for ratpoints. coming in the next beta. François > On 4/10/2016, at 19:07, Ralf Stephan wrote: > > On Sunday, October 2, 2016 at 10:33:38 PM UTC+2, François wrote: > this is the status after about two weeks > > ratpoints

Re: [sage-devel] State of sage built with clang/clang++ on OS X - update

On Monday, October 3, 2016 at 4:04:20 PM UTC+2, Dima Pasechnik wrote: > > > > On Monday, October 3, 2016 at 11:48:22 AM UTC+1, François wrote: >> >> I haven’t tried SAGE_INSTALL_GCC=no on linux or using clang >> for a full build on linux. Just one packages here and there. >> >> And yes you

Re: [sage-devel] State of sage built with clang/clang++ on OS X - update

On Monday, October 3, 2016 at 11:48:22 AM UTC+1, François wrote: > > I haven’t tried SAGE_INSTALL_GCC=no on linux or using clang > for a full build on linux. Just one packages here and there. > > And yes you cannot build gfortran without gcc a t this time. > this is a limitation of Sage's gcc

Re: [sage-devel] State of sage built with clang/clang++ on OS X - update

I haven’t tried SAGE_INSTALL_GCC=no on linux or using clang for a full build on linux. Just one packages here and there. And yes you cannot build gfortran without gcc a t this time. François > On 3/10/2016, at 22:48, Dima Pasechnik wrote: > > And how about Linux with

Re: [sage-devel] State of sage built with clang/clang++ on OS X - update

On Monday, October 3, 2016 at 8:56:27 AM UTC, François wrote: > > In the current state of sage starting from scratch with clang/clang++ > via > CC=clang CXX=clang++ make > will trigger the building of sage’s gcc (which is OK on OS X since > you still need gfortran). > The problem is that

Re: [sage-devel] State of sage built with clang/clang++ on OS X - update

In the current state of sage starting from scratch with clang/clang++ via CC=clang CXX=clang++ make will trigger the building of sage’s gcc (which is OK on OS X since you still need gfortran). The problem is that once you build sage’s gcc, there is a clause in src/bin/sage-env to use sage’s

Re: [sage-devel] State of sage built with clang/clang++ on OS X - update

What exactly should be set to start the Sage build using clang rather than gcc? On Monday, October 3, 2016 at 6:32:45 AM UTC, François wrote: > > > > On 3/10/2016, at 09:33, François Bissey > wrote: > > > >> linbox > > > > No news from upstream at > >

Re: [sage-devel] State of sage built with clang/clang++ on OS X - update

> On 3/10/2016, at 09:33, François Bissey > wrote: > >> linbox > > No news from upstream at > https://github.com/linbox-team/linbox/issues/39 > contributions welome. Well as it turns out the problem is only in the interface with fplll which we are going to

Re: [sage-devel] State of sage built with clang/clang++ on OS X

Thank you both. I'm installing it now. Best, Travis On Sunday, September 18, 2016 at 2:33:39 AM UTC-5, tdumont wrote: > > Le 17/09/2016 à 22:15, Francois Bissey a écrit : > > I don’t know about debian based distro specifically but installing clang > > shouldn’t remove gcc, they are orthogonal

Re: [sage-devel] State of sage built with clang/clang++ on OS X

Le 17/09/2016 à 22:15, Francois Bissey a écrit : > I don’t know about debian based distro specifically but installing clang > shouldn’t remove gcc, they are orthogonal to each other. > I confirm what François says: You can install clang and the gcc programs togeteher on Debian and Debian like

Re: [sage-devel] State of sage built with clang/clang++ on OS X

I don’t know about debian based distro specifically but installing clang shouldn’t remove gcc, they are orthogonal to each other. When you try building a specific package try CC=clang CXX=clang++ ./sage -f symmetrica for example. Yes there is a possibility of your sage install breaking after

Re: [sage-devel] State of sage built with clang/clang++ on OS X

On Saturday, September 17, 2016 at 2:48:40 AM UTC-5, François wrote: > > Reanimating https://trac.sagemath.org/ticket/12426 > There is a ticket for symmetrica, if you still want to do it, I’d rather > you > fix the code with a patch than with a compilation flags as is suggested in > #12439.

Re: [sage-devel] State of sage built with clang/clang++ on OS X

Reanimating https://trac.sagemath.org/ticket/12426 There is a ticket for symmetrica, if you still want to do it, I’d rather you fix the code with a patch than with a compilation flags as is suggested in #12439. François > On 17/09/2016, at 15:53, Francois Bissey

Re: [sage-devel] State of sage built with clang/clang++ on OS X

In theory you just need clang. François > On 17/09/2016, at 03:18, Travis Scrimshaw wrote: > > I could look into the Symmetrica code next week for things like you > mentioned, but I don't have access to an OS X machine to test. > > Best, > Travis > > > -- > You

Re: [sage-devel] State of sage built with clang/clang++ on OS X

I could look into the Symmetrica code next week for things like you mentioned, but I don't have access to an OS X machine to test. Best, Travis -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving

Re: [sage-devel] State of sage built with clang/clang++ on OS X

> On 16/09/2016, at 19:43, Jeroen Demeyer wrote: > > On 2016-09-15 23:21, Francois Bissey wrote: >> lcalc: is no surprise. It uses a number of obsolete features, not sure >> how long gcc itself will build it. > > This is a bit off-topic, but for lcalc we should also at

Re: [sage-devel] State of sage built with clang/clang++ on OS X

On 2016-09-15 23:21, Francois Bissey wrote: lcalc: is no surprise. It uses a number of obsolete features, not sure how long gcc itself will build it. This is a bit off-topic, but for lcalc we should also at some investigate whether we really need the package. It could very well be that all