Perhaps a slightly less radical idea would be to make sage interface with the underlying package manager to install the necessary dependencies when running make. Or at the very least, stop immediately and state what needs to be installed if a system-wide dependency is not available.
Best, Travis On Thursday, June 18, 2015 at 3:08:57 PM UTC-7, la...@math.luc.edu wrote: > > 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. > > -- 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.
