Bug#920147: Sage FTBFS on mipsel + mips64el

[John Scott]

On the off-chance they're relevant and Jmol is a red herring, I'm re-sending
my misplaced comments [1] about relevant parts of /usr/bin/sage here:

> 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 [in
> addition to the -z] 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)?
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948731#12
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: This is a digitally signed message part.
URL: <http://alioth-lists.debian.net/pipermail/debian-science-maintainers/attachments/20200201/872a55f5/attachment.sig>