While looking at #7438 and friends, it was noticed that even on sage.math, where a certain spkg does build (unlike many places), a binary download Sage had to be run first in order to run the script that changes the hard-coded paths from the buildbot.
Would it make sense to run that script (sage-location, maybe?) before installing an spkg, to make sure that problem couldn't occur? First running Sage fixed the problem, of course, since that script was then run, but the error message was just a normal compilation can't find thus-and-such and it was only because I saw the /home/release bit that I realized this was the problem; a non-developer user would not be able to interpret this. - kcrisman -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
