From: "Michael Grønager" <gronager@ceptacle•com>
To: Brian McQueen <mcqueenorama@gmail•com>
Cc: Bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Mac libboost_thread or thread-mt?
Date: Wed, 5 Oct 2011 07:35:52 +0200 [thread overview]
Message-ID: <260F44BE-5DF3-4F6F-A3ED-A408E5B7A7B5@ceptacle.com> (raw)
In-Reply-To: <CAPfzCrQapXWj_qVRffi5Tnr6_e3_0NEXjGnusHiSOkE-RJ5KLw@mail.gmail.com>
Hi Brian,
Had a similar issue the other day with my cmake btc buildsystem - I just changed the name to -mt, I think that is th way to go.
Cheers,
Michael
On 05/10/2011, at 01:40, 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?
>
> --
> Make a Small Loan, Make a Big Difference - Check out Kiva.org to Learn How!
>
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure contains a
> definitive record of customers, application performance, security
> threats, fraudulent activity and more. Splunk takes this data and makes
> sense of it. Business sense. IT sense. Common sense.
> http://p.sf.net/sfu/splunk-d2dcopy1
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
next prev parent reply other threads:[~2011-10-05 5:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-04 23:40 Brian McQueen
2011-10-05 5:35 ` Michael Grønager [this message]
2011-10-05 14:37 ` Matt Corallo
2011-10-05 18:42 ` Gavin Andresen
2011-10-05 18:50 ` Douglas Huff
2011-10-06 22:18 ` Brian McQueen
2011-10-06 23:35 ` Eric Mockensturm
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=260F44BE-5DF3-4F6F-A3ED-A408E5B7A7B5@ceptacle.com \
--to=gronager@ceptacle$(echo .)com \
--cc=Bitcoin-development@lists$(echo .)sourceforge.net \
--cc=mcqueenorama@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