I literally meant "merge that [the branch from #31183] into the develop branch" (or vice versa), not just use the branch from #31183. The develop branch has some crucial pieces for building Sage in Big Sur.
John On Friday, January 22, 2021 at 11:30:57 AM UTC-8 [email protected] wrote: > Thanks! > > But it didn't fix it for me. For me the u/jhpalmieri/scipy-big-sur > <https://trac.sagemath.org/git-merger/470ffac111a769b3f2b02631e5174ff6fa483f2b> > fails > in numpy and > doesn't get to scipy. So I merged the change in #31166 (addressing numpy) > into > the scipy-big-sur branch and that fails to build in scipy again. > > Dan > > On Thursday, January 21, 2021 at 8:09:14 PM UTC-8 John H Palmieri wrote: > >> Ticket 31183 (https://trac.sagemath.org/ticket/31183) should fix that. >> Merging that into the develop branch works for me. >> >> -- >> John >> >> >> On Thursday, January 21, 2021 at 8:03:55 PM UTC-8 [email protected] wrote: >> >>> I'm unable to build the develop branch since upgrading my iMac to Big >>> Sur. I have python3 and scipy installed through homebrew. In /usr/local/bin >>> I have a symbolic link from python to python3. >>> >>> Although I have scipy through homebrew, Sage insists on installing the >>> spkg. In previous build attempts (in late December) the build failed in >>> numpy. >>> >>> I'm attaching my scipy.1.5.4.log. I would appreciate any suggestions. >>> >>> Thank you, >>> Daniel Bump >>> >>> >>> -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/426b1255-daea-4cfa-a4af-1ff42029f9acn%40googlegroups.com.
