Volker Braun wrote:
If you want to go that route you probably want to include glibc
(contains standard math library) as well.
While a viable possibility,
there are two obvious arguments against it:
On Feb 22, 11:27 am, "Dr. David Kirkby" <david.kir...@onetel.net>
wrote:
* Always have the libraries.
Instead, check on first startup that all required packages are
installed and print an error message instead ('Please "yum install
libgfortran"').
I assume one would need root to do that, but perhaps not.
In any case, we already include the fortran library. The question is whether to
extend that to C and C++ too.
* Always have the exact same versions Sage was built with.
Downside: if your distribution comes out with a bugfix you don't
automatically profit from it.
True, though the Sage developers tend to build the binaries with late gcc
versions. In which case bug fixes in the libraries are more likely to be
included in the Sage binary than they are on the users system unless that user
has kept more up to date with gcc than the Sage developers.
Problems are more likely to occur if the user has an older buggy gcc, but the
Sage binary was built and tested using a newer gcc.
Also, if your distribution keeps
breaking the C++ ABI then maybe its time to switch.
Well, it was annoying that simply updating gcc to 4.4.3 from a slightly earlier
release caused problems. But including the libraries should avoid that.
At least with the libraries included, the user gets to use Sage with libraries
where Sage has been tested.
I know Mathematica on Solaris ships with libraries that are included on Solaris.
I assume Wolfram Research feel happier knowing that Mathematica runs with
libraries which it was tested on, rather than what the end user may have.
Dave
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
