From: "Luke-Jr" <luke@dashjr.org>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] 0.8.0rc1 status
Date: Sat, 9 Feb 2013 01:29:16 +0000 [thread overview]
Message-ID: <201302090129.17999.luke@dashjr.org> (raw)
In-Reply-To: <CABsx9T1D08uOenXch7ZwrEaCeOdFCFOtzK8ochN8z3REGm0mLQ@mail.gmail.com>
On Friday, February 08, 2013 11:49:09 PM Gavin Andresen wrote:
> 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.
FWIW, this should be already mostly-fixed in pull #2243 I submitted 9 days
ago... only thing not in that pull is changing gitian to use the standard
CXXFLAGS rather than our non-standard DEBUGFLAGS (whether DEBUGFLAGS should be
propagated to LevelDB or not is another conversation I guess).
Luke
next prev parent reply other threads:[~2013-02-09 2:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-08 23:49 [Bitcoin-development] 0.8.0rc1 status Gavin Andresen
2013-02-09 1:29 ` Luke-Jr [this message]
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=201302090129.17999.luke@dashjr.org \
--to=luke@dashjr.org \
--cc=bitcoin-development@lists.sourceforge.net \
/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