blob: a80edfa6f1c7f2ca694ffdb5d9edd672fc2d43f4 (
plain)
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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <bitcoin-list@bluematt.me>) id 1RBSxd-0006Gi-CL
for Bitcoin-development@lists.sourceforge.net;
Wed, 05 Oct 2011 15:00:41 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of bluematt.me
designates 173.246.101.161 as permitted sender)
client-ip=173.246.101.161;
envelope-from=bitcoin-list@bluematt.me; helo=mail.bluematt.me;
Received: from vps.bluematt.me ([173.246.101.161] helo=mail.bluematt.me)
by sog-mx-2.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
id 1RBSxZ-0007wA-Dx for Bitcoin-development@lists.sourceforge.net;
Wed, 05 Oct 2011 15:00:41 +0000
Received: from [152.23.41.89] (MainCampusMid00342.1Xwireless.unc.edu
[152.23.41.89])
by mail.bluematt.me (Postfix) with ESMTPSA id 7F131F05;
Wed, 5 Oct 2011 16:59:53 +0200 (CEST)
From: Matt Corallo <bitcoin-list@bluematt.me>
To: Brian McQueen <mcqueenorama@gmail.com>
In-Reply-To: <CAPfzCrQapXWj_qVRffi5Tnr6_e3_0NEXjGnusHiSOkE-RJ5KLw@mail.gmail.com>
References: <CAPfzCrQapXWj_qVRffi5Tnr6_e3_0NEXjGnusHiSOkE-RJ5KLw@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Date: Wed, 05 Oct 2011 10:37:55 -0400
Message-ID: <1317825475.3047.3.camel@BMThinkPad.lan.bluematt.me>
Mime-Version: 1.0
X-Mailer: Evolution 2.32.2
Content-Transfer-Encoding: 7bit
X-Spam-Score: -2.0 (--)
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 SPF_PASS SPF: sender matches SPF record
-0.5 RP_MATCHES_RCVD Envelope sender domain matches handover relay
domain
X-Headers-End: 1RBSxZ-0007wA-Dx
Cc: Bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Mac libboost_thread or thread-mt?
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: Wed, 05 Oct 2011 15:00:41 -0000
On Tue, 2011-10-04 at 16:40 -0700, Brian McQueen wrote:
> I installed boost via the mac ports. Its got lobboost_thread-mt, but
> it doesn't have libboost_thread.a. Should I modify the makefile or get
> a different version of boost?
>
(from
http://stackoverflow.com/questions/2293962/boost-libraries-in-multithreading-aware-mode)
The -mt suffix means built in multithreading aware mode (what this means
for a threading library I have no idea), however that suffix was removed
from Linux and Mac builds in 1.42. If you are linking against 1.42+ on
Linux/Mac, adding/removing the -mt suffix means nothing AFAICT.
Matt
|
