From: "Luke-Jr" <luke@dashjr•org>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] 0.5 release updated
Date: Fri, 28 Oct 2011 19:56:01 -0400 [thread overview]
Message-ID: <201110281956.04246.luke@dashjr.org> (raw)
In-Reply-To: <CABsx9T3Csb5qKTeEWoA_1_e0s0OnXFjxVpw2EV0RP+6hATeDrA@mail.gmail.com>
On Friday, October 28, 2011 2:33:44 PM Gavin Andresen wrote:
> Windows builds are being difficult; we need a gcc expert to help debug
> the 'gitian' cross-compile (see
> https://github.com/bitcoin/bitcoin/pull/587 ).
This is an Ubuntu issue. Can't gitian use something else?
> I think it'd be spiffy to have a .pro file to compile bitcoind;
> maintaining N different makefiles is annoying and error-prone.
Better would be a GUI=0/1 option to the bitcoin-qt.pro until a nicer (ideally
automake/autoconf) system is implemented...
next prev parent reply other threads:[~2011-10-28 23:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-28 18:33 Gavin Andresen
2011-10-28 23:56 ` Luke-Jr [this message]
2011-10-29 8:09 ` John Smith
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=201110281956.04246.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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