public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Douglas Huff <dhuff@jrbobdobbs.org>
To: Gavin Andresen <gavinandresen@gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Please help sanity test: Linux/Windows 0.5.0rc2 binaries
Date: Fri, 4 Nov 2011 16:35:05 -0500	[thread overview]
Message-ID: <7C8BD633-5F93-457B-93EC-6E72B09A5D17@jrbobdobbs.org> (raw)
In-Reply-To: <CABsx9T0wzyCJBTZz=UqX-gXLEaM6krgZeVqhN5089WbvCLjTJA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 847 bytes --]

What's wrong with the mac build? I just built on 10.7 without any issues.

-- 
Douglas Huff

On Nov 4, 2011, at 4:29 PM, Gavin Andresen wrote:

> If you wonder where the bitcoin-0.5.0rc2-linux.tar.gz went...
> 
> I removed it because it is not sane (we need to teach the Qt build to
> statically link dependencies).
> 
> Once the Mac and Linux deployment issues are fixed, expect a release
> candidate 3...
> 
> -- 
> --
> Gavin Andresen
> 
> ------------------------------------------------------------------------------
> RSA(R) Conference 2012
> Save $700 by Nov 18
> Register now
> http://p.sf.net/sfu/rsa-sfdev2dev1
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development


[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

      reply	other threads:[~2011-11-04 21:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-04 18:08 [Bitcoin-development] Please help sanity test: Linux/Windows 0.5.0rc2 binaries Gavin Andresen
2011-11-04 21:29 ` Gavin Andresen
2011-11-04 21:35   ` Douglas Huff [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=7C8BD633-5F93-457B-93EC-6E72B09A5D17@jrbobdobbs.org \
    --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