From: Douglas Huff <dhuff@jrbobdobbs.org>
To: Gavin Andresen <gavinandresen@gmail.com>
Cc: Bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Mac libboost_thread or thread-mt?
Date: Wed, 5 Oct 2011 13:50:21 -0500 [thread overview]
Message-ID: <CAPiTikU=9=1cyL9EQPX5Ou47UBn+Q_VqXG51RP8_47DVT3zMGw@mail.gmail.com> (raw)
In-Reply-To: <CABsx9T0PXuod3MS_B07PEOMEvKKjTtR3wAetbOkNp1HO5KFr-w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1066 bytes --]
Bad update. Macports has a couple of boost packages. Install the newer 1.46
ones.
--
Douglas Huff
On Oct 5, 2011 1:43 PM, "Gavin Andresen" <gavinandresen@gmail.com> wrote:
> I updated src/makefile.osx and doc/build-osx.txt today, assuming that
> the MacPorts versions of dependencies will be used and the -mt boost
> libraries will be used.
>
> I also modified makefile.unix and makefile.osx to auto-build
> dependencies using gcc's -MMD option.
>
> --
> --
> Gavin Andresen
>
>
------------------------------------------------------------------------------
> 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
[-- Attachment #2: Type: text/html, Size: 1541 bytes --]
next prev parent reply other threads:[~2011-10-05 19:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-04 23:40 [Bitcoin-development] Mac libboost_thread or thread-mt? Brian McQueen
2011-10-05 5:35 ` Michael Grønager
2011-10-05 14:37 ` Matt Corallo
2011-10-05 18:42 ` Gavin Andresen
2011-10-05 18:50 ` Douglas Huff [this message]
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='CAPiTikU=9=1cyL9EQPX5Ou47UBn+Q_VqXG51RP8_47DVT3zMGw@mail.gmail.com' \
--to=dhuff@jrbobdobbs.org \
--cc=Bitcoin-development@lists.sourceforge.net \
--cc=gavinandresen@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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