From: Mark Kirkwood <mark.kirkwood@catalyst.net.nz>
To: Gregory Farnum <greg@gregs42.com>, Josh Durgin <jdurgin@redhat.com>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: Ceph master - build broken unless --enable-debug specified
Date: Fri, 17 Apr 2015 12:34:20 +1200 [thread overview]
Message-ID: <5530550C.7080808@catalyst.net.nz> (raw)
In-Reply-To: <CAC6JEv_uRE=UfVQpZ+NtzX2nCpMthienXuTdNHtynDK6oQ4G1A@mail.gmail.com>
On 17/04/15 12:27, Gregory Farnum wrote:
> On Sat, Apr 11, 2015 at 8:42 PM, Mark Kirkwood
> <mark.kirkwood@catalyst.net.nz> wrote:
>> Hi,
>>
>> Building without --enable-debug produces:
>>
>> ceph_fuse.cc: In member function ‘virtual void* main(int, const char**,
>> const char**)::RemountTest::entry()’:
>> ceph_fuse.cc:146:15: warning: ignoring return value of ‘int system(const
>> char*)’, declared with attribute warn_unused_result [-Wunused-result]
>> system(buf);
>> ^
>> CXX ceph_osd.o
>> CXX ceph_mds.o
>> make[3]: *** No rule to make target '../src/gmock/lib/libgmock_main.la',
>> needed by 'unittest_librbd'. Stop.
>> make[3]: *** Waiting for unfinished jobs....
>> CXX test/erasure-code/ceph_erasure_code_non_regression.o
>> make[3]: Leaving directory '/home/markir/develop/c/ceph/src'
>> Makefile:20716: recipe for target 'all-recursive' failed
>> make[2]: *** [all-recursive] Error 1
>> make[2]: Leaving directory '/home/markir/develop/c/ceph/src'
>> Makefile:8977: recipe for target 'all' failed
>> make[1]: *** [all] Error 2
>> make[1]: Leaving directory '/home/markir/develop/c/ceph/src'
>> Makefile:467: recipe for target 'all-recursive' failed
>> make: *** [all-recursive] Error 1
>>
>>
>> Adding in --enable-debug gives a successful build.
>>
>> This is on Ubuntu 14.10 64 bit, and the build procedure is:
>>
>> $ git pull
>> $ git submodule update --init
>> $ ./autogen.sh
>> $ ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var \
>> [--with-debug \ ]
>> --with-nss \
>> --with-radosgw \
>> --with-librocksdb-static=check \
>>
>> $ make [ -j4 ]
>
> Yep, looks like the unittest_librbd binary is in the noinst_PROGRAMS
> target (whatever that is) rather than the check_PROGRAMS target.
> Changing that seems to work — I pushed a branch wip-nodebug-build
> fixing it, but if you have your own fix a PR is welcome. If not I'll
> make a PR in the next couple days.
I had not looked very closely at what the exact problem was - your
analysis looks good to me, I'll leave you to file a PR :-)
Cheers
Mark
--
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
prev parent reply other threads:[~2015-04-17 0:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-12 3:42 Ceph master - build broken unless --enable-debug specified Mark Kirkwood
2015-04-17 0:27 ` Gregory Farnum
2015-04-17 0:34 ` Mark Kirkwood [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=5530550C.7080808@catalyst.net.nz \
--to=mark.kirkwood@catalyst.net.nz \
--cc=ceph-devel@vger.kernel.org \
--cc=greg@gregs42.com \
--cc=jdurgin@redhat.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.