From: Sylvain Le Gall <gildor478@gmail.com>
To: Francois BERENGER <francois.berenger@inria.fr>, caml-list@inria.fr
Subject: Re: [Caml-list] Zarith problems on ppc64le
Date: Mon, 07 Nov 2016 14:11:52 +0000 [thread overview]
Message-ID: <CAOCAUGPHKvdXx6rx-5ueQ8EKRNCMFd-EA6_jagjaDjUm4Uc5wA@mail.gmail.com> (raw)
In-Reply-To: <aa2dd790-a548-780f-8563-5c02eafec089@inria.fr>
[-- Attachment #1: Type: text/plain, Size: 2442 bytes --]
1. the machine is up
$ ssh ssh.ocamlcore.org
RSA host key for IP address '87.98.190.243' not in list of known hosts.
Last login: Tue Oct 18 08:17:05 2016 from 212.51.151.109
(but it can be a bit slow on the authentication, but not enough to cause a
time out)
2. Check your SSH port, it must be 522.
https://forge.ocamlcore.org/forum/forum.php?forum_id=939
There is a mention of this news on the SCM settings page as well:
https://forge.ocamlcore.org/scm/?group_id=243
Using 522 as a port:
$ svn checkout svn+ssh://gildor-admin@ssh.ocamlcore.org/svn/zarith/trunk
A trunk/z_pp.ml
A trunk/q.mli
A trunk/configure
A trunk/z_pp.pl
3. Anonymous access is indeed buggy, I will fix it later.
Can you open a bug here, so that you get notified when it is solved:
https://forge.ocamlcore.org/tracker/?atid=101&group_id=1&func=browse
Actually, the fix is pretty straightforward:
rather than, as stated on the SCM page:
$ svn checkout svn://ssh.ocamlcore.org/svn/zarith/trunk
use:
$ svn checkout svn://ocamlcore.org/svn/zarith/trunk
I'll update the instruction on the SCM page and publish a news about that.
Le lun. 7 nov. 2016 à 14:55, Francois BERENGER <francois.berenger@inria.fr>
a écrit :
> On 11/07/2016 02:22 PM, Richard W.M. Jones wrote:
> >
> > https://bugzilla.redhat.com/show_bug.cgi?id=1392247
> >
> > Zarith fails tests on OCaml 4.04.0 + ppc64le with some fairly gross
> > errors, eg:
> >
> > of_float -1.
> > - = -1
> > + = 0
> >
> > (It passes fine on OCaml 4.04.0 + ppc64)
> >
> > The implementation of Zarith is quite complex and I've so far failed
> > to understand what's going on.
> >
> > However an additional problem which makes debugging this harder is
> > that I cannot work out how to check out the source code for the
> > package. Using anon svn access hangs. Using svn+ssh access fails to
> > authenticate. (Could we switch the project over to git?) I'm fairly
> > sure this isn't a network problem at my end.
>
> svn: E000110: Can't connect to host 'ssh.ocamlcore.org': Connection
> timed out
>
> I suppose this machine is down.
>
> On the other hand, opam can tell you how to get a tarball:
> # opam info zarith
> [...]
> upstream-url:
> https://forge.ocamlcore.org/frs/download.php/1574/zarith-1.4.1.tgz
> [...]
>
> This URL works with wget.
>
> --
> Regards,
> Francois.
> "When in doubt, use more types"
>
[-- Attachment #2: Type: text/html, Size: 4886 bytes --]
next prev parent reply other threads:[~2016-11-07 14:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-07 13:22 Richard W.M. Jones
2016-11-07 13:31 ` Nicolas Ojeda Bar
2016-11-07 13:55 ` Francois BERENGER
2016-11-07 14:11 ` Sylvain Le Gall [this message]
2016-11-07 14:59 ` Simon Cruanes
2016-11-15 9:11 ` Bernhard Schommer
2016-11-07 15:48 ` Richard W.M. Jones
2016-11-07 15:58 ` Xavier Leroy
2016-11-07 16:19 ` Richard W.M. Jones
2016-11-08 10:00 ` Goswin von Brederlow
2016-11-08 11:10 ` Richard W.M. Jones
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAOCAUGPHKvdXx6rx-5ueQ8EKRNCMFd-EA6_jagjaDjUm4Uc5wA@mail.gmail.com \
--to=gildor478@gmail.com \
--cc=caml-list@inria.fr \
--cc=francois.berenger@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox