ports/128710: math/open-axiom port appears broken

[Nate Eldredge]

>Number:         128710
>Category:       ports
>Synopsis:       math/open-axiom port appears broken
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-ports-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Nov 09 00:50:02 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Nate Eldredge
>Release:        7.0-RELEASE-p5
>Organization:
>Environment:
FreeBSD vulcan.lan 7.0-RELEASE-p5 FreeBSD 7.0-RELEASE-p5 #14: Sun Oct  5 11:20:57 PDT 2008     nate at vulcan.lan:/usr/obj/usr/src/sys/VULCAN  amd64

>Description:
The math/open-axiom port seems broken.  I tried a few things from an Axiom tutorial I found, but got poor results.

nate at vulcan:/usr/home/nate$ pkg_info |grep axiom 
open-axiom-1.2.0    A computer algebra system
nate at vulcan:/usr/home/nate$ open-axiom 
             OpenAxiom: The Open Scientific Computation Platform 
                          Version: OpenAxiom 1.2.0
               Built on Saturday November 8, 2008 at 11:43:24 
-----------------------------------------------------------------------------
   Issue )copyright to view copyright notices.
   Issue )summary for a summary of useful system commands.
   Issue )quit to leave OpenAxiom and return to shell.
-----------------------------------------------------------------------------
 
(1) -> 
(1) -> 1+1

   (1)  2
                                                        Type: PositiveInteger
(2) -> 123^45

 
   >> System error:
   
LOG: floating point overflow


(2) -> 2^65536

nate at vulcan:/usr/home/nate$ echo $?
0

As I understand it, both of the exponentiation computations should have given a result as a big integer.  Indeed, this is what happens with original Axiom on a Linux system.  Instead the first one gives a floating point overflow and the second causes open-axiom to exit.

It is possible this is just a situation of open-axiom behaving differently from classic Axiom, but it seems unlikely.  It could also be an amd64 related problem; I have not tried it on i386.
>How-To-Repeat:
See above.
>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted: