Since I had never tried downloading and running a binary, I thought I would. For a laptop running ubuntu 14.04 I looked at the UK mirror and found no 7.3 binary so I downloaded the 7.2 one (there was 7.3 for ubuntu 12.04 but not 14.04 or later). Using the command-line I unpacked the tarball (tar jxf ...tar.bz2) which created a SageMath directory, so I cd'd into there and typed ./sage. As the original poster reported, this resulted in a lot of "patching..." messages appearing, followed by the 7.2 banner and a sage: prompt. Subsequent runs also worked without the patching stuff.
This does not help much, though I wonder how many of the posted binaries are tested? And why is it neccessary to patch all those files? If it really is necessary (and it might well be) then it would be more user-friendly for the function which is causing all that patching to be done to display a more user-friendly message, something like "I see that this is the first time you are running this copy of SageMath. Please wait while some one-time configuration is carried out...." with the actual pacthing messages going to /dev/null or a log file. John On 2 September 2016 at 11:15, Dima Pasechnik <dimp...@gmail.com> wrote: > > > On Friday, September 2, 2016 at 8:31:55 AM UTC, John Cremona wrote: >> >> >> >> On 2 September 2016 at 07:17, Thierry Dumont <tdu...@math.univ-lyon1.fr> >> wrote: >> >>> Le 01/09/2016 à 21:29, Pierre-Yves Bienvenu a écrit : >>> > Hi, I'm trying to use Sage 7.3 on Ubuntu. I've downloaded the archive, >>> > used archive manager to extract it and got a directory SageMath. Inside >>> > I double click the sage executable. The terminal opens and after a lot >>> > of lines starting with "patching" it says "SageMath version 7.3, >>> release >>> > date..." etc but immediately after "Ooops sage crashed". No way to find >>> > the allegedly created report so I don't know exactly what's wrong. Any >>> > help would be greatly appreciated (I'm an ignorant I must say). >>> > >>> > -- >>> > >>> I think you shoul not process like this. >>> Open a shell(terminal), go in the uncompresed directory and launch >>> ./sage (do not click). >>> At least it will be cleaner. When "clicking", I am not sure the >>> environment is the same. >>> >> >> It is not very user friendly to provide executables which do not execute! >> > > that's executioners that execute, no? > > >> >> John Cremona >> >> >>> Yours >>> t. >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "sage-support" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to sage-support...@googlegroups.com. >>> To post to this group, send email to sage-s...@googlegroups.com. >>> Visit this group at https://groups.google.com/group/sage-support. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- > You received this message because you are subscribed to the Google Groups > "sage-support" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to sage-support+unsubscr...@googlegroups.com. > To post to this group, send email to sage-support@googlegroups.com. > Visit this group at https://groups.google.com/group/sage-support. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-support+unsubscr...@googlegroups.com. To post to this group, send email to sage-support@googlegroups.com. Visit this group at https://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout.
