From: Willem Jan Withagen <wjw@digiware.nl>
To: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: FreeBSD Building and Testing
Date: Tue, 22 Dec 2015 00:40:35 +0100 [thread overview]
Message-ID: <56788DF3.3090205@digiware.nl> (raw)
In-Reply-To: <5676D2D9.5010600@digiware.nl>
On 20-12-2015 17:10, Willem Jan Withagen wrote:
> Hi,
>
> Most of the Ceph is getting there in the most crude and rough state.
> So beneath is a status update on what is not working for me jet.
> Further:
> A) unittest_erasure_code_plugin failes on the fact that there is a
> different error code returned when dlopen-ing a non existent library.
> load dlopen(.libs/libec_invalid.so): Cannot open
> ".libs/libec_invalid.so"load dlsym(.libs/libec_missing_version.so, _
> _erasure_code_init): Undefined symbol
> "__erasure_code_init"test/erasure-code/TestErasureCodePlugin.cc:88: Failure
> Value of: instance.factory("missing_version", g_conf->erasure_code_dir,
> profile, &erasure_code, &cerr)
> Actual: -2
> Expected: -18
EXDEV is actually 18, so that part is correct.
But EXDEV is cross-device link error.
Where as the actual answer: -2 is factual correct:
#define ENOENT 2 /* No such file or directory */
So why is the test for EXDEV instead of ENOENT?
Could be a typical Linux <> FreeBSD thingy.
--WjW
prev parent reply other threads:[~2015-12-21 23:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-20 16:10 FreeBSD Building and Testing Willem Jan Withagen
2015-12-21 0:45 ` Xinze Chi (信泽)
[not found] ` <CANE=7sU9QPH2uUS8A4xhPQ1j+jR6Fi88=PVvLRGEhzt2cmOceg@mail.gmail.com>
2015-12-21 1:16 ` Fwd: " Xinze Chi (信泽)
2015-12-21 20:14 ` Willem Jan Withagen
2015-12-28 16:53 ` Willem Jan Withagen
2016-01-05 18:23 ` Gregory Farnum
2016-01-06 10:21 ` Willem Jan Withagen
2016-01-06 7:51 ` Mykola Golub
2016-01-06 10:16 ` Willem Jan Withagen
2016-01-06 12:41 ` Willem Jan Withagen
2015-12-21 23:40 ` Willem Jan Withagen [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=56788DF3.3090205@digiware.nl \
--to=wjw@digiware.nl \
--cc=ceph-devel@vger.kernel.org \
/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.