Maxima/ECL combination not printing a leading zero

asinh(1.0) is approximately 0.88137358701954302523. Using ECL 10.2.1 and Maxima 
5.20.1, on two Solaris 10 systems, we get a problem on the system running 
Solaris x86, but not on the system with the SPARC processor.

This was in Sage 4.5.2.rc1, but Maxima is (as far as I can tell), run 
independently of Sage, so the maxima input and output are seen, with no 
processing by Sage.

On the Solaris 10 x86 system, we see:


============================================================
drkirkby at fulvia:[/home/palmieri/fulvia/32bit/sage-4.5.2.rc1] $ ./sage -maxima
;;; Loading 
#P"/home/palmieri/fulvia/32bit/sage-4.5.2.rc1/local/lib/ecl/defsystem.fas"
;;; Loading #P"/home/palmieri/fulvia/32bit/sage-4.5.2.rc1/local/lib/ecl/cmp.fas"
;;; Loading #P"/home/palmieri/fulvia/32bit/sage-4.5.2.rc1/local/lib/ecl/sysfun.lsp"
Maxima 5.20.1 http://maxima.sourceforge.net
using Lisp ECL 10.2.1
Distributed under the GNU Public License. See the file COPYING.
Dedicated to the memory of William Schelter.
The function bug_report() provides bug reporting information.
(%i1) asinh(1.0);
(%o1)                          .8813735870195429
(%i2)
===============================================================


Although the result is numerically correct, it is certainly not printed in a 
very nice way.

When run on a Solaris 10 SPARC system, one gets a leading zero as one would hope 
for.


================================================================
32 drkirkby at redstart:[~/redstart/32/sage-4.5.2.rc1] $ ./sage -maxima
;;; Loading 
#P"/export/home/drkirkby/redstart/32/sage-4.5.2.rc1/local/lib/ecl/defsystem.fas"
;;; Loading 
#P"/export/home/drkirkby/redstart/32/sage-4.5.2.rc1/local/lib/ecl/cmp.fas"
;;; Loading 
#P"/export/home/drkirkby/redstart/32/sage-4.5.2.rc1/local/lib/ecl/sysfun.lsp"
Maxima 5.20.1 http://maxima.sourceforge.net
using Lisp ECL 10.2.1
Distributed under the GNU Public License. See the file COPYING.
Dedicated to the memory of William Schelter.
The function bug_report() provides bug reporting information.
(%i1)  asinh(1.0);
(%o1)                          0.881373587019543
(%i2)
================================================================

Can anyone suggest what may or may not be the cause of this difference in 
behavior? There's a bit more details on a Sage trac bug ticket I created for 
this, though I believe there's enough information above.

Although the Solaris 10 SPARC port of Sage has been stable for several month, on 
Solaris 10 x86, Sage was built for the first time this week, so a few problems 
do exist, though I don't think there's anything related to this problem.


Dave