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.
But spkg-install is generating the error message from 'cp'. If I add
'set -e' at the top, so this exits and aborts the build of sage.
I've put the full file below. Does anyone know if the copy should be
removed, or what should be happening?
Dave
====================
drkir...@smudge:[~/sage/sage-4.1.1/spkg/standard/sage_scripts-4.1.1] $
cat spkg-install
#!/usr/bin/env bash
CUR=`pwd`
TARGET="$SAGE_ROOT"/local/bin/
if [ -d "$TARGET"/.hg ]; then
# Merge the repositories, rather than overwrite changes
# that the user may have made.
cd "$TARGET"
hg ci
hg pull "$CUR"
hg merge tip
hg ci -m "Check-in during upgrade of Sage."
hg update
else
# Initial install. Just copy all the files over.
cp -r sage-* dsage_* *doctest.py SbuildHack.pm .hg*
ipy_profile_sage.py "$TARGET"
fi
# Finally, make sure some symbolic links exist.
cd "$CUR"
# These are not part of the scripts repo and are
# not under revision control, so they get wacked (at least
# we do save the last versions in tmp, just in case).
TMP="$SAGE_ROOT"/tmp/
if [ ! -d "$TMP" ]; then
mkdir "$TMP"
fi
cp "$SAGE_ROOT"/sage-python "$TMP"/
cp sage-python "$SAGE_ROOT"/
cp "$SAGE_ROOT"/spkg/install "$TMP"/
cp install "$SAGE_ROOT"/spkg/
cp "$SAGE_ROOT"/*.txt "$TMP"/
cp *.txt "$SAGE_ROOT"/
rm -rf "$TMP"/ipython
cp -r "$SAGE_ROOT"/ipython "$TMP"/
cp -r ipython "$SAGE_ROOT/"
# I think these below should moved to the relevant spkg's.
# -- William Stein (2007-10-04)
cd "$TARGET"
ln -sf python sage.bin
ln -sf Singular sage_singular
ln -sf gp sage_pari
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send an email to [email protected]
To unsubscribe from this group, send an email to
[email protected]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
