> > Apart from moving to the latest upstream I think the singular spkg
> > is due for a spring clean. It build an enormous amount of targets
> > in a way that looks like a very careful choreography and apart
> > from libsingular and the singular binary there is no indication
> > sage uses any of th
> On 06/ 7/10 10:22 AM, François Bissey wrote:
> >>> Thoughts?
> >>
> >> I am personally all for updating to the beta version of ATLAS.
> >
> > We are currently using 3.9.23 in sage-on-gentoo without any
> > issues. The only reason we don'
> > Thoughts?
>
> I am personally all for updating to the beta version of ATLAS.
>
We are currently using 3.9.23 in sage-on-gentoo without any
issues. The only reason we don't use 3.9.24 is that the person
who usually does the revbump is "away" atm.
Francois
--
To post to this group, send an e
> I'm sure Singular has a process to fix the problems you mention.
> All you have to do is send a 'diff -Naur' patch that improves the build.
>
> You got hundreds of megabytes of code for free and you're complaining
> because the install script isn't written the way you advocate?
>
> Advocacy is
> I've tested on multiple Solaris systems, both with and without 'flex' in
> the path - see trac ticket for further details.
>
> The more I look at the Singular package in Sage, the more I realise it is
> a complete mess. There are 5 copies of install-sh for example. Sage's
> spkg-install has op
> On 06/ 6/10 10:53 AM, François Bissey wrote:
> >>> You could also try
> >>>
> >>> sage -ba
> >>>
> >>> which will rebuild from scratch all Cython code.
> >>
> >> OK I will give it a go.
> >
> > You could also try
> >
> >
> >sage -ba
> >
> >
> > which will rebuild from scratch all Cython code.
>
> OK I will give it a go.
No improvement. I am considering this upgrade officially failed
on my machine.
Francois
--
To post to this group, send an email to sage-devel@googlegroups.c
> You could also try
>
>sage -ba
>
> which will rebuild from scratch all Cython code.
OK I will give it a go.
> If you have an SMP machine, do
>export MAKE="make -j10"
> , where 10 is the number of cores, first. For example, on
> sage.math.washington.edu, I
> do "make -j24" and can bui
> It couldn't hurt to force a rebuild of pynac (or failing that Python).
>
>sage -f pynac-0.2.0.p3
>
>
> Fortunately, whatever happened isn't going to happen to *everybody*.
> I tested upgrading from 4.4.2 to 4.4.3 on our development server, and
> it worked fine.
No luck with that. I even tr
./sage
--
| Sage Version 4.4.3, Release Date: 2010-06-04 |
| Type notebook() for the GUI, and license() for information.|
--
--
> Just one thought:
>
> problems may arise with libraries which are used by both the R binary
> and certain other binaries from Sage. E.g. "iconv" comes to my mind.
> Probably one has to invest a greater-than-normal amount of care
> (w.r.t. environment variable settings and such), to ensure that R
> It appears that building R with gcc on OpenSolaris may be impossible. I
> can't get it to build, and the R manual
>
> http://cran.r-project.org/doc/manuals/R-admin.html#Solaris
>
> makes it clear nobody else has. It does however build (according to the R
> manual at least), with Sun Studio.
>
> On 05/31/10 08:36 AM, François Bissey wrote:
> >> I think you've found a bug in the makefile.
> >>
> >> We have
> >>
> >> LINBOX depends on ATLAS
> >>
> >> ATLAS depends on LAPACK and PYTHON
> >>
> I think you've found a bug in the makefile.
>
> We have
>
>LINBOX depends on ATLAS
>
>ATLAS depends on LAPACK and PYTHON
>
>LAPACK depends on FORTRAN
>
>
> It is just a lucky coincidence that the Sage build has actually worked.
> We need to add BLAS as a dependency of LAPACK, e.
> Trying to build Sage 4.3.2 on Solaris 10 (SPARC), as a 64-bit build (my
> first semi-serious attempt at 64-bit SPARC build), I get a failure:
>
> checking for C interface to BLAS... not found
> checking for others BLAS... not found
>
>
> *
> On Wed, May 26, 2010 at 3:30 AM, François Bissey
>
> wrote:
> >> On 25 May 2010 20:58, Robert Bradshaw
wrote:
> >> > On May 25, 2010, at 12:35 PM, kcrisman wrote:
> >> >> SPKG.txt version
> >> >>
> >> >> === r-2.1
> On 25 May 2010 20:58, Robert Bradshaw wrote:
> > On May 25, 2010, at 12:35 PM, kcrisman wrote:
> >> SPKG.txt version
> >>
> >> === r-2.10.1.p0 (David Kirkby, February 16th 2010) ===
>
>
>
> >> Are you really suggesting that the commit message should be this
> >> long? Maybe they should be!
> On May 25, 11:14 am, François Bissey wrote:
> Thats no more correct on gentoo - I have written a set of sed commands
> which fixes this behaviour:
>
> http://github.com/cschwan/sage-on-gentoo/blob/master/sci-mathematics/sympow
> /sympow-1.018.ebuild
>
> (see lines 27 t
> When on builds 'sympow', a directory $SAGE_LOCAL/lib/sympow is made, and
> the file 'sympow' executable copied there:
>
> drkir...@hawk:~/sage-4.4.2$ ./local/lib/sympow/sympow
> sympow 1.018 RELEASE (c) Mark Watkins --- see README and COPYING for
> details
>
>
> It seems a strange decision t
> I've tried to create a 64-bit version of Sage on OpenSolaris, but some
> files are building as 32-bit. Does anyone know what package(s) these are
> part of?
>
> local/bin/class.x:
> local/bin/cws.x:
> local/bin/dikcube:
> local/bin/nef.x:
> local/bin/poly.x:
> local/bin/QuadraticSieve:
> local/b
Hi,
> ANNOUNCEMENT
>
>Sage is now operative on another platform.*
>
That's cool, which distro?
> ( Not-able-to-compile-packages so far include Altas and R )
>
Available for alpha in gentoo so it has to be doable.
Francois
--
To post to this group, send an email t
Hi Carl,
I will comment a bit
> versions
> on net in sage-4.4.2.rc0
>
> python 2.6.5 2.6.4.p7
That will cause trouble, I have made a post about that earlier this week.
> boost 1.421.34.1
a truncated version is shipped for polybori, I know
system 1.41 wor
Hi all,
While I was working on a failing test in set.py in sage-on-gentoo
(and actually sage-on-mandriva) I noticed two strange things
while tracing "Primes()
> /home/francois/Work/sandbox/install/sage-4.4.1/local/lib/python2.6/site-
packages/sage/sets/set.py(319)__cmp__()
318 if not
We had a long standing problem in both Gentoo and Mandriva
with the following test
sage -t -force_lib "devel/sage/sage/combinat/iet/strata.py"
which is failing for us using the system python shipped with our
distributions.
As it turns out it is because the python shipped in our system includes
the
Hi,
While sorting dependencies for sage on gentoo we discovered that
zope-testbrowser is included in sagenb but we cannot find it being
used or called anywhere in sage (not just the notebook).
Are we missing something or should it be removed.
Francois
--
To post to this group, send an email to
> This has nothing to do with version 4.3.3, it also happened with 4.3.5.
> The problem turns out to be that Arch Linux has now upgraded openssl
> from 0.9.8 to 1.0.0. A long and painful solution is to rebuild Sage.
> The shorter and painless one is to only rebuild the python spkg in
> Sage:
>
>
> > -eclib,
>
> It barely uses Sage; it's just used a tiny bit for factoring, I think.
>
I meant that eclib uses and links against pari.
> > -genus2reduction (I guess sage is technically upstream there,
>
> I'm upstream for that; I doubt the modifications will be difficult.
>
same here.
> >
> On Sun, Mar 28, 2010 at 3:13 AM, William Stein wrote:
> > We should definitely move to PARI 2.4. We haven't only because it is
> > indeed a monumental task. Perhaps I'll do the move, since I wrote
> > most of the Sage wrapper of PARI anyways, and surely porting is much
> > less work than writi
> If somebody gets PyGSL to work, that would be very good (it would be
> great to have an optional spkg!). Please note one issue though, which
> is that SWIG wrappers (PyGSL is a swig wrapper) have a significant
> performance penalty.
Just for kicks how do you benchmarks the performance in questi
> No, I'm barely getting started. I hardly know my way around Gentoo, I
> had no interest in it until I discovered Gentoo prefix. (I need to
> distribute software on clusters, and I certainly don't have root
> access to those! -- and I'm really glad that the others who are on the
> cluster don't ha
> I just stumbled over "Gentoo prefix" -- have any of you tried it out?
>
> In short, it allows a Gentoo "Linux" system in a subdirectory, on Linux,
> Mac, Windows/SUA, Solaris. Gentoo is thus awfully similar to the Sage
> spkg system:
>
> - Installs Unix software in a common prefix location.
>
> 2010/3/23 François Bissey :
> > Hi,
>
> 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
> >
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 "$@"
--
> 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
> 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,
>
> 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
>
> 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
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
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, 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
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 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:
> 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 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 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 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 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 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 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
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 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
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
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 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
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 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 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 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, 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 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
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, 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
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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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, 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 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
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 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
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 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
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 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
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 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
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 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 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
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
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
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
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 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 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
701 - 800 of 813 matches
Mail list logo
