From: Dave Wolfe <dwolfe@lists.linuxppc.org>
To: William Blew <wblew@home.com>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: drand48() broken?
Date: Tue, 15 Aug 2000 17:26:11 -0500 [thread overview]
Message-ID: <20000815172610.B16806@lists.linuxppc.org> (raw)
In-Reply-To: <Pine.LNX.4.10.10008151301340.12763-100000@apollo.kulian.net>; from William Blew on Tue, Aug 15, 2000 at 01:12:58PM -0700
[ William Blew writes: ]
> On Tue, 15 Aug 2000, Dave Wolfe wrote:
>
> > Is my PPC installation just too old and drand48() (actually it's
> > probably srand48() that's broken) is fixed now? To see what your Perl
> > uses, enter `perl -V:randfunc' (just `perl -V' gives you the version of
> > Perl). If it says `drand48', try this:
> >
> > while true;do perl -e 'print int rand(62), " "';done
> >
> > (Hit ^C to stop it) then let's compare versions of the various parts.
>
> I am using YDL champion server 1.2 on a beige G/3266 Power Macintosh
>
> kernel: 2.2.17-0.6.1 (the latest kernel from YDL)
> gcc: version 2.95.2, release 1i ( from champion server 1.2 )
> glibc: version 2.1.3, release 5a ( from champion server 1.2 )
>
> perl 5.6.0, release 1 ( built from the SRPM )
>
> perl -V:randfunc yields randfunc='drand48';
>
> [root@artemis /tmp]# while true;do perl -e 'print int rand(62), " "';done
> 61 32 24 11 34 21 42 18 9 59 10 41 44 27 37 2 44 9 47 3 34 42 51 7 40 0
[...]
> Is this different from your results? Should I re-compile my perl install?
Quite. I got a continuous string of '19 19 19 19 19 19 19 19'. Sounds
like yours is working just fine.
--
Dave Wolfe
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2000-08-15 22:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-15 15:45 drand48() broken? Dave Wolfe
2000-08-15 20:12 ` William Blew
2000-08-15 22:26 ` Dave Wolfe [this message]
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=20000815172610.B16806@lists.linuxppc.org \
--to=dwolfe@lists.linuxppc.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=wblew@home.com \
/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;
as well as URLs for NNTP newsgroup(s).