Debian Version?
frosty
working on making a Debian version that would work without having to
compile all the parts. i.e. use the needed files, apps & libraries
that are already packaged in Debian.
Secondly I have downloaded the binary for Linux and have it installed
& runnimng: I want to actually compile Sage for my server which is an
AMD 6 core based server with 8Gb of ram running Debian stable. I
tried , but it errored out, error 1 showing a segmentation fault. I am
including the message snippet part of the install log to this mail.
Maybe it will help.
Thanks!
Frosty
> sage/geometry/triangulation/base.cpp: In function ‘int __pyx_pf_4sage_8geometry_13triangulation_4base_31ConnectedTriangulationsIterator_1__init__(PyObject*, PyObject*, PyObject*)’:
> sage/geometry/triangulation/base.cpp:3928: internal compiler error: Segmentation fault
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See <file:///usr/share/doc/gcc-4.4/README.Bugs> for instructions.
> error: command 'gcc' failed with exit status 1
> sage: There was an error installing modified sage library code.
>
> ERROR installing Sage
>
> real 5m48.351s
> user 31m10.961s
> sys 0m55.679s
> sage: An error occurred while installing sage-4.7.2
> Please email sage-devel http://groups.google.com/group/sage-devel
> explaining the problem and send the relevant part of
> of /home/frosty/sage-4.7.2/install.log. Describe your computer, operating system, etc.
> If you want to try to fix the problem yourself, *don't* just cd to
> /home/frosty/sage-4.7.2/spkg/build/sage-4.7.2 and type 'make check' or whatever is appropriate.
> Instead, the following commands setup all environment variables
> correctly and load a subshell for you to debug the error:
> (cd '/home/frosty/sage-4.7.2/spkg/build/sage-4.7.2' && '/home/frosty/sage-4.7.2/sage' -sh)
> When you are done debugging, you can type "exit" to leave the
> subshell.
> make[1]: *** [installed/sage-4.7.2] Error 1
> make[1]: Leaving directory `/home/frosty/sage-4.7.2/spkg'
>
> real 243m1.297s
> user 263m5.531s
> sys 13m38.279s
> Error building Sage.
>
>
David Roe
There was an effort a couple years ago to get Sage as a debian
package. It was successful for a while, but then the maintainer left
academia and founded a startup, so it hasn't been upgraded.
I think one of the problems is getting a fairly current version of
Sage into Debian. It takes quite a while before a new package can
make it past experimental. But I'm not really familiar with all of
the current issues related to the Debian port. The wiki page
http://wiki.sagemath.org/devel/DebianSage looks fairly old; there's
also a google group debian-sage that hasn't had any traffic in a year.
David
> --
> To post to this group, send an email to sage-...@googlegroups.com
> To unsubscribe from this group, send an email to sage-devel+...@googlegroups.com
> For more options, visit this group at http://groups.google.com/group/sage-devel
> URL: http://www.sagemath.org
>
William Stein
> I have just discovered Sage & want to know if there are any folks here
> working on making a Debian version that would work without having to
> compile all the parts. i.e. use the needed files, apps & libraries
> that are already packaged in Debian.
There are people in the Mandriva and Gentoo communities that have got
Sage (mostly) into their distros. Nobody in Debian is taking on the
challenge, as it turns out. All it would take would be somebody who
really wanted to do it (and had the drive).
> Secondly I have downloaded the binary for Linux and have it installed
> & runnimng: I want to actually compile Sage for my server which is an
> AMD 6 core based server with 8Gb of ram running Debian stable. I
> tried , but it errored out, error 1 showing a segmentation fault. I am
> including the message snippet part of the install log to this mail.
> Maybe it will help.
Either you have some really old version of GCC that is broken, your
compilers are misinstalled, or your hardware is somehow broken.
"internal compiler error" means the compiler crashed, which can be
caused by faulty hardware or a buggy compiler.
William
> --
> To post to this group, send an email to sage-...@googlegroups.com
> To unsubscribe from this group, send an email to sage-devel+...@googlegroups.com
> For more options, visit this group at http://groups.google.com/group/sage-devel
> URL: http://www.sagemath.org
>
--
William Stein
Professor of Mathematics
University of Washington
http://wstein.org
Jeroen Demeyer
> Secondly I have downloaded the binary for Linux and have it installed
> & runnimng: I want to actually compile Sage for my server which is an
> AMD 6 core based server with 8Gb of ram running Debian stable. I
> tried , but it errored out, error 1 showing a segmentation fault. I am
> including the message snippet part of the install log to this mail.
the error again)?
Francois Bissey
> On Fri, Nov 11, 2011 at 12:59 PM, frosty <jfoste...@gmail.com> wrote:
> > I have just discovered Sage & want to know if there are any folks here
> > working on making a Debian version that would work without having to
> > compile all the parts. i.e. use the needed files, apps & libraries
> > that are already packaged in Debian.
>
> There are people in the Mandriva and Gentoo communities that have got
> Sage (mostly) into their distros. Nobody in Debian is taking on the
> challenge, as it turns out. All it would take would be somebody who
> really wanted to do it (and had the drive).
>
> > Secondly I have downloaded the binary for Linux and have it installed
> > & runnimng: I want to actually compile Sage for my server which is an
> > AMD 6 core based server with 8Gb of ram running Debian stable. I
> > tried , but it errored out, error 1 showing a segmentation fault. I am
> > including the message snippet part of the install log to this mail.
> > Maybe it will help.
>
> Either you have some really old version of GCC that is broken, your
> compilers are misinstalled, or your hardware is somehow broken.
> "internal compiler error" means the compiler crashed, which can be
> caused by faulty hardware or a buggy compiler.
>
I think that when tabbott tried to get it into debian he tried to take the
highway in some way. In debian you can add repo.
Someone with debian knowledge could take the work we have done in
Gentoo and Mandriva and create a sage repo with binaries for debian.
All that is needed is someone with the drive, I, Christopher and Paulo
(Mandriva) would certainly help someone taking that route.
Francois
This email may be confidential and subject to legal privilege, it may not reflect the views of the University of Canterbury, and it is not guaranteed to be virus free. If you are not an intended recipient, please notify the sender immediately and erase all copies of the message and any attachments. Please refer to http://www.canterbury.ac.nz/emaildisclaimer for more information.
RegB
both in virtual machines (VirtualBox under Windows Vista with 1 Gig
memory)
and physical. The most recent change to the Atlas package that allows
me to
specify architecture=fast has speeded things up considerably, i.e. it
takes
a reasonable set of tuning parameters and builds relatively quickly
instead
of striving for perfection and taking 3, 4 or 5 times as long and then
failing
due to what it perceives as an unstable system (unpredictable
performance).
As a newbie I have followed ALL the instructions in the installation
document
to the letter, so I have not had to chase down obsolete compilers,
libraries,
or anything like that.
A minor tip on the install/build manual, before you actually type
"make" DO
read on through the section on environment variables and set those,
then come
back and type "make", take a break, find other things to do for n
hours, etc.
Paulo César Pereira de Andrade
The major issue of working on integrating sage on a distro is how
to keep up with upstream versions of packages. Save for packages
where sage is upstream, I cannot, or not dare to, tell package maintainers
to freeze for several years some packages, so, I either get it to work
with sage or use some approach to have sage using the older version
it distributes.
The other major issue is when sage needs patches. You know,
getting a patch in some projects sometimes may be an impossible
mission, for the most different reasons. And then, if you attempt to
add a patch to the package as distributed by the distro and you are
not the maintainer, you may clash with that package maintainer
because the patch does not come from upstream...
But after all, I would say that like 95% of packages just works
with the system version, and can keep up to date with updates.
The major problem is getting it to work in the first time, after that,
as long as it does not rot for too long, maintenance is a lot easier.
Since start of working on sage on Mandriva I was expecting other
distros to do the same, so that sage developers would actually
use sage as shipped by their preferred distro, and would be
a win win for everybody. Gentoo is doing a great job :-)
> Francois
Paulo