Maybe you can check where gap-static-linux-i686 is on your system, that might give us a clue for how it is being run.
On Friday, January 17, 2014 1:28:52 PM UTC-5, Georg Grafendorfer wrote: > > As I told you, this already happend at least more than 5 times with > several 5.x versions of sage, after building sage from scratch and > performing ptestlong, I was just to bussy to report it earlier. > > Allthough having no clue about gap I can "guarantee" you that this comes > from sage and ptestlong... > > > On Friday, January 17, 2014 6:53:33 PM UTC+1, Volker Braun wrote: >> >> Is "gap-static-linux-i686" really our gap binary? I think ours would be >> SAGE_ROOT/local/gap/latest/bin/<arch>/gap. >> >> Also, whats this about gap3 in the output? >> > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/groups/opt_out.
