On Dec 2, 11:36 am, William Stein wrote:
> On Wed, Dec 1, 2010 at 2:25 PM, David Kirkby wrote:
> >> Verifying correctness of tests is not a waste of time.
>
> > I don't know what the current coverage is, but lets say for argument
> > it needs another 1000 tests to get 100% coverage. It's better t
Indeed they are! Thanks for the tip.
On Feb 15, 6:11 am, Robert Bradshaw
wrote:
> On Sun, Feb 13, 2011 at 2:54 AM, Francois Bissey
>
> wrote:
> > Hi all,
>
> > Just want to check something that I think is weird.
> > I was looking at ticket #10764 and basically fixing the deprecated
> > warnings
On Feb 22, 4:00 am, Volker Braun wrote:
> The problem is when configure calls
>
> /export/home/drkirkby/sage-4.6.2.rc0/spkg/build/cddlib-094f.p8/src/
> missing --run automake-1.11 --gnu
>
> if automake were not installed, then "missing" would emulate it. This
> means that it would touch the Makefi
On Mar 17, 1:50 am, kcrisman wrote:
> On Mar 16, 9:15 pm, Jason Grout wrote:
>
> > On 3/16/11 3:04 PM, Peter Jeremy wrote:
>
> > > Overall, I believe the abs(actual-expected) > > the only practical way to handle doctests. The expected numeric
> > > result is still available, just not on a line b
On Apr 20, 8:26 pm, "Nicolas M. Thiery"
wrote:
> On Fri, Apr 15, 2011 at 12:40:20PM +1200, Francois Bissey wrote:
> > After a small number of patch (#11156 from Nicolas M. Thiery, and 2 in
> > #9958, one of which is from my friend Steve Trogdon) we have a clear view
> > of what needs to be fixed
On May 1, 10:01 pm, Jeroen Demeyer wrote:
> It would be useful if everybody who is running OS X 10.5 or older could
> report whether sage-4.7.rc1 builds and passes doctests. Be sure to
> mention your gcc version (output of gcc --version), OS X version and
> whether you have an Intel or PPC proces
On May 2, 10:06 am, François wrote:
> On May 1, 10:01 pm, Jeroen Demeyer wrote:> It would
> be useful if everybody who is running OS X 10.5 or older could
> > report whether sage-4.7.rc1 builds and passes doctests. Be sure to
> > mention your gcc version (output of
On May 3, 7:21 am, Francois Bissey
wrote:
> > On 2011-05-02 00:06, François wrote:
> > > it failed here but I have a somewhat older gcc:
> > Yes, I believe there are more recent gcc versions for your system, right?
>
> I will see if gcc-4.0.1 from xcode 3.1.4 fared b
On May 3, 9:48 am, François wrote:
> On May 3, 7:21 am, Francois Bissey
> wrote:> > On 2011-05-02 00:06, François wrote:
> > > > it failed here but I have a somewhat older gcc:
> > > Yes, I believe there are more recent gcc versions for your system, right?
&
On May 4, 7:58 am, Maarten Derickx
wrote:
> On May 3, 7:23 pm, Burcin Erocal wrote:
>
> > IIRC, there were messages on this list about having python as a
> > dependency already. What are the dependencies of Sage besides tar,
> > gcc and gfortran? Does Sage depend on bash?
>
> It definitly d
On May 4, 5:23 am, Burcin Erocal wrote:
> Hi,
>
> > One last thing about "sage -clone, -b, -ba, br, ..." --- from my
> > memory about several discussions, the sage community regards this as a
> > "killer feature", i.e. that there is not some "sage" and then some
> > other, different "sage-dev" pac
gf2x is a little bugger. If you are on x86_64 or a few other select
platforms (any of core2|opteron|x86_64|nocona|k10 )
it automatically add files tuned for sse2 regardless of the other
configurations checks. That will be quite messy to untangle
properly.
I may have to force sse2 on x86_64, the
OK I did some analysis on the failure of
sage -t -long -force_lib "devel/sage/sage/gsl/interpolation.pyx"
A list of point is initialized with:
v = [(i + sin(i)/2, i+cos(i^2)) for i in range(10)]
then a spline is created:
s = spline(v)
The failure is when we try this:
show(point(v) + plot(s,0,11, h
And in the other test we actually look at the chi squared distribution for
k=1:
sage: nu = 1
sage: T = RealDistribution('chisquared', nu)
sage: T.get_random_element() # random
0.103230507883
sage: T.distribution_function(0)
0.0
If I am not mistaken
If you are using Volker new ATLAS spkg can you tell me what you get from
this doctest:
sage -t -force_lib "devel/sage/sage/modular/modsym/space.py"
We found in sage-on-gentoo that this test fails with some ATLAS-3.9.xx.
Francois
--
To post to this group, send an email to sage-devel@googlegroup
For those interested Jason Grout has already filled a ticket to upgrade to
ipython-0.10.2 (trac #11460) with a comment that Fernando told him that
it would be better to skip 0.11.
There is a new spkg on that ticket that needs testing, especially on OS X
and with sage -gdb.
Francois
--
To post t
On Friday, November 22, 2013 3:47:16 PM UTC+13, William wrote:
>
> On Thu, Nov 21, 2013 at 6:40 PM, kcrisman >
> wrote:
> >
> >
> > On Thursday, November 21, 2013 3:08:44 PM UTC-5, François wrote:
> >>
> >> On Thu, 21 Nov 2013 09:54:1
Before someone jump and create a ticket this is already discussed in
#16002. In short the freetype2 skpg need
a small adjustment to remove that file if found.
Francois
On Tuesday, March 25, 2014 6:43:56 AM UTC+13, Peter Bruin wrote:
>
> Hello,
>
> After the matplotlib upgrade (#14993), typing 'm
If you do remove them don't forget to remove the associated documentation.
That is remove sage/dev but also doc/en/reference/dev and apply this little
patch too
https://github.com/cschwan/sage-on-gentoo/blob/master/sci-mathematics/sage-doc/files/sage-doc-dev.patch
François
On Sat
On Sat, 29 Dec 2007, mabshoff wrote:
> On Dec 28, 8:36 pm, Francois <[EMAIL PROTECTED]> wrote:
> > Hello Michael,
>
> Hello Francois,
>
> > I think I found my problem. A little googling actually helped with
> > this link:http://bugs.archlinux.org/task/6864
> > I did some experiments with the intel
On Sat, 29 Dec 2007, mabshoff wrote:
> Well, if we were to limit ourselves to Linux systems that might be an
> option, but with the need to support OSX and Solaris [and in the
> futute Windows] I don't see this as something viable. Portage is nice,
> but it is the wrong tool for a cross platform t
On Tue, 24 Jun 2008, William Stein wrote:
> On Mon, Jun 23, 2008 at 10:27 PM, Francois <[EMAIL PROTECTED]> wrote:
> > I just found out that I have xmaxima in my $SAGE_LOCAL/bin folder.
> > I am pretty sure no one ordered that. It seems that it will build by
> > default
> > if the configure script
On Wed, 25 Jun 2008, Michael Abshoff wrote:
>
> I am not sure if there is any harm if Maxima builds it. When woulds
> building xmaxima cause a problem?
>
No harm, I cannot imagine how I could be harmful in fact.
More like a small waste of ressources and an unintended side-effect. Just my
reactio
On Wed, 09 Jul 2008, Ondrej Certik wrote:
> The only remaining annoying thing is this one LD_LIBRARY_PATH thing.
> I'll probably put it to my .bashrc, as there doesn't seem to be any
> way around it.
>
It's probably better to make a small launcher script setting the variable
correctly. I have seen
On Thu, 10 Jul 2008, Robert Dodier wrote:
> William Stein wrote:
> > If you answer could you summarize what Maple/Mathematica do
> > (if you care), and if so why you think whatever you propose is
> > better than them.
>
> Not sure if I am the "you" in question here, but fwiw I don't know
> what Ma
On Thu, 10 Jul 2008, David Philp wrote:
> Multiple solutions are different to assumptions in Mathematica.
>
> Solve[x^2 == 1, x] returns a two unconditional solutions. (x -> 1, x-
>
> > -1 are both solutions).
>
> Integrate[x^a, {x, 1, Infinity}] returns an answer that incorporates
> assumption
On Thu, 10 Jul 2008, Dr. David Kirkby wrote:
> I've tried to build Sage 3.0.4 on my Sun Blade 2000 (Solaris 10 8/07
> s10s_u4wos_12b SPARC). It fails when building ntl, reporting:
>
> ../include/NTL/ctools.h:6:27: NTL/mach_desc.h: No such file or
> directory
>
> Looking at the sage tree, I note th
On Thu, 10 Jul 2008, François Bissey wrote:
> On Thu, 10 Jul 2008, Dr. David Kirkby wrote:
> > I've tried to build Sage 3.0.4 on my Sun Blade 2000 (Solaris 10 8/07
> > s10s_u4wos_12b SPARC). It fails when building ntl, reporting:
> >
> > ../include/NTL/ctools.h:6:2
On Thu, 10 Jul 2008, Dr. David Kirkby wrote:
> I tried to build sage 3.0.4 on my laptop (Solaris Express Community
> Edition snv_91 X86), but it fails when building pari. It looks from a
> search of the web, that the error generated:
>
> "ld: fatal: relocations remain against allocatable but non-w
Hi all,
Recently David Kirkby tried to compile sage on
solaris express and it blew up on pari. Turns out
the pari shared library is build without any PIC
flag and that caused his linker to just give up.
Turns out that the problem is in fact widespread
across a number of archs where the linker e
On Mon, 21 Jul 2008, William Stein wrote:
> On Sun, Jul 20, 2008 at 10:54 PM, Tim Abbott <[EMAIL PROTECTED]> wrote:
> > I'm getting the point in the Debianization of Sage that I'm primarily
> > working on the package for Sage itself (rather than its dependencies).
> > Below is my current draft des
On Mon, 21 Jul 2008, mabshoff wrote:
> > Packages need to be configured with --prefix=$SAGE_ROOT/local,
> > installed with DESTDIR=somewhere, and then somewhere/$SAGE_ROOT/local
> > has to be renamed to $SAGE_ROOT/spkg/graft/packagename-v.er.si-on
> > before graft (or whichever one) is called to p
On Tue, 22 Jul 2008, Timothy G Abbott wrote:
> On Mon, 21 Jul 2008, François Bissey wrote:
> > Hi,
> >
> > I am almost at the same stage myself on Gentoo. I have started uploading
> > individual packages to the science overlay and have a few under review.
> > An
On Sat, 30 Aug 2008, Jaap Spies wrote:
> Philippe Saade wrote:
> > Hi dev team,
> >
> > Some of you know that wednesday and thursday i made an official
> > presentation of Sage at the Maths' Teachers' Summer School (French
> > Educational System).
> >
> > Notebook ended up on TV (well 3 seconds) i
On Mon, 29 Sep 2008, mabshoff wrote:
> On Sep 27, 8:50 am, Tim Abbott <[EMAIL PROTECTED]> wrote:
> > On Sep 26, 3:39 pm, mabshoff <[EMAIL PROTECTED]> wrote:
>
> Hi Tim,
>
> > > For example: Take the FLINT.spkg - ever since we used the patches Tim
> > > submitted the spkg was broken twice by either
On Mon, 17 Aug 2009, John Cremona wrote:
> 2009/8/17 Dr. David Kirkby :
> > I'm trying to work out exactly how the makefiles in ntl are generated,
> > The flags to add shared library support are gcc specific. I'd like to
> > try to make them configurable, so they can work with other compilers,
> >
On Tue, 18 Aug 2009, David Kirkby wrote:
> 2009/8/17 François Bissey :
> > On Mon, 17 Aug 2009, John Cremona wrote:
> >> 2009/8/17 Dr. David Kirkby :
> >> > I'm trying to work out exactly how the makefiles in ntl are generated,
> >> > The flags to a
Hi,
I have a problem compiling polybori in sage-4.2.
I get the following:
g++ -o groebner/src/randomset.o -c -O3 -Wno-long-long -Wreturn-type -g -fPIC -
ftemplate-depth-100 -g -fPIC -O3 -Wno-long-long -Wreturn-type -g -fPIC -
DNDEBUG -DHAVE_GD -DHAVE_TR1_UNORDERED_MAP -DPACKED -DHAVE_M4RI -DHAVE_
On Sat, 31 Oct 2009 23:52:14 you wrote:
> I'm somewhat intrigued why there were so many options given to gcc when it
> was built. It's anyones guess if one of those is causing the problem.
>
> There are numerous repeated options given to the g++ command which makes
> me think the build proces
I found the problem. I had an old of version of m4ri installed on my system
(20090105) and it was picked up by polybori. This version of m4ri lacks
mzd_t which lead to the error.
By the way it looks like the sage version of polybori doesn't depend on
libm4ri which means the internal copy is use
On Sun, 01 Nov 2009 23:42:41 Martin Albrecht wrote:
> On Sunday 01 November 2009, François Bissey wrote:
> > By the way it looks like the sage version of polybori doesn't depend on
> > libm4ri
>
> Can you clarify what you mean by that? Do you mean in the Makefile?
&g
On Tue, 10 Nov 2009 02:33:49 David Kirkby wrote:
> Who created it?
>
It is quite possibly Tim Abbott from the time he
developed the debian port has everything that is
put in /usr/bin needs a man page by debian policy.
I remember he wrote basic man page for at least
one other program shipped with
On Thu, 12 Nov 2009 19:27:51 Jason Grout wrote:
> William Stein wrote:
> > Dear Jason,
> >
> > The Nauty spkg is broken with modern GCC's. You're spkg maintainer
> > for that package, so I'm letting you know:
> >
> >http://trac.sagemath.org/sage_trac/ticket/7439
> >
> > Of course, if anybody
On Tue, 17 Nov 2009 07:14:41 William Stein wrote:
> On Mon, Nov 16, 2009 at 10:11 AM, Matt Rissler wrote:
> > Yes, I've been building from source. And both 32-bit and 64-bit. I
> > haven't been running the tests, but nothing seems to be broken due to
> > being on Gentoo.
> >
> > I will admit in
On Wed, 18 Nov 2009 08:23:39 Jason Grout wrote:
> I have a fairly fresh installation of 64-bit Ubuntu 9.10, and I'm
> compiling 4.2.1. I've installed gfortran and build-essential, plus the
> other packages listed in step 1 of the README. I even set
> SAGE_FORTRAN=/usr/bin/gfortran before building
On Wed, 18 Nov 2009 10:05:55 Jason Grout wrote:
>
> I haven't modified anything:
>
> /dev/shm/sage-4.2.1/local/bin% cat sage_fortran
>
> #!/bin/sh
>
> sage_fortran.bin -fPIC $...@%
>
>
>
> Of course, sage_fortran.bin is a binary executable.
>
> Checking the SAGE_FORTRAN bit:
>
> /dev/shm/s
On Sat, 28 Nov 2009 07:14:56 roelof wrote:
> Hello,
>
> Im trying to make Sage working on a gentoo box but it fails here :
>
> Thread model: posix
> gcc version 4.3.4 (Gentoo 4.3.4 p1.0, pie-10.1.5)
>
> checking build system type... k8-unknown-
On Sat, 28 Nov 2009 06:50:37 William Stein wrote:
> On Fri, Nov 27, 2009 at 6:56 AM, Pat LeSmithe wrote:
> > Part of the outline at
> >
> > http://wiki.sagemath.org/SageTasks
> >
> > is about build logs:
> >
> >* Separate file for each spkg for parallel builds.
> >* Group by install, upgra
On Sat, 28 Nov 2009 11:56:02 William Stein wrote:
> On Fri, Nov 27, 2009 at 1:57 PM, François Bissey
>
> wrote:
> > On Sat, 28 Nov 2009 07:14:56 roelof wrote:
> >> Hello,
> >>
> >> Im trying to make Sage working on a gentoo box but it fails here :
>
On Tue, 01 Dec 2009 14:42:43 strogdon wrote:
> Now when I unpack the sage-4.2.1.spkg tarball and insert
>
> unset CFLAGS
> unset CXXFLAGS
>
> near the top of the spkg-install script, repackage the tarball and
> issue the above 'make' with custom CFLAGS; both sage and the
> documentation build an
On Wed, 02 Dec 2009 04:17:50 strogdon wrote:
> Hey Francois. I too thought that perhaps the spkg supplied flags would
> override any changes with custom flags. However the custom flags seem
> to be appended to the spkg provided ones. For example
>
> with custom CFLAGS
> building 'sage.algebras.qua
On Thu, 03 Dec 2009 08:03:44 strogdon wrote:
> So, it would appear that it is not the CFLAGS but whether CFLAGS has
> been set to something. The no-strict-aliasing is suspiciously missing.
> The documentation I have on gcc 4.3.4 indicates that optimization
> levels O2 and O3 turn on strict-aliasing
On Tue, 15 Dec 2009 06:23:30 John Cremona wrote:
> 2009/12/14 kcrisman :
> > Dear sage-devel,
> >
> > It's time to fix our R stuff. I have some suspicions on some issues,
> > so I would appreciate if people on a wide variety of machines could
> > try the following and reply to this thread.
> >
> >
On Wed, 16 Dec 2009 13:46:40 Dr. David Kirkby wrote:
> I was wondering if something could be done with version numbers of
> libraries, or perhaps all libraries are built with the name 'sage' at the
> front, so there is libsagereadline for example. But I suspect that is the
> name of the functio
On Thu, 17 Dec 2009 16:45:36 Dr. David Kirkby wrote:
> This is not simply a run-time issue, as the conflicts are causing a failure
> of Sage to build on OpenSolaris.
>
> http://trac.sagemath.org/sage_trac/ticket/7387
>
> I'm not convinced renaming the libraries would solve it - as you say, it
>
On Fri, 18 Dec 2009 09:42:40 Paulo César Pereira de Andrade wrote:
> You may want to check the sagemath package in Mandriva cooker, and
> its dependencies.
>
> Mandriva 2010.0 has a contrib sagemath 4.1.1 package that required a hack
> tough, that is LD_PRELOAD of libpolibori and libntl or it
On Fri, 18 Dec 2009 14:49:38 William Stein wrote:
> Better would be a single environment variable such as
>
>SAGE_USE_SYSTEM_LIBRARY="readline libz sqlite"
>
> with a space separated list of libraries
>
I was going to suggest something like that myself.
That would just be the one variable in
On Fri, 18 Dec 2009 20:07:26 Dr. David Kirkby wrote:
> François Bissey wrote:
> > On Fri, 18 Dec 2009 14:49:38 William Stein wrote:
> >> Better would be a single environment variable such as
> >>
> >>SAGE_USE_SYSTEM_LIBRARY="readline libz sqlite&
On Tue, 24 Feb 2009, water wrote:
> this is my log's last several lines.
>
> Configure findings:
> FFI:yes (user requested: default)
> readline: yes (user requested: yes)
> libsigsegv: yes
> ./makemake --with-dynamic-ffi --with-readline --with-libreadline-
> prefix=/home/huxpen
OK so I can reproduce the problem on my machine building sage-3.3 from
scratch. I may investigate the problem tomorrow.
Do you have any problem emerging clisp 2.46 from portage?
emerge =dev-lisp/clisp-2.46
you would have to unmask as it isn't stable (gentoo skipped it
in favor of 2.47).
Francois
OK setting aside the slightly off-topic of Gentoo ricers.
I worked out where the actual log is for building clisp from
the spkg and reproduced the various steps in the sage
environment (no playing with C(XX)FLAGS) - I use gcc-4.3.3.
First we have an interesting warning at the beginning
that may
On Thu, 26 Feb 2009, mabshoff wrote:
> On Feb 25, 3:05 am, water wrote:
> > if I need to wait sage 3.4 ?
>
> Hi,
>
> Sage 3.4 won't fix the issue since it needs to be out by friday at the
> latest and I will need to work on other things until then.
>
> I have thought about this some more and it s
On Fri, 27 Feb 2009, mabshoff wrote:
> I have a badly hacked together clisp-2.47.spkg for my Sparc Solaris
> build, but it does not have all the patches in it that we used for
> clisp 2.46. I don't want to spend any more time on this since I have
> wasted too much time on clisp instead of doing the
On Sat, 28 Feb 2009, mabshoff wrote:
> On Feb 27, 2:08 am, François Bissey wrote:
> > On Fri, 27 Feb 2009, mabshoff wrote:
> Ok, it is a little longer than I would have thought it would be. Maybe
> we you can stick something in the Sage 3.4 release tour wiki page and
> we men
On Sat, 28 Feb 2009, mabshoff wrote:
> Well, let me rephrase my point: If you
>
> touch spkg/installed/clisp-2.46.p7
>
> Sage's dependency system will assume that that clisp.spkg is
> installed, so even if the compilation failed at some point you never
> need to mess with "deps", i.e. the instru
OK latest version of gentoo notes for 3.4.
Francois
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at h
On Mon, 06 Apr 2009, Prabhu Ramachandran wrote:
> Just one minor point. I think wxPython should be an optional install,
> needed only if you want the full UI at some point. I've fixed all
> issues relating to using mlab off screen without having wxPython
> installed. If there is a problem, its a
On Tue, 29 Dec 2009 19:54:34 Dr. David Kirkby wrote:
> In the Makefile for cliquer-1.2.p3 it says:
>
> # Enable long options for cl (eg. "cl --help"), comment out to disable.
> # Requires getopt_long(3) (a GNU extension)
> LONGOPTS = -DENABLE_LONG_OPTIONS
>
>
> Is cliquer being used interactive
On Tue, 29 Dec 2009 22:31:35 Nathann Cohen wrote:
> Hello everybody !!!
>
> There is some Cython code used for Linear Programs in sage that
> require optional packages/libraries to be installed ( they can not
> become standard because of licence issues ) to compile without error.
> For the moment,
On Tue, 29 Dec 2009 22:46:12 Nathann Cohen wrote:
> The packages mentionned are GLPK and CBC.
>
Thanks for the info. Looks like cbc may be a bit a bit of
a stumbling block.
Francois
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an
On Tue, 29 Dec 2009 23:05:47 Nathann Cohen wrote:
> Why is is so troublesome for you ? Wouldn't it be easier to fix this
> Sage issue instead of dealing with CBC or GLPK as they are for the
> moment ? :-)
Fixing the sage issue would certainly be a good thing. From the point
of view of packaging sag
Hi all,
The work on porting sage to Gentoo has made good progress
but we got a bloody nose on the issue of pickle
I am referring to the following thread:
http://groups.google.com/group/sage-
devel/browse_thread/thread/583048dc7d373d6a/735ec83cf845d145
and this ticket:
http://trac.sagemath.org
On Tue, 12 Jan 2010 04:53:14 Craig Citro wrote:
> Hi Francois,
>
> > While Carl Witty mentions that python shouldn't be patched directly
> > as it would make it harder to package sage for distros, Craig Citro
> > went ahead and did just that.
> > I couldn't find a ticket or a thread describing the
On Wed, 13 Jan 2010 22:35:16 Craig Citro wrote:
> > If you work on getting this merged upstream as a bug that's a good
> > selling point for us. We can produce a patched ebuild and possibly
> > get it accepted.
> > Do you have a bug tracking number of some kind for it?
>
> I just submitted the bug
On Thu, 14 Jan 2010 22:27:53 Dr. David Kirkby wrote:
> I tried a 64-bit build of Sage on a Sun Blade 2000 SPARC workstation
> running Solaris 10. I don't know if linbox is only looking for GMP in /usr
> and /usr/local, which is semi-implied below. But for whatever reason, it
> decides it can't f
On Wed, 20 Jan 2010 16:21:55 Jonathan Bober wrote:
> The Sage README.txt contains the text:
>
> "On Linux, if you get this error message:
>
> " restore segment prot after reloc: Permission denied "
>
> the problem is probably related to SELinux."
>
> I got this error on a machine on which I
On Fri, 22 Jan 2010 19:27:56 Gonzalo Tornaria wrote:
> > If you are only going to shave off 20 MB or so from the source code, it
> > might be more hassle than it is worth. If you could cut the download time
> > by 30%, then I could see it would probably be worth the effort in doing
> > this. But I'
On Sat, 23 Jan 2010 10:45:55 Peter Jeremy wrote:
> >
> >make[4]: Entering directory
> >`/export/home/drkirkby/sage-4.2/spkg/build/singular-3-1-0-4-20090818.p1/sr
> >c/factory' WARNING: You need to rerun autoconf. I am proceeding, for
On Sun, 24 Jan 2010 16:19:21 Peter Jeremy wrote:
> On 2010-Jan-24 10:54:34 +1300, François Bissey
wrote:
> >On Sun, 24 Jan 2010 10:26:45 Aleksej Saushev wrote:
> >> FreeBSD's make isn't bmake. It is important to remember that this
> >> difference exists
Hi,
I am wondering why is pyprocessing still is in the sage tarball as I thought
the functionality had been moved in python in the 2.6.x series.
Is there a specific reason it is still built separately? Possibly overriding
the native python capabilities?
Francois
--
To post to this group, send
On Tue, 26 Jan 2010 18:15:05 William Stein wrote:
> Hi,
>
> I opened a ticket about removing this... 7 months ago:
>
>http://trac.sagemath.org/sage_trac/ticket/6503
>
> I updated the ticket to blocker, posted instructions, and changed it
> to "positive review" so that it will get merged by M
On Fri, 29 Jan 2010 07:02:15 Bill Hart wrote:
> Hi all,
>
> it is with pleasure that we (finally) officially release MPIR 1.3.0.
> It is available at our website http://www.mpir.org/
>
Well I am making a Gentoo ebuild, it is already in the sage-on-gentoo
overlay and will be in the science overla
Hi Bill,
Let me try to clarify a bit.
On Sat, 30 Jan 2010 12:18:54 Bill Hart wrote:
> All of those object files seem to come from assembly code assembled by
> yasm. I actually don't understand the bug report though. So I am not
> sure what needs fixing. I don't know of any systems that these file
On Sat, 30 Jan 2010 15:26:51 Bill Hart wrote:
> > It is a bit more subtle than that, it should work most of the time. The
> > main case where things could go south is if you have a hardened system
> > with the NX bit turned on - my guess.
> > It is a QA issue meaning that actual side effects are ha
On Sat, 30 Jan 2010 16:28:04 David Kirkby wrote:
> I will however test this out later today (within the next 12 hours) on
> the Sun Blade 2000 I own. That will at least enable us to determine if
> it is the hardening in Solaris on SPARC which is causing this. The
> fact this has been around since 1
On Fri, 12 Feb 2010 15:29:22 Dr. David Kirkby wrote:
> I've tried to build sage-4.3.2 on Solaris 10 using gcc 4.4.3 (the latest
> version). It is complaining about some code in NTL, specicially the use of
> 'if' and 'define' include/NTL/config.h.
>
> I'm not a C++ programmer. It is normal to put
On Fri, 12 Feb 2010 22:00:02 Dr. David Kirkby wrote:
> François Bissey wrote:
> > On Fri, 12 Feb 2010 15:29:22 Dr. David Kirkby wrote:
> >> I've tried to build sage-4.3.2 on Solaris 10 using gcc 4.4.3 (the latest
> >> version). It is complaining about some code in
On Tue, 16 Feb 2010 08:47:45 Georg S. Weber wrote:
> On 15 Feb., 12:38, cschwan wrote:
> > Hello,
> >
> > since this is my first post on this list I think it is a good idea to
> > briefly introduce myself: My name is Christopher Schwan, I am studying
> > physics at Uni Mainz (Germany) and I am one
On Tue, 16 Feb 2010 10:40:11 William Stein wrote:
> > sage -t "devel/sage/doc/en/tutorial/tour_numtheory.rst"
> > **
> > File "/opt/sage/devel/sage/doc/en/tutorial/tour_numtheory.rst", line 94:
> >sage: x = crt(2, 1, 3, 5); x
On Tue, 16 Feb 2010 12:41:31 William Stein wrote:
> On Mon, Feb 15, 2010 at 3:09 PM, François Bissey
>
> wrote:
> > On Tue, 16 Feb 2010 10:40:11 William Stein wrote:
> >> > sage -t "devel/sage/do
On Tue, 16 Feb 2010 12:38:59 Robert Bradshaw wrote:
> Another issue with the piecemeal approach is that upgrading a
> component could suddenly cause Sage to break. Have you given any
> thought to how you will handle this?
>
Kind of. We can have several versions of the same package in tree.
We
On Tue, 16 Feb 2010 12:41:31 William Stein wrote:
> If you link against mpir then the above discrepancy would go away.
> However, i can also tell you that the above discrepancy is harmless.
> The issue is simply that both answers are right. e.g., the line
>
> sage: x = crt(2, 1, 3, 5); x
>
> us
On Tue, 16 Feb 2010 21:23:58 Robert Bradshaw wrote:
> MPIR is supposed to be a drop in replacement for GMP and provides a
> "compatibility" mode, so we really are linking to MPIR. (It's also
> force of habit, and easier than patching all the upstream packages).
>
Well it will be easier to fix
Hi,
it seems that the author of sympow left the University of Bristol.
Consequently his homepage there has been removed along with
sympow sources. Does anyone knows where it is all gone?
Couldn't find anything with a lazy Google search. The sage components
web page will need updating for it as wel
On Tue, 23 Feb 2010 09:44:34 Bill Hart wrote:
> This is a yasm issue (yasm is a prereq for MPIR and is included in the
> tarball).
>
> I haven't ever seen yasm not build on an Opteron before.
>
> Can you download MPIR 1.3.1 from http://www.mpir.org/ and verify it
> builds on your machine outside
> I downloaded mpir-1.3.1 outside of sage and started the compile. Yasm
> seems to have built just fine. But it failed in a different place.
> When creating libmpir.so, GCC returns the error,
>
> mpn/.libs/add_n.o: file not recognized: File format not recognized
>
> The more-or-less full log is
> Hi,
>
> Some are known problems due to using different versions of certain
> packages, example:
>
> -%<-
> File "/usr/share/sage/devel/doc/en/numerical_sage/cvxopt.rst", line 57:
> sage: print(A)
> Expected:
> SIZE: (5,5)
> (0, 0) 2.e+00
> (1, 0) 3.e+00
>
> In the past, Tim Abbott asked to be cc'ed on threads like these. I
> think his primary difficulty is keeping up with all the dependencies
> of sage, especially when sage releases with a patched version of a
> dependency that has not made it upstream yet. Debian package
> maintainers are unlikely
> Hi,
>
> I would like to work on two tickets: #5731 (Update NTL to 5.5.2
> release) and #2114 (get gf2x into Sage!).
>
> As already reported in the discussion for #2114, the easiest way to
> add gf2x is just to install it first, and then add an option to the ./
> configure script of NTL. If hav
Hi,
I am trying to find the root of some test failure with the maxima interface
on the port of sage of Gentoo and I have just read the content of
maxima-noreadline:
#!/bin/sh
SAGE_CLISP_DISABLE_READLINE_HACK="yes"; export
SAGE_CLISP_DISABLE_READLINE_HACK
exec "$SAGE_LOCAL"/bin/maxima "$@"
--
1 - 100 of 852 matches
Mail list logo
