From: Willem Jan Withagen <wjw@digiware.nl>
To: Alan Somers <asomers@freebsd.org>
Cc: Sage Weil <sage@newdream.net>, Mykola Golub <mgolub@mirantis.com>,
"Yan, Zheng" <ukernel@gmail.com>, Haomai Wang <haomai@xsky.com>,
Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: Compiling for FreeBSD
Date: Tue, 1 Dec 2015 19:08:52 +0100 [thread overview]
Message-ID: <565DE234.6070505@digiware.nl> (raw)
In-Reply-To: <CAOtMX2jWDOLqmjY=S9PorKeaHDgTx5WyMo8jiV3LxOS4K67dMg@mail.gmail.com>
On 1-12-2015 18:22, Alan Somers wrote:
> I did some work porting Ceph to FreeBSD, but got distracted and
> stopped about two years ago. You may find this port useful, though it
> will probably need to be updated:
>
> https://people.freebsd.org/~asomers/ports/net/ceph/
I'll chcek that one as well...
> Also, there's one major outstanding issue that I know of. It breaks
> interoperability between FreeBSD and Linux Ceph nodes. I posted a
> patch to fix it, but it doesn't look like it's been merged yet.
> http://tracker.ceph.com/issues/6636
In the issues I find:
====
Updated by Sage Weil almost 2 years ago
Status changed from New to Verified
Updated by Sage Weil almost 2 years ago
Assignee set to Noah Watkins
====
Probably left at that point because there was no presure to actually commit?
--WjW
next prev parent reply other threads:[~2015-12-01 18:09 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-29 17:44 Compiling for FreeBSD Willem Jan Withagen
2015-11-29 18:08 ` Haomai Wang
2015-11-29 18:57 ` Willem Jan Withagen
2015-11-30 3:46 ` Yan, Zheng
2015-11-30 6:58 ` Mykola Golub
2015-11-30 11:53 ` Willem Jan Withagen
2015-11-30 14:13 ` Mykola Golub
2015-11-30 14:40 ` Willem Jan Withagen
2015-11-30 16:04 ` Willem Jan Withagen
2015-11-30 16:20 ` Gregory Farnum
2015-12-01 9:42 ` Willem Jan Withagen
2015-12-01 12:22 ` Mykola Golub
2015-12-01 12:44 ` Willem Jan Withagen
2015-11-30 14:56 ` Willem Jan Withagen
2015-11-30 13:21 ` Sage Weil
2015-11-30 13:54 ` Willem Jan Withagen
2015-12-01 11:08 ` Willem Jan Withagen
2015-12-01 13:30 ` Sage Weil
2015-12-01 13:42 ` Willem Jan Withagen
2015-12-01 14:35 ` Sage Weil
2015-12-01 16:24 ` Willem Jan Withagen
2015-12-01 17:22 ` Alan Somers
2015-12-01 18:08 ` Willem Jan Withagen [this message]
2015-12-01 18:21 ` Alan Somers
2015-12-01 18:31 ` Willem Jan Withagen
2015-12-01 18:36 ` Sage Weil
2015-12-01 18:43 ` Willem Jan Withagen
2015-12-02 14:13 ` Yan, Zheng
2015-12-02 20:52 ` Willem Jan Withagen
2015-12-03 0:27 ` Yan, Zheng
2015-12-04 18:30 ` Willem Jan Withagen
2015-12-04 18:44 ` Gregory Farnum
2015-12-04 20:11 ` Willem Jan Withagen
2015-12-08 9:59 ` Willem Jan Withagen
2015-12-08 10:04 ` Willem Jan Withagen
2015-12-08 12:36 ` Mykola Golub
2015-12-08 15:59 ` Willem Jan Withagen
2015-12-01 18:51 ` Willem Jan Withagen
2015-12-02 21:10 ` Willem Jan Withagen
2015-12-02 22:47 ` Compiling for FreeBSD, missing rbd Willem Jan Withagen
2015-12-03 12:34 ` Mykola Golub
2015-12-03 13:27 ` Willem Jan Withagen
2015-12-03 9:50 ` Compiling for FreeBSD, runtimes for seperate tests Willem Jan Withagen
2015-12-03 14:12 ` Willem Jan Withagen
2015-12-03 21:06 ` Gregory Farnum
2015-12-05 12:56 ` Compiling for FreeBSD, Clang refuses to compile a test Willem Jan Withagen
2015-12-05 13:02 ` Xinze Chi (信泽)
2015-12-07 21:44 ` Willem Jan Withagen
2015-12-07 22:19 ` Michal Jarzabek
2015-12-08 0:29 ` Willem Jan Withagen
2015-12-08 8:48 ` Willem Jan Withagen
2016-01-16 12:56 ` Compiling for FreeBSD Willem Jan Withagen
2015-12-10 15:03 ` Compiling for FreeBSD, trouble in buffer.c Willem Jan Withagen
2015-12-11 9:56 ` Willem Jan Withagen
2016-01-15 10:52 ` Compiling for FreeBSD, Bluestore requires AIO Willem Jan Withagen
2016-01-15 11:21 ` Willem Jan Withagen
2016-01-15 17:30 ` Sage Weil
2016-01-15 18:34 ` Willem Jan Withagen
2016-01-18 9:54 ` Mykola Golub
2016-01-18 10:05 ` Willem Jan Withagen
2016-05-28 0:15 ` Compiling for FreeBSD Willem Jan Withagen
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=565DE234.6070505@digiware.nl \
--to=wjw@digiware.nl \
--cc=asomers@freebsd.org \
--cc=ceph-devel@vger.kernel.org \
--cc=haomai@xsky.com \
--cc=mgolub@mirantis.com \
--cc=sage@newdream.net \
--cc=ukernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.