From: Eric Mockensturm <emm10@psu•edu>
To: Brian McQueen <mcqueenorama@gmail•com>
Cc: Bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Mac libboost_thread or thread-mt?
Date: Thu, 6 Oct 2011 19:35:23 -0400 [thread overview]
Message-ID: <FC56C4D3-F4FE-4CDA-BC31-2C382AAB0973@psu.edu> (raw)
In-Reply-To: <CAPfzCrRhRr_2AfwiR+NGSbRkBQ=n1tN=YLhVp3FOXJaSWFrk6Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3285 bytes --]
Brian,
Yea, I vaguely remember going through all this when I first tried building it. If I recall you can statically link libz into crypto when you compile crypto. Or something like that. Maybe the default MacPorts crypto install does not do this.
Eric
--
Eric Mockensturm, Ph.D.
Associate Professor
Department of Mechanical & Nuclear Engineering
The Pennsylvania State University
157C Hammond Building
University Park, PA 16802
Email: emm10@psu•edu
Phone/Fax: (814) 863-0736/7222
On Oct 6, 2011, at 6:18 PM, Brian McQueen wrote:
> I added -mt and it compiles, but here is a surprise. I had to add
> libz.a to the makefile.osx. Sounds odd! Its coming from the crypto
> libs.
>
> On Wed, Oct 5, 2011 at 11:50 AM, Douglas Huff <dhuff@jrbobdobbs•org> wrote:
>> 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
>>
>> ------------------------------------------------------------------------------
>> 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
>>
>>
>
>
>
> --
> 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
[-- Attachment #2: Type: text/html, Size: 8439 bytes --]
prev parent reply other threads:[~2011-10-06 23:35 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
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 [this message]
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=FC56C4D3-F4FE-4CDA-BC31-2C382AAB0973@psu.edu \
--to=emm10@psu$(echo .)edu \
--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