What do the commands

which python
python --version

tell you? OS X should include a version of Python. Mine has version 2.7.10, 
dating from last December, in /usr/bin. If yours is missing, maybe your 
PATH is wrong or maybe your Xcode installation is broken somehow.



On Monday, July 25, 2016 at 9:06:35 PM UTC-7, Paul Masson wrote:
>
>
> MacBook-Retina:~ Masson$ cd 
> Downloads/GitHub/sage/local/var/lib/sage/installed
>
> MacBook-Retina:installed Masson$ ls
>
> arb-2.8.1.p0 gcc-4.9.3.p1 mpfr-3.1.4 patch-2.7.5
>
> bzip2-1.0.6-20150304 gf2x-1.1.p1 mpir-2.7.2 pkgconf-0.9.7
>
> flint-2.5.2.p0 mpc-1.0.3.p0 ntl-9.6.2.p1
>
>
> On Monday, July 25, 2016 at 8:26:25 PM UTC-7, leif wrote:
>>
>> Paul Masson wrote: 
>> > Ran make again without specifying any jobs, which I understand to be 
>> the 
>> > same as specifying one job. Same error from Atlas this time as well. 
>> > Here's the contents of that log: 
>> > 
>> > Found local metadata for atlas-3.10.2.p2 
>> > Attempting to download package atlas-3.10.2.tar.bz2 from mirrors 
>> > 
>> http://mirrors.xmission.com/sage/spkg/upstream/atlas/atlas-3.10.2.tar.bz2 
>> > 
>> [.......................................................................] 
>> > atlas-3.10.2..p2 
>> > ==================================================== 
>> > Setting up build directory for atlas-3.10.2..p2 
>> > Finished set up 
>> > Error: The spkg-install script is written in Python, but the Python 
>> > package is not yet installed in Sage.  You should add $(PYTHON) 
>> > as dependency in build/pkgs/atlas/dependencies 
>>
>> Yep.  Both errors (in ATLAS and Cython) have the same cause, namely that 
>> Sage's Python doesn't get built.  (I know how I could manage to get the 
>> same errors, but in your case something else seems to be wrong.) 
>>
>> Could you post your build/make/Makefile somewhere, too?  (It's not that 
>> large, but long, ~2900 lines...) 
>>
>>
>> And to go triple-safe, the output of 'ls local/var/lib/sage/installed/'. 
>>
>>
>> -leif 
>>
>> > On Monday, July 25, 2016 at 4:47:06 PM UTC-7, leif wrote: 
>> > 
>> >     Paul Masson wrote: 
>> >     > Sorry about that Leif. My bad. 
>> >     > 
>> >     > I'm the only person using this machine, so I'm the administrator. 
>> The 
>> >     > directory in the Cython error is a system directory. 
>> > 
>> >     Yes, and Sage shouldn't try to write to /that/. 
>> > 
>> > 
>> >     > I think my very first build of 7.2 a couple months ago was not a 
>> >     > parallel build: is that an issue for an initial build? 
>> > 
>> >     It shouldn't, but somehow Sage's Python apparently doesn't get 
>> built 
>> >     [early enough]; you may try to build with just one 'make' job 
>> ('-j1'), 
>> >     be it just to better track down what's going wrong. 
>> > 
>> > 
>> >     People on MacOS X will have better suggestions I guess. 
>> > 
>> > 
>> >     -leif 
>>
>>
>>

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Reply via email to