From: Willem Jan Withagen <wjw@digiware.nl>
To: Gregory Farnum <gfarnum@redhat.com>
Cc: Mykola Golub <mgolub@mirantis.com>,
"ceph-devel@vger.kernel.org >> Ceph Development"
<ceph-devel@vger.kernel.org>
Subject: Re: Compiling for FreeBSD
Date: Tue, 1 Dec 2015 10:42:57 +0100 [thread overview]
Message-ID: <565D6BA1.1020300@digiware.nl> (raw)
In-Reply-To: <CAJ4mKGb0FZ=P5rzCOhDsh2Z2BiPa4hXav_QXTipZB3x0fQa0=A@mail.gmail.com>
On 30-11-2015 17:20, Gregory Farnum wrote:
>> Installed the results:
>> gmake install
>>
>> And looked at what it delivered:
>> zfs diff <fs-en>
>>
>> And I have to be honest that I'm not really enjoying all the ceph-test
>> stuff in my /usr/local/bin....
>> Would prefer it to go into something like:
>> /usr/local/libexec/ceph/tests
>> or
>> /usr/local/share/ceph/tests
>>
>> Not sure if this is possible without disrupting the automated testing.
>
> As far as I know, none of what we do upstream relies on "make install"
> and I don't think it's very well-maintained. You could make some
> changes and submit a PR — if it does break something it should show up
> in the autobuilder bot.
Well got that all compiled and installed.
Fixed a startup problem in /usr/local/bin/ceph's python with an unknown
error value. So that looks to run.
Created a config, and acompanying directories.
And now for the real work:
Run:
ceph-mon -i freetest -d --debug_mon 10 --cluster digiceph -c
/etc/ceph/ceph.conf
Which bombs out with:
2015-12-01 10:32:41.877243 804015000 0 ceph version 10.0.0-677-gd704c54
(d704c54b7923ef7265fa27018e9411d8deb463b3), process (unknown), pid 93896
2015-12-01 10:32:41.879339 804015000 -1 load
dlopen(/usr/local/lib/ceph/erasure-code/libec_jerasure.so):
/usr/local/lib/ceph/erasure-code/libec_jerasure.so: Undefined symbol
"ceph_arch_neon"
So of to find where ceph_arch_neon is, and why it seems not defined.
Perhaps as simple as loading the shared libs??
--WjW
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-12-01 9:43 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 [this message]
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
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=565D6BA1.1020300@digiware.nl \
--to=wjw@digiware.nl \
--cc=ceph-devel@vger.kernel.org \
--cc=gfarnum@redhat.com \
--cc=mgolub@mirantis.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