| Newsgroups |
gmane.lisp.scheme.bigloo |
| Organization |
Inria |
| Message-ID |
<[email protected]> |
> I hacked up process.scm to just exit and ran 'make test' again.
>
> This time I get to :
>
> .....
> abcd_efgh...Resolving key for: 89d06450289f546b
> found 1 keys.
> testy key <[email protected]> 89d06450289f546b DSA (Digital Signature Standard)
> ok.
>
> All tests executed...
> all succeeded
> make[1]: Leaving directory
> `/proj/samson/user/tdukes/Downloads/tmp/bigloo4.1a-beta04Feb14'
> bash-4.2$
>
>
> But looking back was concerned about:
>
> ...
> bignum.scm:
> 58.bignum(bignum.34) fail: provided [#f], wanted [#t]
> 59.bignum(bignum.35) fail: provided [#f], wanted [#t]
> 60.bignum(bignum.36) fail: provided [#f], wanted [#t]
> list.scm:
> ...
> process.scm:
>
> ------------------------------
> recette failed: 3 error(s) occurred.
>
>
> Should not reporting these failures be an issue? I don't see the work
> 'fail' or 'error' anywhere else in the output other than 'error.scm'
>
> I will look at more detail about why process.scm is not completing.
>
> Thanks,
> Todd
Do you get these errors with the C or the JVM backend? I would say that for
the C backend they are "expected" if you don't have GMP installed and
recognized at configuration time. I don't think it is a real problem because
independently of this minor problem using bignum without GMP is unrealistic.
The Scheme implementation of bignum is by far too slow.
--
Manuel