Bug#948731: /usr/bin/sage shell script

John Scott jolescot at iu.edu
Sun Jan 12 17:07:41 GMT 2020


By the way, looking at the header of that file I see
# workaround #892622; unfortunately we can't simply run setarch -R when 
running Singular
# because src/sage/libs/singular/singular.pyx loads libsingular.so into the 
current process
if [ "$(arch)" = "mips64" -a -z "$SAGE_DEB_MIPS64_WORKAROUND" ]; then
    SAGE_DEB_MIPS64_WORKAROUND=1 exec setarch mips64 -R "$0" "$@"
fi

I don't understand the test inside the brackets. Why do you use -a when there 
is no mention of a file? And if you're checking equality, shouldn't that be a 
double equals sign (==)?

Furthermore, the code refers to mips64, but #892622 refers to mips64el. Is it 
possible these issues are the cause of Sage failing to build from source there 
(#920147)?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3721 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/debian-science-maintainers/attachments/20200112/8c56db97/attachment.bin>


More information about the debian-science-maintainers mailing list