1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <gavinandresen@gmail.com>) id 1RJrFX-0006J6-FU
for bitcoin-development@lists.sourceforge.net;
Fri, 28 Oct 2011 18:33:51 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.161.47 as permitted sender)
client-ip=209.85.161.47; envelope-from=gavinandresen@gmail.com;
helo=mail-fx0-f47.google.com;
Received: from mail-fx0-f47.google.com ([209.85.161.47])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1RJrFW-0000RN-K8
for bitcoin-development@lists.sourceforge.net;
Fri, 28 Oct 2011 18:33:51 +0000
Received: by faas16 with SMTP id s16so6185148faa.34
for <bitcoin-development@lists.sourceforge.net>;
Fri, 28 Oct 2011 11:33:44 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.61.211 with SMTP id u19mr7726748fah.29.1319826824343; Fri,
28 Oct 2011 11:33:44 -0700 (PDT)
Received: by 10.152.24.229 with HTTP; Fri, 28 Oct 2011 11:33:44 -0700 (PDT)
Date: Fri, 28 Oct 2011 14:33:44 -0400
Message-ID: <CABsx9T3Csb5qKTeEWoA_1_e0s0OnXFjxVpw2EV0RP+6hATeDrA@mail.gmail.com>
From: Gavin Andresen <gavinandresen@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: text/plain; charset=ISO-8859-1
X-Spam-Score: -1.6 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(gavinandresen[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
0.0 T_FRT_PROFILE1 BODY: ReplaceTags: Profile (1)
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
-0.0 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1RJrFW-0000RN-K8
Subject: [Bitcoin-development] 0.5 release updated
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Fri, 28 Oct 2011 18:33:51 -0000
Quick update on why there is no final 0.5 release out yet:
Short answer: because I'm really paranoid about bitcoin binary builds,
and the switch to Qt means a change in the way the builds are done.
Long answer:
Linux builds should be all set; the 'gitian' trusted build process works nicely.
Windows builds are being difficult; we need a gcc expert to help debug
the 'gitian' cross-compile (see
https://github.com/bitcoin/bitcoin/pull/587 ).
Unless somebody steps forward and says "I'll support compiling
bitcoin-qt/bitcoind with Visual Studio) I'm going to remove
src/makefile.vc and make sure the readmes say that only the mingw
toolchain is supported.
Mac builds were slightly broken for the 0.4 release (they don't run on
OSX 10.5-- you need 10.6 or greater). I'm "recompiling the world" to
hopefully fix that, and hope to have mac binaries available soon (let
me know if you can help test, especially if you have a 32-bit Intel
mac running 10.5).
On my wish list for builds (anybody want to volunteer?):
I think it'd be spiffy to have a .pro file to compile bitcoind;
maintaining N different makefiles is annoying and error-prone.
--
--
Gavin Andresen
|
