Re: [sage-devel] sage 8.0 build failure for openblas

See https://trac.sagemath.org/ticket/23272 > On 24/07/2017, at 20:20, João Palhoto Matos wrote: > > ++ > sage-8.0/logs/pkgs/openblas-0.2.19.p0.log > ++ > > Found local metadata for openblas-0.2.19.p0 > Using cached file

Re: [sage-devel] Sage build failure with MPFR

What do you have in /home/josh/sage/local/var/tmp/sage/build/mpfr-3.1.5.p0/src/src/.libs/ ? The log is not especially enlightening, I must say. François > On 24/07/2017, at 06:15, Joshua Wall wrote: > > Hello all. I'm currently attempting to build from the git source

Re: [sage-devel] Cython 0.26 released

Copying sage-packaging. This is great news! Now some more details about that pickling support. People working on distro may very well want to ship cython with that support enabled. Is it dangerous or do you disable it as a security to make absolutely sure it doesn’t have an impact on sage?

Re: [sage-devel] Error installing package linbox-1.4.2

Hum “internal compiler error” on compiling liblinbox-sage.o. Something broke your sage installed gcc. One thing that I don’t remember seeing anywhere before and that I find suspicious “-fabi-version=6” in CFLAGS. Is this something you somehow added or you have no ideas what I am talking about?

Re: [sage-devel] Unable to compile 8.0.rc2 on mac

No 8.0.beta4 had an older version of mpir. François > On 18/07/2017, at 18:47, Andrew <andrew.mat...@gmail.com> wrote: > > I managed to compile 8.0.beta4 without issues but perhaps xcode has changed > in the interim... > > Andrew > > On Tuesday, 18 July 2017 14

Re: [sage-devel] Unable to compile 8.0.rc2 on mac

You appear to have some relatively recent hardware. I am suspecting that the combination OS X + skylake cpu hasn’t had a lot of testing. Not sure how to get around that really. François > On 18/07/2017, at 16:32, Andrew wrote: > > I'm trying to compile the current

Re: [sage-devel] Re: Error rebuilding Sage (ncurses)

The OS X file system only fake case sensitivity, so “Sage” and “sage” are actually the same folder. Now it is very suspicious. It fails because permission is denied on > /Users/J_Honrubia/Sage/sage/local/var/lib/sage/installed Yet you are t143730 and you are building from /Users/t143730/sage/ so

Re: [sage-devel] Re: sage built with icc/icpc/gfortran

On 28/06/17 10:51, François Bissey wrote: with the peculiar being: ** File "src/sage/rings/real_double.pyx", line 2296, in sage.rings.real_double.RealDoubleElement.arccos Failed example: i.arccos() ==

[sage-devel] Re: sage built with icc/icpc/gfortran

On Tuesday, June 27, 2017 at 10:14:30 PM UTC+12, François Bissey wrote: > > Well after realising that in its current state #12426/#22646/#23046 > would at least let me try to build sage with the intel compiler, > I just did go ahead and got myself an open source license.

[sage-devel] sage built with icc/icpc/gfortran

Well after realising that in its current state #12426/#22646/#23046 would at least let me try to build sage with the intel compiler, I just did go ahead and got myself an open source license. On top of the above tickets I had to patch _2_ packages to finish the build. * sqlite [icc has all the

[sage-devel] clang on OS X and beyond

Hi all, I think it is time to say where we are again in regards to supporting building sage with clang on OS X rather than gcc. There are two tickets currently needed to achieve it: https://trac.sagemath.org/ticket/22646 which aim is to make your compiler configuration to “stick” if it isn’t

Re: [sage-devel] use alternative compiler

It looks like you are a perfect candidate for testing https://trac.sagemath.org/ticket/22646 which was requested for just such things. And that I am abusing in my quest to support clang. François > On 21/06/2017, at 20:20, Vincent Delecroix <20100.delecr...@gmail.com> wrote: > > Dear all, > >

Re: [sage-devel] Re: python3 : help needed

Originally only sent to Frederic instead of the group Forwarded Message Subject: Re: [sage-devel] Re: python3 : help needed Date: Mon, 29 May 2017 10:00:25 +1200 From: François Bissey <francois.bis...@canterbury.ac.nz> To: Frédéric Chapoton <fchapot...@gmail.com>

[sage-devel] splitting BRiAl

