From: Robert Backhaus <robbak@robbak•com>
To: Pieter Wuille <pieter.wuille@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] 0.8.0rc1 status
Date: Sat, 9 Feb 2013 17:58:33 +1000 [thread overview]
Message-ID: <CA+i0-i-0Q9EnMJvajEfUtPf7jGa3Aw5qn0RqwMqjP4nOASsO0g@mail.gmail.com> (raw)
In-Reply-To: <CAPg+sBiGHnT1-W7m8RCt93-cZbpz0vxm+YQcnpFNXv7f-mrBXg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1167 bytes --]
I have done test builds on FreeBSD.
Clean builds using gcc and clang, building both the qt gui and the command
line daemon, and the tests run clean as well. The qt gui runs, and cleanly
reindexed and caught up. I have no problems to report.
I am not doing any adjustments apart from applying the needed changes to
the include directory statements.
On 9 February 2013 16:10, Pieter Wuille <pieter.wuille@gmail•com> wrote:
>
> On 9 Feb 2013 00:50, "Gavin Andresen" <gavinandresen@gmail•com> wrote:
> > 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.
>
> #2243 should fix that, I think.
>
> --
> Pieter
>
>
> ------------------------------------------------------------------------------
> Free Next-Gen Firewall Hardware Offer
> Buy your Sophos next-gen firewall before the end March 2013
> and get the hardware for free! Learn more.
> http://p.sf.net/sfu/sophos-d2d-feb
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
[-- Attachment #2: Type: text/html, Size: 2007 bytes --]
prev parent reply other threads:[~2013-02-09 8:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-08 23:49 Gavin Andresen
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 [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=CA+i0-i-0Q9EnMJvajEfUtPf7jGa3Aw5qn0RqwMqjP4nOASsO0g@mail.gmail.com \
--to=robbak@robbak$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=pieter.wuille@gmail$(echo .)com \
/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