The binaries are all built with SAGE_INSTALL_GCC=yes to be as self-contained as possible. AFAIK a default Ubuntu install doesn't include a fortran compiler, for example.
The LD_LIBRARY_PATH problem is fixed in Trac #19641 On Tuesday, December 22, 2015 at 9:40:25 AM UTC+1, Eric Gourgoulhon wrote: > > Hi, > > Le vendredi 18 décembre 2015 16:46:19 UTC+1, leif a écrit : >> >> >> Not strange (although probably a flaw), but all binaries are built with >> SAGE_INSTALL_GCC=yes AFAIK, so Sage is mainly built with GCC 4.9.2 which >> ships with an older libstdc++. >> >> The issue will presumably vanish when we get rid of setting >> LD_LIBRARY_PATH (and using sage-native-execute here and there); until >> then, you can simply create symlinks to your distro's libstdc++, >> libgfortran, etc. >> >> > Thanks for these explanations. > But this means that all Ubuntu 15.10 users will be facing the same issue. > Why are Sage binaries built with SAGE_INSTALL_GCC=yes instead of > using gcc of the targeted system ? With Ubuntu 15.10, there is no problem > with the latter. Note that 15.10 is the latest Ubuntu version, so it is > somehow annoying if SageMath is shipping bad binaries for it, especially > given the present discussion of making jupyter the default notebook. > > Best wishes, > > Eric. > -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-release+unsubscr...@googlegroups.com. To post to this group, send email to sage-release@googlegroups.com. Visit this group at https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
