William Stein wrote: > On Sat, Aug 15, 2009 at 6:59 AM, Dr. David > Kirkby<david.kir...@onetel.net> wrote: >> Dr. David Kirkby wrote: >>> I notice this when installing sage. >>> >>> >>> sage_scripts-4.1.1/README.txt >>> sage_scripts-4.1.1/sage-crap >>> sage_scripts-4.1.1/sage-test-import >>> Finished extraction >>> **************************************************** >>> Host system >>> uname -a: >>> SunOS smudge 5.10 Generic_139555-08 sun4u sparc SUNW,Sun-Blade-1000 >>> **************************************************** >>> **************************************************** >>> CC Version >>> gcc -v >>> Using built-in specs. >>> Target: sparc-sun-solaris2.10 >>> Configured with: ../gcc-4.4.1/configure >>> --prefix=/usr/local/gcc-4.4.1-sun-linker/ --with-as=/usr/ccs/bin/as >>> --without-gnu-as --with-ld=/usr/ccs/bin/ld --without-gnu-ld >>> --enable-languages=c,c++,fortran --with-mpfr-include=/usr/local/include >>> --with-mpfr-lib=/usr/local/lib --with-gmp-include=/usr/local/include >>> --with-gmp-lib=/usr/local/lib CC=/usr/sfw/bin/gcc CXX=/usr/sfw/bin/g++ >>> LDFLAGS='-R /usr/local/lib -L /usr/local/lib' >>> Thread model: posix >>> gcc version 4.4.1 (GCC) >>> **************************************************** >>> cp: cannot access /export/home/drkirkby/sage/sage-4.1.1/sage-python >>> cp: cannot access /export/home/drkirkby/sage/sage-4.1.1/ipython >>> >>> real 0m0.243s >>> user 0m0.037s >>> sys 0m0.205s >>> Successfully installed sage_scripts-4.1.1 >>> >>> >>> The installation os sage_scripts appears to succeed, but there are two >>> errors from 'cp' which don't appear to be copied properly. >>> >>> >>> I believe I have seen this before, but it's quite easy to miss, as the >>> error does not cause the build of sage to stop. >>> >>> Dave >> I've found the problem, though I don't know the best way to fix it. >> >> In the file sage-4.1.1/spkg/standard/sage_scripts-4.1.1.spkg there are >> two identical files sage-spkg-install spkg-install. >> >> $ diff sage-spkg-install spkg-install >> $ >> >> >> Why there should be two identical files under two names I don't know. >> > > *EVERY* single file in SAGE_ROOT/local/bin/ > that is under revision control or installed by the sage_scripts spkg > starts with "sage-". In fact, when the sage_scripts-*.spkg is made, > it copies precisely the scripts of the form sage-* from local/bin/. > > Here is where sage-spkg-install is relevant: > > wst...@sage:~/build/sage-4.1.1/spkg/standard/sage_scripts-4.1.1$ grep > sage-spkg-install * > sage-make_devel_packages:cp -p $SAGE_ROOT/local/bin/sage-spkg-install > $SCRIPTS/spkg-install > > For consistency, the sage scripts spkg only uses files that start with > "sage-" in SAGE_ROOT/local/bin/. Since spkg-install doesn't begin > with "sage-" it is instead stored as "sage-spkg-install".
It is not really *instead* of, but in *addition* to. The same file is stored twice. Anyway, more to the point, the script is generating an error, as it tries to copy a non-existent file. Do you know the best way to fix that? There are also some notes at the bottom of the script about things that should be done in the .spkg files. I don't know if any of them have since been done, and so these could be removed. Dave --~--~---------~--~----~------------~-------~--~----~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
