I'm interested in Sage development (and contributing some enhancements) and so I'd like to be able to build the current release (and ultimately the development branch) from source.
I am running macOS 10.9 (Mavericks) because that is what I prefer, and because some of my hardware tops out at that version. Anyway, I've had decent success getting open-source software up and running under MacPorts, which has good support for 10.9 (and even earlier). So I've been working on building Sage from source using MacPorts. Compilation seems to go smoothly with MacPorts LLVM tools, but I've run into some snags whereby the build for some SPKGs seems to get gummed up when it can't locate some of the libraries or headers provided by MacPorts. By its nature, this hasn't felt like an insurmountable problem. Still, while I can keep hacking away at this, I figured I should ask: Is there any fundamental reason why what I'm trying to do should be impossible? If there are major barriers in my path with this that I'm just not encountering yet or just haven't realized, then it would (of course) help me out to know. For what it's worth, if building under MacPorts is theoretically possible but would require some additional effort on the Sage side, then that's something I'd be willing to contribute to, if anything comes out of my own efforts. Thanks in advance for any advice! -- Louis -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/c6f58f7e-9678-4649-9718-dd2213a9ff57n%40googlegroups.com.