Hi all, Sorry for the cross posting but I believe it is relevant to sage-devel as a statement of intent. As you may remember BRiAl is a slightly stripped down version of polybori that has been autotooled. I say stripped down because BRiAl do not built the pypolybori python dynamic library that

[sage-devel] sage.misc.package considered harmful

Hi all, This is a rare rant cross-posted to sage-packaging about one of the annoyance faced by the people packaging sage and not using sage's packaging system. The functions found in `sage.misc.package` are a result of the fact that sagemath and its development is closely linked to its own

Re: [sage-devel] Re: linker options for C code in ext/interpreters and other stuff in sagelib

The generated sage/ext/interpreters/wrapper_cdf.pxd has the following statement: cimport sage.libs.cypari2.types That would pull `-lpari`. To add `-lm` you would have to add a line #distutils: libraries = m at the top of the same .pxd file, you'll have to dig a bit inside

Re: [sage-devel] "replacement" optional packages

On 13/03/17 11:00, Justin C. Walker wrote: I'm trying to imagine surf without graphics (:-}), but perhaps that's not what you mean exactly. Thanks for clarifying. I don't know surf :) but I imagine it can output to jpeg and tiff directly. And if X is found to a basic x-window. If the gui

Re: [sage-devel] ipython-5.0.0 crash

Is this a re-located install? Francois On 10/03/17 09:30, Gere Mia wrote: ipython-5.0.0 crash in Sage 7.5.1 crashes on Linux: | ┌┐ │SageMathversion 7.5.1,ReleaseDate:2017-01-15 │ │Type"notebook()"forthe

Re: [sage-devel] build fails due to giac-1.2.2.103

On 10/03/17 09:18, Darij Grinberg wrote: > Hi, > > On Thu, Mar 9, 2017 at 2:16 PM, Isuru Fernando wrote: >> Can you also attach the ntl log? > > Here it goes: https://dl.dropboxusercontent.com/u/83265276/ntl-10.1.0.log > > Best regards, > Darij > Sorry for the echo.

Re: [sage-devel] build fails due to giac-1.2.2.103

Hum, that's definitely a signal that ntl has been compiled with -std=c++11 and eclib doesn't. Which is strange because I put code in configure to make sure it would pick up the c++11 bit myself. I probably didn't take into account a corner case. On the other hand I think eclib should just switch

Re: [sage-devel] Re: Can't run binaries

There used to be a "make install" target but it is deprecated. You should move the entire install and run ./sage --location but I never do that. Someone else may have more experience with it. Francois On 09/03/17 10:52, Gere Mia wrote: > I built mine in /tmp, now it wants me to run it in temp.

Re: [sage-devel] Re: tachyon-0.98.9.p5 build error in Linux

On 08/03/17 09:35, Gere Mia wrote: > Both of you are right. My make is really a bash script/alias for "make > -j4", so that might have messed things up. I thought I tried using a > non-"-j" make, and it didn't work, but "MAKE='make -d' ./sage -p > tachyon" built it successfully. thank you > I

Re: [sage-devel] Re: Our SSL serial drama-cum-cliffhanger

It depend what compilers are exposed. Last time someone filled a bug, gfortran from brew was interfering with the gfortran sage installs. https://trac.sagemath.org/ticket/22112 Francois On 25/01/17 11:46, Konstantin Kliakhandler wrote: Ah, I misunderstood the question. AFAICT homebrew does not

Re: [sage-devel] Re: Our current git doesn't build anymore with recent (>=1.1) openSSL

On 15/12/16 11:36, Dima Pasechnik wrote: except that this makes it unclear how one can ship a fully functioning (with SSL) Sage binary on OSX that does not depend on system git being available (and the latter I presume needs Xcode). I'll admit that I cannot check that right now. In fact I am

Re: [sage-devel] Re: Our current git doesn't build anymore with recent (>=1.1) openSSL

On 15/12/16 11:17, Dima Pasechnik wrote: IIRC, Sage's current git also does not build on OSX properly, and this was also related to SSL. I'd open a ticket to upgrade to the current stable git (2.10.2, I guess). Definitely. You are encouraged to open a ticket. And yes some OS X problem are

Re: [sage-devel] Python 2.7.13rc1 breaks UnknownClass

