I also have the recent GCL version:
(C1) build_info();
Maxima version: 5.9.0
Maxima build date: 19:17 9/9/2003
host type: i686-pc-linux-gnu
lisp-implementation-type: Kyoto Common Lisp
lisp-implementation-version: GCL-2-6.0999999999999996
Jaime
On Wed, Oct 01, 2003 at 01:13:36PM -0500, James Amundson wrote:
> Wow. That is very bad. The problem seems to be a bad interaction
> between (presumably) newer versions of GCL and Maxima. The GCL-Maxima
> 5.9.0 we distribute in RPM does not have the problem:
>
> ------------------------------------------------------------------
> (C1) build_info();
>
>
> Maxima version: 5.9.0
> Maxima build date: 22:24 2/9/2003
> host type: i386-redhat-linux-gnu
> lisp-implementation-type: Kyoto Common Lisp
> lisp-implementation-version: GCL-2-5.0
>
> (D1)
> (C2) asin(0.5);
>
> (D2) 0.5235987755983
> ------------------------------------------------------------------
>
> The GCL-Maxima I have in my development area (which I think is identical
> to the current cvs), when compiled with a recent cvs version of GCL,
> does have the problem:
> ------------------------------------------------------------------
> (C1) build_info();
>
>
> Maxima version: 5.9.0.1cvs
> Maxima build date: 7:43 9/25/2003
> host type: i686-pc-linux-gnu
> lisp-implementation-type: Kyoto Common Lisp
> lisp-implementation-version: GCL-2-6.0999999999999996
>
> (D1)
> (C2) asin(0.5);
>
> (D2) 0.5
> ------------------------------------------------------------------
>
> Please send the build_info() output for your Maxima.