The current script for building a binary does not copy over either libgcc_s or libstdc++ runtime libraries. Yet Sage will be linked against them. I suspect you can get away with this on Linux, as those libraries will be present in a directory searched at runtime.
You can't get away without copying these on Solaris, as in general they will not be present. (The file COPYING.RUNTIME in the gcc sources permits one to do this. They are exempted from the normal restrictions that would stop us using code from a GPL3 version of gcc). However, I do worry even on Linux and OS X if it is safe to avoid copying these libraries. Let's assume someone had an oldish version of Linux, and and oldish gcc. We build Sage with the latest gcc. There is no guarantee the library on their system will be compatible. I think there is always a risk building on the latest versions of operating systems and hoping code runs on older ones. That's the reason I set up an old Sun workstation with the first release of Solaris 10. 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
