OK, now the dynamically-linked v19.0.2 version is working fine. I guess
the "ERROR: Primenet error 1" was occurring while PrimeNet was down, as
Scott pointed out, not because there was anything buggy with the client.
It was just bad timing that I tried connecting then. :-) The static
executable still gives "Error 2250: Server unavailable", though.
Now I'm curious. v19 is linked against glibc2.1, right? I'm running a
glibc2 (not glibc2.1) machine (redhat 5.1 base, but almost everything has
been upgraded by compiling from source for a long time now). But the v19
dynamically-linked client is running just fine for me. Does anyone know
why? (I'm not complaining! :-)
Anyway, in light of my success here, I would suggest to those of you
trying unsuccessfully to run the static executable on a non-glibc2.1
machine to give the dynamically-linked executable a try. Of course, your
mileage may vary. (If you still have problems, feel free to email me, and
we'll try to sort out how our systems differ. I'm sure I'm not the only
one who'd like to document what's making or breaking mprime.)
-jason
On Tue, 12 Oct 1999, Robin Stevens wrote:
> On Mon, Oct 11, 1999 at 12:06:07PM -0500, jason wrote:
> > Well, I also downloaded mprime.tar.gz, and I had a slightly different
> > problem trying to connect to the PrimeNet server. To summarize:
> >
> > mprime.tar.gz v19.0.2: results in "ERROR: Primenet error 1"
> > sprime.tar.gz v19.0.2: results in "Error 2250: Server unavailable"
> > mprime.tar.gz v18.1.2: No problems.
> >
> > I wonder why the two versions give different error messages (and why I'm
> > getting them at all)? Anyway, I just compiled mprime from source
> > (debugging not enabled), and it's working just fine. Except for the fact
> > that I will not receive credit for my work, since I compiled it myself...
> > so much for initiative. :-)
>
> Indeed - this is the problem I reported a little while ago (again with
> sprime, since I don't have glibc 2.1 as yet). If v19 works faster, I might
> as well use it even if I can't currently report results. My temporary
> solution has been to grab 90 days' of work, switch the machines to run as
> dialup hosts even if they aren't, and wait for someone else to fix it,
> reporting via the web interface if necessary :-)
> --
> Robin Stevens <[EMAIL PROTECTED]> http://www-astro.physics.ox.ac.uk/~rejs/
> (+44) (0)1865: 273212 (work) 726796 (home) 273275 (fax) Pager: 0839 629682
> Oxford University Computing Services, 13 Banbury Road, Oxford OX2 6NN, UK
> "Life, loathe it or ignore it, you can't like it." -- Marvin
> _________________________________________________________________
> Unsubscribe & list info -- http://www.scruz.net/~luke/signup.htm
> Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
>
_________________________________________________________________
Unsubscribe & list info -- http://www.scruz.net/~luke/signup.htm
Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
