public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: "Luke-Jr" <luke@dashjr.org>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Tentitive port for FreeBSD
Date: Sat, 25 May 2013 04:03:43 +0000	[thread overview]
Message-ID: <201305250403.45062.luke@dashjr.org> (raw)
In-Reply-To: <CA+i0-i-f7MDq5g4jukm-ME-3aWa=_2u_hLhaYk9=kZ_zkJLkgA@mail.gmail.com>

On Saturday, May 25, 2013 3:36:46 AM Robert Backhaus wrote:
> Here is the link to the FreeBSD build system 'port' that I am planning to
> get committed when 0.8.2 is released. Any comments appreciated.
> 
> The Makefile mostly just applies the users request for GIU/QR/UPNP. The
> major change is using the external port for leveldb. The files directory
> contains 5 patches - 2 that add boost-crypto to LIBS because we still need
> that until boost is updated, one that patches the build to use that
> external leveldb, and 2 minor fixes that are needed to build. I have got
> branches ready for pullreqs on those minor fixes - I'll double check them
> and make pullreqs this evening.
> 
> Again, any comments very welcome.

Would be nice if you could help test (and use?) the pull request for system 
LevelDB support: https://github.com/bitcoin/bitcoin/pull/2241
Note that you should be careful to tie your port to the specific LevelDB 
version bundled, to avoid any risk of unexpected hardforking bugs or fixes in 
upstream LevelDB.

For the other patches, please try to find a portable solution (if they aren't 
already) and open pull requests on github.

Thanks,

Luke



      reply	other threads:[~2013-05-25  4:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-25  3:36 [Bitcoin-development] Tentitive port for FreeBSD Robert Backhaus
2013-05-25  4:03 ` Luke-Jr [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=201305250403.45062.luke@dashjr.org \
    --to=luke@dashjr.org \
    --cc=bitcoin-development@lists.sourceforge.net \
    /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