If you look in the header the problem this time is precisely that the
offending line is not guarded by #if OS_OBJECT_USE_OBJC
On Tuesday, October 21, 2014 7:50:56 AM UTC+1, Samuel Lelievre wrote:
>
> William Stein wrote:
>
> > This pattern has happened with literally every single OS X release:
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], wi
>
>
>
> This pattern has happened with literally every single OS X release:
>
>
Agreed, this is really annoying, and +A to the person who is the hero each
time!
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group an
On Mon, Oct 20, 2014 at 10:05 AM, Samuel Lelievre
wrote:
> Hi all,
>
> I am using OS X 10.10 Yosemite.
>
> I was beta-testing it since July, and failing to build Sage.
>
> (Strangely I never thought about using the OSX-10.9 version.
> I just tried and it works! Thanks Stefan for asking the
> quest
Oh that's fun. I usually get that message when xvcc cannot find its own
libraries
in stage 1. Something that is usually solved by setting LD_LIBRARY_PATH (or here
its mac equivalent) or using static libraries for gmp/mpfr/mpc. But this is new,
someone hasn't been thinking forward about new version
