This is the mail archive of the
gsl-discuss@sources.redhat.com
mailing list for the GSL project.
Can we close BUG#6 ?
- From: Slaven Peles <peles at cns dot physics dot gatech dot edu>
- To: Brian Gough <bjg at network-theory dot co dot uk>,gsl-discuss at sources dot redhat dot com
- Date: Tue, 8 Oct 2002 15:55:24 -0400
- Subject: Can we close BUG#6 ?
- References: <m17z05G-0000eCC@localhost>
I posted this before, but I guess there's no harm repeating it. If I compile
GSL on Compaq Alpha with the additional flag "-ieee" everything seem to work
fine and make check reports that all checks are passed. So it seems that bug
is actually in documentation only. In INSTALL file hints for Compaq/DEC Alpha
should say:
> Hints for Compaq/DEC Alpha
> ==========================
>
> The library should compile successfully with Compaq's C compiler using
> the -std option for ANSI conformance. Use
>
> CC=cc ./configure
> make CFLAGS="-std -ieee"
>
> to build the library this way.
>
> Use GNU tar to unpack the tar file, as Tru64 tar gives an error
> halfway through.
Is it safe to close this bug then?
Cheers,
Slaven
-------------------------------------------------------------------
BUG#6 -- gsl_isnan, isinf on Compaq Unix STATUS: open
From: Slaven Peles <peles@cns.physics.gatech.edu>
To: gsl-discuss@sources.redhat.com
Subject: Make check fails on Alpha
Date: Fri, 20 Sep 2002 08:47:54 -0400
I compiled GSL 1.2 on Compaq Alpha with:
CC=cc ./configure
make CFLAGS="-std"
Compiler I used identifies itself as:
Compaq C V6.3-025 on Compaq Tru64 UNIX V5.1 (Rev. 732)
Compiler Driver V6.3-026 (sys) cc Driver
Make check fails for gsl_isnan, gsl_isinf and gsl_finite functions.
make check-TESTS
FAIL: gsl_isinf(inf) (0 observed vs 1 expected)
FAIL: gsl_isinf(-inf) (0 observed vs -1 expected)
FAIL: gsl_isnan(nan) (0 observed vs 1 expected)
FAIL: gsl_finite(inf) (1 observed vs 0 expected)
FAIL: gsl_finite(nan) (1 observed vs 0 expected)
On Tuesday 08 October 2002 03:31 pm, Brian Gough wrote:
> I'm also posting a summary of the current BUGS list.
>
> These bugs are all open, so if you think you might be able to fix any
> of them see the top-level BUGS file in CVS for more details about each
> one.
>