On 07/12/16 12:20, than...@debian.org wrote: Hi sage-devel, we're almost ready to upload Sage to Debian (in fact we basically have to upload it this week to make sure it's included in the next Debian release). However, on Sunday python 2.7.13rc1 was uploaded to Debian and now we are facing a

Re: [sage-devel] sage 7.4 does not build on Ubuntu 16.10

Yes, building gcc 4.9.3 with gcc 6.2.0 is not exactly supported. On 01/11/16 09:09, William Stein wrote: I tried to install sage-7.4 on a clean new Ubuntu:16.10 docker container (on 64-bit x68 intel). It fails trying to building GCC with ... gcc-4.9.3.p1] (cd

Re: [sage-devel] Trac error on push

On 01/11/16 07:31, jhonrubia6 wrote: Thank you. Is there any place where is documented how to get the new ssh key for the host whenever this happens again? I don't know that's published anywhere at the present time. Anyone? Francois -- You received this message because you are subscribed to

Re: [sage-devel] NTL 1v0.1.0

On 19/10/16 23:57, Victor Shoup wrote: Sure. Will do. For people not on libsingular-devel, Hannes' answer: == The problem is a fast/convinient conversion between long integers in factory of type CanonicalForm (which is in principle a mpz_t number) and long integers in NTL of type ZZ

Re: [sage-devel] NTL 1v0.1.0

On 15/10/16 03:28, Victor Shoup wrote: After much foot dragging, and with the help and encouragement of folks here at sage-devel, I've finally got around to making (nearly) all of the packaging/build features that were requested. The big ones are locally generated libtool and $(MAKE). I did not

Re: [sage-devel] Re: trouble compiling latest sage development version

On 12/10/16 09:26, Dima Pasechnik wrote: On Tuesday, October 11, 2016 at 7:47:47 PM UTC, John H Palmieri wrote: Right, Sage's Python is broken. Try deleting sage/local/bin/python and python2, and also sage/local/lib/python2.7 and sage/local/lib/libpython2.7.dylib. Then the build

Re: [sage-devel] NTL v10

On 11/10/16 01:58, Victor Shoup wrote: Another issue. I'm not sure if $(MAKE) is specific to gnu make or if it is universal. In general, I don't want to assume gnu. But I can certainly make this the default, and provide a config variable to override. I'll have another go at this when you use

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

Hi all, this is the status after about two weeks On 16/09/16 09:21, Francois Bissey wrote: I couldn’t build sagelib, I didn’t manage to get there. Here are the packages that fail to build with clang in sage 7.4.beta4 on OS X: ratpoints #12473 for this has positive review lcalc #12437 for

Re: [sage-devel] libc mandatory for Sage dmg on OSX 10.11.6?

On 15/09/16 08:23, Dima Pasechnik wrote: FYI, R is normally built on OSX using clang (from XCode) and gfortran. Given the huge (compared to Sage) user base of R, it looks as if it should work quite well. And we can just steal their binary gfortran package... I have regular thoughts about that

Re: [sage-devel] Re: Upgrade to Singular 4.x

On 08/09/16 11:21, mmarco wrote: Both results are equivalent in this case (the given charts actually differ only by a change of coordinates), but I am not sure why the difference has appeared. I will try to have a look at it in the following days (although don't have much time available lately).

Re: [sage-devel] Re: giacpy depends (silently) on SageObject

On 02/09/16 01:51, Michael Orlitzky wrote: On 09/01/2016 09:46 AM, leif wrote: Exactly. (See also my other reply.) It would be dumb and totally annoying if all such packages would get rebuilt upon *any* change to the Sage library, and just as bad as having to "manually" figure out /which/

Re: [sage-devel] Re: Issues when building Sage with --with-mp=gmp

7.0.3 over there: https://gforge.inria.fr/frs/?group_id=135 fixes stuff for gcc 5+ and gmp 6.1.0 and ppc64. Will try on recent OS X to check if that bit is fixed. I was thinking of another QA problem. Francois On 03/08/16 12:48, leif wrote: Francois Bissey wrote:

Re: [sage-devel] Re: Issues when building Sage with --with-mp=gmp

On 01/08/16 09:49, leif wrote: because this is an old bug (happened in the past with MPIR as well) which never got fixed nor really tracked down, just the now failing doctest (unpickling all a second time) got added in #5838; I've also commented there [1]. -leif [1]

Re: [sage-devel] Re: make giac/giacpy a standard package

On 06/07/16 04:16, leif wrote: If so, should we change also the spkg name? (may be we should not, so > people will really upgrade?) That's not a problem, since Sage releases and specific spkg versions are now stupidly tied together (even for optional spkgs). Upgrade has to be handled

Re: [sage-devel] Re: make giac/giacpy a standard package

On 04/07/16 22:41, parisse wrote: I'm fixing the build for --disable-gui And I am guessing you didn't mean that it would be in 1.2.2-65 either. I am still getting /bin/sh ../libtool --tag=CXX --mode=compile x86_64-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I.. -DIN_GIAC -I. -I.. -I. -I..

Re: [sage-devel] Re: make giac/giacpy a standard package

On 04/07/16 22:41, parisse wrote: I will also add a --disable-ao flag in configure.in (ao is used for the playsnd command) Do you have an ETA for that? I noticed it has not landed in 1.2.2-65. Francois -- You received this message because you are subscribed to the Google Groups "sage-devel"

Re: [sage-devel] Re: make giac/giacpy a standard package

So I have been inspecting giac, as any discussion of making something a standard package as an impact for sage-on-gentoo. We have an old version in the science overlay so I am working on upgrading it. 1) current 1.2.2-63 and a few earlier versions need the gui, compiling with "--disable-gui" is

Re: [sage-devel] Re: consistency in trac e-mails

On 06/27/16 09:50, Dima Pasechnik wrote: could you check sage-trac@googlegroups for these "missing" emails? Didn't think about that. I don't remember seeing the tickets in the digest. But they are there. Francois -- You received this message because you are subscribed to the Google Groups

Re: [sage-devel] Re: consistency in trac e-mails

On 06/27/16 03:34, leif wrote: Vincent Delecroix wrote: Hello, Thanks for the hard work for the infrastructure transition! As a consequence of the new trac infrastructure, my e-mail reader (thunderbird) is not able to group the e-mails by thread. Works for me. There was some temporary

Re: [sage-devel] Using the systemwide R (or upgrading it internally)

On 06/07/16 07:28, Jack Dyson wrote: Hi everyone, I'd appreciate some help on this: I need to use mixtools on R in sage for the ER stuff they have. It turns out you need R 3.2.4 or better. I thought of (a) upgrading the sage internal R or (b) using the system wide one that I have on sagemath

Re: [sage-devel] Re: SageMath 7.3.beta3 build failure on OS X versions 10.8 and 10.9.

Yes that's new. Although it is disabled for fat binaries, but there is no easy way to disable it from outside spkg-install. Francois On 06/07/16 08:08, Nathan Dunfield wrote: I have successfully compiled Sage 7.2, which has an earlier version of NTL, from source on both 10.8 and

Re: [sage-devel] NTL new.h patch - singular-related - details?

On 05/27/16 02:55, Jean-Pierre Flori wrote: I tried to do archeology once for this one and found nothing conclusive... I think inspection of #852 is fairly conclusive although the final word on the matter would rest on singular devs as they are the one the patch was stolen from.

Re: [sage-devel] error building ipython for sage-7.2

On 05/19/16 02:28, John Cremona wrote: Two similar machines running ubuntu 14.04 and gcc-4.8.4. On one 7.2 built fine but on the other ipython ran into difficulties. This was an upgrade from 7.1 in the git sense, i.e. I have the source repo, which was probably at 7.0 and first did git pull

Re: [sage-devel] sage-notebook css problem (sage-7.2.beta6)

11:26, Vincent Delecroix wrote: Perhaps I have to rebuild the doc (something I do not do for each release)... On 03/05/16 18:24, François Bissey wrote: Here: http://git.sagemath.org/sage.git/diff/src/doc/common/themes/sage/theme.conf?id=8a1385636d6f256415b07462114ccecc46efedf8 On 05/04/16

Re: [sage-devel] sage-notebook css problem (sage-7.2.beta6)

Here: http://git.sagemath.org/sage.git/diff/src/doc/common/themes/sage/theme.conf?id=8a1385636d6f256415b07462114ccecc46efedf8 On 05/04/16 11:20, François Bissey wrote: Indeed I do not have this file. I think in the latest changes for the sphinx upgrade something as been changed from "de

Re: [sage-devel] sage-notebook css problem (sage-7.2.beta6)

Indeed I do not have this file. I think in the latest changes for the sphinx upgrade something as been changed from "default" to "classic" (and there is a classic.css). I wonder if we need a matching change in sagenb. Francois On 05/04/16 11:13, Vincent Delecroix wrote: Hello, Trying to

Re: [sage-devel] Re: openssl gone?

... no checking for iconv in -lc... yes so ssl is there but curl is not detected, still want config.log. Francois On 04/06/16 10:32, François Bissey wrote: Hum... configure: CHECKS for libraries checking for SHA1_Init in -lcrypto... no checking for SHA1_Init in -lssl... no checking for curl_global_init

Re: [sage-devel] Re: openssl gone?

Hum... configure: CHECKS for libraries checking for SHA1_Init in -lcrypto... no checking for SHA1_Init in -lssl... no checking for curl_global_init in -lcurl... no checking for XML_ParserCreate in -lexpat... no checking for iconv in -lc... yes Would you be able to get the config.log file

Re: [sage-devel] Re: openssl gone?

On 04/06/16 09:54, Simon King wrote: Am Dienstag, 5. April 2016 23:47:20 UTC+2 schrieb François: On 04/06/16 09:27, Simon King wrote: > Interesting. There really is no such thing as git-remote-http. Why could > that be? Do you have curl+curl-dev installed? That what it

Re: [sage-devel] Re: openssl gone?

On 04/06/16 09:27, Simon King wrote: Interesting. There really is no such thing as git-remote-http. Why could that be? Do you have curl+curl-dev installed? That what it uses for those. Francois -- You received this message because you are subscribed to the Google Groups "sage-devel" group.

Re: [sage-devel] Re: openssl gone?

What do you have in local/libexec/git-core? You should have something like /usr/libexec/git-core/git-remote /usr/libexec/git-core/git-remote-ext /usr/libexec/git-core/git-remote-fd /usr/libexec/git-core/git-remote-ftp /usr/libexec/git-core/git-remote-ftps /usr/libexec/git-core/git-remote-http

Re: [sage-devel] NTL 9.7.0

On 03/15/16 09:28, François Bissey wrote: On 03/15/16 05:23, Victor Shoup wrote: That is a bummer with the C++11 issues. The way I see it, C++11 is the future, and pretty much all C++ must eventually deal with it. Looking over the build issues with singular -- if the make files don't respect

Re: [sage-devel] NTL 9.7.0

On 03/15/16 05:23, Victor Shoup wrote: That is a bummer with the C++11 issues. The way I see it, C++11 is the future, and pretty much all C++ must eventually deal with it. Looking over the build issues with singular -- if the make files don't respect CFLAGS or CXXFLAGS, then maybe one can make

Re: [sage-devel] Sage "and" Anaconda

On 03/11/16 07:54, Jeroen Demeyer wrote: On 2016-03-10 18:19, William Stein wrote: On Thu, Mar 10, 2016 at 9:10 AM, Jeroen Demeyer wrote: After a quick look at conda, one major difference is that its focus is really on binary packages. It might not be easy to support

Re: [sage-devel] The package system: redundancy

On 03/08/16 00:22, Erik Bray wrote: Ah, I see what you're saying here. Though in that case I would think one wouldn't want to rely on SAGE_LOCAL at all. Instead it might be nice if each spkg came with a Python-based way to check for it (those checks can and should be cached as well). Indeed,

Re: [sage-devel] Re: An Arabic translation of "A Tour of Sage"

On 03/03/16 09:39, Ahmed Alharbi wrote: As soon as I receive my login credentials, I will open a ticket. Should be in your inbox by now. If not check your spam folder. I can re-send you the details from another email adress if necessary. Francois -- You received this message because you

Re: [sage-devel] any buildbot using gcc-5.3 out there?

On 01/28/16 11:18, François Bissey wrote: I am asking because I got a report about a singular/ntl interaction with gcc-5.3.0 in sage-on-gentoo. Basically ntl 9.6.2 switches on c++11 support and then g++ refuse to compile bits of singular calling ntl without c++11 being enabled. Of course

[sage-devel] any buildbot using gcc-5.3 out there?

I am asking because I got a report about a singular/ntl interaction with gcc-5.3.0 in sage-on-gentoo. Basically ntl 9.6.2 switches on c++11 support and then g++ refuse to compile bits of singular calling ntl without c++11 being enabled. Of course singular's configure scripts [yes there are

Re: [sage-devel] vote for making nauty a standard package (Re: About license of nauty and poset generator)

On 01/21/16 12:29, Dima Pasechnik wrote: On Wednesday, 20 January 2016 22:44:06 UTC, Jeroen Demeyer wrote: On 2016-01-20 22:12, Dima Pasechnik wrote: > Here is a ticket with the new nauty release, and a proposal to make it a > standard package. >

Re: [sage-devel] Build failure OS X sage-6.10.beta7 numpy-1.10

options are passed to gfortran to link the shared object. This is probably due to some confusion in the numpy build system which doesn't expect ATLAS on OS X. Francois On 12/10/15 15:12, François Bissey wrote: > Have you set SAGE_ATLAS_ARCH? Doing so is definit

Re: [sage-devel] Build failure OS X sage-6.10.beta7 numpy-1.10

:12, François Bissey wrote: Have you set SAGE_ATLAS_ARCH? Doing so is definitely not supported. We prefer using the accelerate framework on OS X. I have just upgraded xcode so I will give it a try. Francois On 12/10/15 13:20, Ian Hoffman wrote: This is my first post (and first time building Sage

Re: [sage-devel] Build failure OS X sage-6.10.beta7 numpy-1.10

Have you set SAGE_ATLAS_ARCH? Doing so is definitely not supported. We prefer using the accelerate framework on OS X. I have just upgraded xcode so I will give it a try. Francois On 12/10/15 13:20, Ian Hoffman wrote: This is my first post (and first time building Sage). I'm using El Capitan

Re: [sage-devel] Request for advice : upgrading a standard package requires a new package

The policy that I, Volker and Jeroen (I think) have followed in those case - and it happened a lot while upgrading the various versions of ipython - is to include the new package as standard in the upgrade ticket. It is the only non-crazy option. Either you leave a stall package because you

Re: [sage-devel] Re: Mathematics without apologies - Portrait of a Problematical Vocation

On 11/26/15 17:17, Ralf Stephan wrote: On Wednesday, November 25, 2015 at 7:18:51 PM UTC+1, rjf wrote: courses that serve to crush the dreams of superfluous applicants to particularly desirable professions (as freshman calculus used to be a formal requirement to enter medical school in the

Re: [sage-devel] numpy/matplotlib/scipy upgrade needs review

Volker just released 6.10.beta5. I think if any one else is interested in getting these in sage 6.10, this would be a good time to review the tickets. After that we may be looking at (6.10)++ whatever that is. Francois On 11/11/15 13:32, François Bissey wrote: Hi all, I have put three tickets

Re: [sage-devel] Re: What in Sage uses Boost ? And who maintains it ?

There is a ticket with a more recent boost: http://trac.sagemath.org/ticket/17966 It basically works on linux. It needs love on OS X because boost's build system has no idea there is such a thing as "install_name" on OS X and it proves being one of the fatal problems on "El Capitan". Other

[sage-devel] numpy/matplotlib/scipy upgrade needs review

Hi all, I have put three tickets that have to be merged together as needing review. * numpy 1.10.1 http://trac.sagemath.org/ticket/17642 * matplotlib 1.5.0 http://trac.sagemath.org/ticket/19556 * scipy 0.16.1 http://trac.sagemath.org/ticket/17643 numpy has three patches added. The first two are

Re: [sage-devel] upgrading to matplotlib

On 11/10/15 08:09, John H Palmieri wrote: With the current version, running grep -R 'width and height must' local/lib/python/site-packages/matplotlib* finds a match. What happens if you do the same with the new version? Blank: fbissey@QCD-nzi3 ~/sandbox/git-fork/sage $ grep -R 'width and

Re: [sage-devel] upgrading to matplotlib

On 11/10/15 08:12, John H Palmieri wrote: Oh, and in original tarball, it's in 'src/_backend_agg.cpp'. I'll have to add that between 1.4.3 and 1.5.0 'src/_backend_agg.cpp' has completely been rewritten... fbissey@QCD-nzi3 ~ $ wc

Re: [sage-devel] upgrading to matplotlib

On 11/10/15 11:33, John H Palmieri wrote: The only possibly relevant thing I could find was in src/_image.h: $ grep 32768 _image.h if (rows >= 32768 || cols >= 32768) { throw "rows and cols must both be less than 32768"; But something like this was also in the old version... I

[sage-devel] upgrading to matplotlib

Hi all, I am working on a series of ticket to upgrade numpy/matplotlib/scipy. http://trac.sagemath.org/ticket/17642 (numpy) http://trac.sagemath.org/ticket/19556 (matplotlib) http://trac.sagemath.org/ticket/17643 (scipy) The upgrade is developed as being a simultaneous one. I have a pending

[sage-devel] Re: [SPAM: 9.600] Fwd: [sage-trac] #10295: Upgrading pexpect

. Francois On 10/16/15 14:03, Bill Page wrote: Is anyone interested in helping to resolve this old pexpect issue? Dealing with the Sage development process and in particular Sage package management is a bit beyond me but François Bissey created a branch almost 5 months ago with an updated version

Re: [sage-devel] Re: [SPAM: 9.600] Fwd: [sage-trac] #10295: Upgrading pexpect

On 10/16/15 14:29, kcrisman wrote: Though I guess one would have to upgrade sagenb and pexpect simultaneously? You got that part right, it will have to be simultaneous. Bill can you update the branch for a version with the commit in question included? Is it even released yet? Francois -- You

Re: [sage-devel] Re: el capitan statement

On 10/08/15 09:42, Dima Pasechnik wrote: On Wednesday, 7 October 2015 11:57:22 UTC-7, Harald Schilly wrote: I've added a very short red banner to the download osx/intel download page for all mirrors. It does link back here to sage-devel, to the last two threads I found about that.

Re: [sage-devel] Re: el capitan statement

On 10/08/15 09:56, François Bissey wrote: On 10/08/15 09:42, Dima Pasechnik wrote: On Wednesday, 7 October 2015 11:57:22 UTC-7, Harald Schilly wrote: I've added a very short red banner to the download osx/intel download page for all mirrors. It does link back here to sage-devel

[sage-devel] el capitan

Hi all OS X sufferers, I have been working about adding rpath from gcc but it turns out it may not be the problem or possibly not the only problem. For some time there has been a known issue that a number of components shipped with sage do not set up proper "install_name" for their libraries.

Re: [sage-devel] updating sage-env LD_LIBRARY_PATH from spkg-install

One design that comes to mind is how distro populate their default environment. Instead of shoving everything in a single file there is a top file that source the content of a directory. Depending on your distro it could be in /etc/env.d or /etc/profile.d. So individual package can put particular

Re: [sage-devel] Does python pass its test suite on any platform?

On 09/04/15 09:17, John H Palmieri wrote: > At least a while ago, Sage's Python failed its test suite on most (all?) > platforms. Is this still true? If you're willing, please try > >sage -f -c python2 > > and report the results. > > For me, it fails on OS X. > Fails here: 358 tests OK. 4

Re: [sage-devel] Does python pass its test suite on any platform?

After opening the firewall only test_gdb was left failing. Francois -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To

Re: [sage-devel] Re: Short fr, de, pt, ru translation

On 08/28/15 08:53, Jeroen Demeyer wrote: On 2015-08-27 22:33, Thierry Dumont wrote: I prefer Pour utiliser GAP ou Pour utiliser les fonctionnalités de GAP. Pour des fonctionnalités GAP is not correct french. Pour utiliser *certains* fonctionnalités de GAP... (is this the correct

Re: [sage-devel] Re: Short fr, de, pt, ru translation

On 08/28/15 09:08, Jeroen Demeyer wrote: On 2015-08-27 22:59, François Bissey wrote: I also don't like paquetage unless I am told it is standard for French localization. In the same document, there is Le logiciel gnuplot est disponible comme paquet optionnel. Apparently both paquet

Re: [sage-devel] packaging vision (pip etc)

On 08/17/15 09:46, Ondřej Čertík wrote: And my next question is what should we do currently to make it easy for Sage users to install SymEngine. Should we continue using the spkg to install the C++ dependencies (cmake, the C++ libsymengine.so library) and then use pip to install the Python

Re: [sage-devel] SymEngine 0.1.0 released

Hi Ondřej, Old fashioned .spkg are not in fashion anymore. In fact we very much want to kill them as much as possible. The new process separate the tarball from upstream (pristine as much as possible) and the building script. In a similar fashion gentoo ebuild or hashtag recipe. Look at

Re: [sage-devel] Re: Issues with GCC 5.x

That's a very simple patch that one of us could apply. But in all honesty I don't think it makes sense to add sub-releases like this. The only thing that will fix the problems with gcc 5.x in the long run is newer version of gf2x and ncurses that can deal with it out of the box. In that context

[sage-devel] elliptic_curves-0.8 seems to have unwanted hidden files

HI, I was just preparing the new elliptic_curves for sage-on-gentoo when I noticed that the archive contains some extra files that I very much doubt where intended to be shipped: drwxr-xr-x 4 fbissey fbissey 4.0K Mar 19 2012 . drwx-- 3 fbissey portage 4.0K Jul 23 11:44 .. -rwxr-xr-x 1

Re: [sage-devel] elliptic_curves-0.8 seems to have unwanted hidden files

On 07/23/15 11:52, François Bissey wrote: HI, I was just preparing the new elliptic_curves for sage-on-gentoo when I noticed that the archive contains some extra files that I very much doubt where intended to be shipped: drwxr-xr-x 4 fbissey fbissey 4.0K Mar 19 2012 . drwx-- 3 fbissey

[sage-devel] problem posting on trac

Hi all, I seem to have trouble posting on trac. I successfully updated a ticket 3 hours ago and since then I have tried posting on http://trac.sagemath.org/ticket/17618 but it just times out on me after I hit the submit change button. I can see tickets just fine. Francois -- You received this

[sage-devel] The future of polybori

Hi all, over at http://trac.sagemath.org/ticket/18437 we have some heated debate about what to do about polybori. Let me summarize the situation. * at this moment polybori is dead upstream * polybori is the last package using scons * is one of the last packages, if not the last, not ready for

Re: [sage-devel] The future of polybori

On 06/11/15 14:39, William Stein wrote: I could easily imagine Andrew and Francois and Jereon are all dutifully imagining that I know all kinds of Polybori enthusiasts and there are good reasons that Polybori really must be really well supported in Sage. However, it turns out this at least

Re: [sage-devel] Sage 6.7 fails to build on Solaris SPARC - libfplll-4.0.4 problem with isfinite

On 05/25/15 09:59, Dr. David Kirkby (Kirkby Microwave Ltd) wrote: On 24 May 2015 22:04, François Bissey francois.bis...@canterbury.ac.nz mailto:francois.bis...@canterbury.ac.nz wrote: Painful memory from when I tried to compile octave with IBM xlC compiler. Before c++11 it is a gnu

Re: [sage-devel] Sage 6.7 fails to build on Solaris SPARC - libfplll-4.0.4 problem with isfinite

Painful memory from when I tried to compile octave with IBM xlC compiler. Before c++11 it is a gnu extension. You probably got a compiler that decided to be stricter. Francois On 05/25/15 09:00, Dr. David Kirkby (Kirkby Microwave Ltd) wrote: Sage used to build fine on 32-bit SPARC, and pass

Re: [sage-devel] Sage 6.7 fails to build on Solaris SPARC - libfplll-4.0.4 problem with isfinite

On 05/25/15 10:03, François Bissey wrote: What version of gcc are you using? I see 4.5.0. I don't really know if it is because it is too old to be automatic or if it is a configuration thing on Sun. I would have expected the default to be `-std=gnu++98` and to allow that. Francois -- You

Re: [sage-devel] Problems building documentation

There has been hosting problems for the sage infrastructure lately. Soon to be resolved. In the meantime I build and host html documentation tarballs for sage-on-gentoo at: http://www.lmona.de/files/sage/sage-6.7-doc-html.tar.xz and http://www.lmona.de/files/sage/sage-6.6-doc-html.tar.gz There

Re: [sage-devel] Problems installing package qepcad

Experimental package not updated since 2008. The first error message you get is clearly because someone assumed you would run on linux - or more probably doesn't that uname -i is not posix and not supported outside of linux. And it goes down from there The spkg probably need an update as

Re: [sage-devel] Re: Sage 6.7 build failure

On 05/19/15 09:56, Antonio Rojas wrote: I'm using cython git master. Nice, I should try that. Right now I am only patching to sage level. Francois -- You received this message because you are subscribed to the Google Groups sage-devel group. To unsubscribe from this group and stop receiving

<    1   2   3   4   5   6   7   8   >