On May 19, 2012, at 7:34 PM, kcrisman wrote:

> 
>> here is a fix:
>> in SAGE_ROOT (the directiry where Sage startup script, called sage, is), run
>> ./sage -f 
>> http://boxen.math.washington.edu/home/jdemeyer/spkg/mpir-2.4.0.p4.spkg
>> this will install a patched MPIR  spkg.
> 
> 
> I get an interesting warning when doing this on a similar machine.
> 
> Successfully installed mpir-2.4.0.p4
> cat: /Users/.../sage/VERSION.txt: No such file or directory
> Deleting temporary build directory
> /Users/.../sage/spkg/build/mpir-2.4.0.p4
> Making Python scripts relocatable...
> Finished installing mpir-2.4.0.p4.spkg
> 
> And indeed, my Sage binary has no VERSION.txt in the SAGE_ROOT directory.
>  

I had not noticed the warning when I rebuilt mpir,
but my SAGE_ROOT directory also lacks VERSION.txt 

But when I start sage, it reports:

./sage
----------------------------------------------------------------------
| Sage Version 5.0, Release Date: 2012-05-14                         |

so sage seems to know which version it is. What is the role of VERSION.txt ?

Jim

-- 
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to 
sage-support+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/sage-support
URL: http://www.sagemath.org

Reply via email to