From: Loic Dachary <loic@dachary.org>
To: kernel neophyte <neophyte.hacker001@gmail.com>,
"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: Cehp - tip - build break ?
Date: Sun, 05 Apr 2015 12:07:48 +0200 [thread overview]
Message-ID: <55210974.2010009@dachary.org> (raw)
In-Reply-To: <CAFkUHxdMwZDR7=Z1XeyF9zrNzV2e1U+OWcsRpVusi_GhzCPN1A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 942 bytes --]
Hi,
My guess is that it's because the gmock directory has been replaced by a gmock submodule and git pull won't be enough to do the right thing. The simplest workaround is to git clone a fresh copy. Or you can try ./autogen.sh which should also do what's necessary.
Cheers
On 05/04/2015 07:07, kernel neophyte wrote:
> Hi,
>
> I am seeing build break in ceph master.
>
> 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
>
>
> Am I missing anything obvious ?
>
>
> -Neo
> --
> 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
>
--
Loïc Dachary, Artisan Logiciel Libre
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2015-04-05 10:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-05 5:07 Cehp - tip - build break ? kernel neophyte
2015-04-05 10:07 ` Loic Dachary [this message]
2015-04-06 16:04 ` kernel neophyte
2015-04-06 16:07 ` Sage Weil
2015-04-06 16:09 ` kernel neophyte
2015-04-06 18:10 ` Gregory Farnum
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=55210974.2010009@dachary.org \
--to=loic@dachary.org \
--cc=ceph-devel@vger.kernel.org \
--cc=neophyte.hacker001@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.