Aha – thank you! I will start playing with this... – Louis
On Monday, May 22, 2023 at 12:17:56 PM UTC-4 Dima Pasechnik wrote: > On Mon, May 22, 2023 at 4:53 PM Dima Pasechnik <dim...@gmail.com> wrote: > > > > On Mon, May 22, 2023 at 3:09 AM Louis Deaett <louis....@gmail.com> > wrote: > > > > > > Many thanks for the word of encouragement, and also for pointing me to > that ticket. I was not even familiar with tox, to be honest, so I read up > on its intended purpose. > > > > > > I can see that the source for Sage 9.7 that I have here has a tox.ini > file, but inside there is no reference to MacPorts. Is that because the > MacPorts environments alluded to in the thread (the one you linked) haven't > been merged into the release branch of Sage? > > > > > > After further digging, I did notice this branch: > > > > > > > https://github.com/sagemath/sagetrac-mirror/tree/u/mkoeppe/tox_ini__add_macports_environment > > > > > > It looks like it hasn't seen any commits in almost a year. But is that > still my best starting point? Shall I pick up and work with this, or has > this effort been abandoned? > > > > indeed, no work had been done since. > > A good starting point would be to take it rebased over the latest > develop, here: > > > https://github.com/dimpase/sage/pull/new/u/mkoeppe/tox_ini__add_macports_environment > > Oops, I meant to post this: https://github.com/sagemath/sage/pull/35667 > (same branch, as a PR) > > > > HTH > > Dima > > > > > > > > > > Many thanks again! > > > > > > – Louis > > > > > > > > > On Friday, May 5, 2023 at 2:42:19 PM UTC-4 John H Palmieri wrote: > > >> > > >> In principle this should work. See > https://github.com/sagemath/sage/issues/31505 for some relevant > information. Others might have direct experience with it. > > >> > > >> On Friday, May 5, 2023 at 11:24:07 AM UTC-7 Louis Deaett wrote: > > >>> > > >>> 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+...@googlegroups.com. > > > To view this discussion on the web visit > https://groups.google.com/d/msgid/sage-devel/5a8f7076-fcb4-462d-8c48-a7b1c7fea26dn%40googlegroups.com > . > -- 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/5fddf3e4-2de2-4634-a48c-b91eff3c660an%40googlegroups.com.
