From: Gavin Andresen <gavinandresen@gmail•com>
To: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: [Bitcoin-development] 0.8.0rc1 status
Date: Fri, 8 Feb 2013 18:49:09 -0500 [thread overview]
Message-ID: <CABsx9T1D08uOenXch7ZwrEaCeOdFCFOtzK8ochN8z3REGm0mLQ@mail.gmail.com> (raw)
Linux builds of 0.8.0rc1 are in good shape; easily gitian-reproduceable.
Windows builds are varying with every compile, and I think I finally
figured out why: we are not passing the -frandom-seed flag down into
the leveldb build (I used objdump to dump two different binaries, and
they differed only in the names of some leveldb objects). That should
be an easy makefile fix.
The OSX build is in pretty good shape, but needs
https://github.com/bitcoin/bitcoin/pull/2286 to compile.
So: I think the path forward is to announce 0.8.0rc1 with the binaries
we've got, to get more testing.
Then before final release (or rc2, if that is needed) pull #2286 and
create and pull a patch to fix the windows non-determinism problem.
I'm done for today, but should have time to sign the windows setup.exe
and send out a rc1 announcement tomorrow.
--
--
Gavin Andresen
next reply other threads:[~2013-02-08 23:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-08 23:49 Gavin Andresen [this message]
2013-02-09 1:29 ` Luke-Jr
2013-02-09 4:11 ` grarpamp
2013-02-09 6:10 ` Pieter Wuille
2013-02-09 7:58 ` Robert Backhaus
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=CABsx9T1D08uOenXch7ZwrEaCeOdFCFOtzK8ochN8z3REGm0mLQ@mail.gmail.com \
--to=gavinandresen@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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