I may be a example of Volker's "random crap" problem... I participated in sage days 65 and still don't have a sage-from-source compiled. (see separate note in sage-devel.)
I also know next-to-nothing about make and computer architecture, so feel free to dismiss the following... How about this for a *radical* idea: a true bundle, with EVERYTHING that one needs all in the SAGE_ROOT directory. If you look at http://www.sagemath.org/documentation/html/en/installation/source.html you find the line "Since Sage builds its own GCC if needed," So some version of what I suggest supposedly already happens. (btw, I would *love* for that to happen on my machine, and make, and m4 and perl and ... as I suspect things are really out-of-whack for me right now.) If so, one needn't hope that things are installed correctly on a given machine, because everything starts from SAGE_ROOT. On Sunday, June 14, 2015 at 4:00:05 PM UTC-5, Jeroen Demeyer wrote: > > On 2015-06-14 11:05, Volker Braun wrote: > > But more machines won't > > help unless you want to install random crap on them. > > I don't know if you're serious, but I think that more machines *with* > random crap might actually be a good idea. > > Normally, packages aren't supposed to look in /usr/local if they are > passed proper configuration flags. If they still do, that's either a bug > in the package or in the way we use it. > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
