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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mh.in.england@gmail.com>) id 1Td0Fv-0000da-Vf
for bitcoin-development@lists.sourceforge.net;
Mon, 26 Nov 2012 15:05:56 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.219.47 as permitted sender)
client-ip=209.85.219.47; envelope-from=mh.in.england@gmail.com;
helo=mail-oa0-f47.google.com;
Received: from mail-oa0-f47.google.com ([209.85.219.47])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Td0Fv-0005EZ-6i
for bitcoin-development@lists.sourceforge.net;
Mon, 26 Nov 2012 15:05:55 +0000
Received: by mail-oa0-f47.google.com with SMTP id h1so11514376oag.34
for <bitcoin-development@lists.sourceforge.net>;
Mon, 26 Nov 2012 07:05:55 -0800 (PST)
MIME-Version: 1.0
Received: by 10.60.13.198 with SMTP id j6mr9398019oec.51.1353942354674; Mon,
26 Nov 2012 07:05:54 -0800 (PST)
Sender: mh.in.england@gmail.com
Received: by 10.76.128.139 with HTTP; Mon, 26 Nov 2012 07:05:54 -0800 (PST)
Date: Mon, 26 Nov 2012 16:05:54 +0100
X-Google-Sender-Auth: ojdEEpTy1Hh6YflBRIhRsogD0Kw
Message-ID: <CANEZrP2ior3tHm9feem9JKqg-WBOzfGqOpLVKvQ3Up_6xbk4yQ@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=e89a8ff253d218c48504cf674519
X-Spam-Score: -0.5 (/)
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
(mh.in.england[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
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
X-Headers-End: 1Td0Fv-0005EZ-6i
Subject: [Bitcoin-development] Has anyone compiled under MacOS 10.8?
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: Mon, 26 Nov 2012 15:05:56 -0000
--e89a8ff253d218c48504cf674519
Content-Type: text/plain; charset=UTF-8
It appears that something about Boost doesn't play nicely with the default
build instructions (possibly the switch to clang++?).
I will dig in eventually but for now, if anyone has a recipe that fixes
things, let me know.
--e89a8ff253d218c48504cf674519
Content-Type: text/html; charset=UTF-8
It appears that something about Boost doesn't play nicely with the default build instructions (possibly the switch to clang++?).<div><br></div><div>I will dig in eventually but for now, if anyone has a recipe that fixes things, let me know.</div>
--e89a8ff253d218c48504cf674519--
|
