William Stein wrote:
> This pattern has happened with literally every single OS X release:
So true! Searching sage lists for '_scproxy' reveals that the failure
to build the _scproxy module happened before on new releases of OS X.
See the search results for sage-release [0] and sage-devel [1], with
especially thread [2], where Volker [3] suggested a workaround:
The following workaround should help to get
around Apple's broken headers:
CFLAGS="-DOS_OBJECT_USE_OBJC=0"
export CFLAGS
make
Maybe this workaround could also help in the present situation?
In the meanwhile, I sent a problem report to Apple via the
'Feedback assistant'.
[0] https://groups.google.com/forum/#!searchin/sage-release/_scproxy
[1] https://groups.google.com/forum/#!searchin/sage-devel/_scproxy
[2] https://groups.google.com/d/topic/sage-devel/9B1GyPe6MAM/discussion
[3] https://groups.google.com/d/msg/sage-devel/9B1GyPe6MAM/lQTo4ZrbjlAJ
--
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 post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
