Hi folks, Ticket #6476
http://trac.sagemath.org/sage_trac/ticket/6476 upgrades Singular to version 3-1-0-4. You can find the new spkg at http://sage.math.washington.edu/home/malb/spkgs/singular-3-1-0-4-20090818.spkg or http://sage.math.washington.edu/home/mvngu/patch/singular-3-1-0-4-20090818.spkg The updated spkg installs fine on T2 with my (failed) build of Sage 4.1.1. However, at the end of the installation process, I notice this message: > Successfully installed singular-3-1-0-4-20090818 > Now cleaning up tmp files. > rm: cannot remove directory > `/scratch/mvngu/sage-4.1.1/spkg/build/singular-3-1-0-4-20090818': Invalid > argument > Making Sage/Python scripts relocatable... > Making script relocatable > Finished installing singular-3-1-0-4-20090818.spkg The line rm: cannot remove directory `/scratch/mvngu/sage-4.1.1/spkg/build/singular-3-1-0-4-20090818': Invalid argument is a result of the following lines from the script SAGE_ROOT/local/bin/sage-spkg: > # Delete the temporary build directory if required. > if [ $DELETE_TMP -eq 1 ]; then > echo "Now cleaning up tmp files." > if [ -d "$SAGE_PACKAGES/build/$PKG_NAME" ]; then > # the if is there only to avoid the possibility of a weird bug. > rm -rf "$SAGE_PACKAGES/build/$PKG_NAME" > fi > else > echo "You can safely delete the temporary build directory" > echo "$SAGE_PACKAGES/build/$PKG_NAME" > fi Note that the compilation of Sage 4.1.1 fails on T2 when building sage-4.1.1.spkg. And singular-3-1-0-2-20090620.p0.spkg builds successfully prior to starting the compilation of sage-4.1.1.spkg. To ensure that the above "Invalid argument" returned by "rm" wasn't specific to singular-3-1-0-4-20090818.spkg, I forced a re-installation of the current Singular spkg that's shipped with Sage 4.1.1, i.e. singular-3-1-0-2-20090620.p0.spkg. Of course the re-installation went OK, but I also got the same "Invalid argument": > real 40m50.228s > user 37m48.054s > sys 2m27.174s > Successfully installed singular-3-1-0-2-20090620.p0 > Now cleaning up tmp files. > rm: cannot remove directory > `/scratch/mvngu/sage-4.1.1/spkg/build/singular-3-1-0-2-20090620.p0': Invalid > argument > Making Sage/Python scripts relocatable... > Making script relocatable > Finished installing singular-3-1-0-2-20090620.p0.spkg Sage 4.1.1 fails to build on cleo, which runs RHEL. The compilation dies before reaching Singular, aborting at the point when building NTL. I forced a re-installation of zn_poly-0.9.p1.spkg. The installation went OK without any of that "Invalid argument" found under Solaris on T2. Sage 4.1.1 fails to build on menas, which runs SUSE. The compilation also dies before reaching Singular, and it aborts at the point when building cliquer. I forced a re-installation of cython-0.11.2.1.spkg, which built OK without any of that "Invalid argument". So somewhere in some script, environment variables are set which are specific to Linux systems, but which would result in Solaris (on T2) reporting an "Invalid argument". -- Regards Minh Van Nguyen --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
