From: Matt Benjamin <mbenjamin@redhat.com>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: "Adam C. Emerson" <aemerson@redhat.com>, ceph-devel@vger.kernel.org
Subject: Re: cmake
Date: Thu, 3 Dec 2015 19:26:52 -0500 (EST) [thread overview]
Message-ID: <295720458.28620860.1449188812348.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20151203170347.33867061@lembas.zaitcev.lan>
Pete,
Could you share the branch you are trying to build? (ceph/wip-5073 would not appear to be it.)
Matt
----- Original Message -----
> From: "Pete Zaitcev" <zaitcev@redhat.com>
> To: "Adam C. Emerson" <aemerson@redhat.com>
> Cc: ceph-devel@vger.kernel.org
> Sent: Thursday, December 3, 2015 7:03:47 PM
> Subject: Re: cmake
>
> On Thu, 3 Dec 2015 17:30:21 -0500
> "Adam C. Emerson" <aemerson@redhat.com> wrote:
>
> > On 03/12/2015, Pete Zaitcev wrote:
>
> > > I'm trying to run cmake, in order to make sure my patches do not break it
> > > (in particular WIP 5073 added source files). Result looks like this:
> > >
> > > [zaitcev@lembas ceph-tip]$ cmake src
> >
> > I believe the problem is 'cmake src'
>
> Thanks for the tip about the separate build directory and the top-level
> CMakeLists.txt. However, it still fails like this:
>
> [zaitcev@lembas build]$ cmake ..
> CMake Error at CMakeLists.txt:1 (include):
> include could not find load file:
>
> GetGitRevisionDescription
> ...................
>
> Do you know by any chance where it gets that include? Also, what's
> your cmake --version?
>
> Greetings,
> -- Pete
> --
> 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
>
--
--
Matt Benjamin
Red Hat, Inc.
315 West Huron Street, Suite 140A
Ann Arbor, Michigan 48103
http://www.redhat.com/en/technologies/storage
tel. 734-707-0660
fax. 734-769-8938
cel. 734-216-5309
next prev parent reply other threads:[~2015-12-04 0:26 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-03 22:24 cmake Pete Zaitcev
2015-12-03 22:30 ` cmake Adam C. Emerson
2015-12-04 0:03 ` cmake Pete Zaitcev
2015-12-04 0:26 ` Matt Benjamin [this message]
2015-12-04 8:59 ` cmake Pete Zaitcev
2015-12-04 14:15 ` cmake Daniel Gryniewicz
2015-12-03 22:30 ` cmake Matt Benjamin
2015-12-03 22:31 ` cmake Matt Benjamin
-- strict thread matches above, loose matches on Subject: below --
2015-12-16 17:33 cmake Sage Weil
2015-12-16 17:53 ` cmake Loic Dachary
2015-12-16 18:28 ` cmake John Spray
2015-12-16 19:36 ` cmake Sage Weil
2015-12-16 18:45 ` cmake Yehuda Sadeh-Weinraub
2015-12-16 19:06 ` cmake Matt Benjamin
2015-12-16 19:38 ` cmake Sage Weil
2015-12-16 23:47 ` cmake Willem Jan Withagen
2015-12-16 23:36 ` cmake Willem Jan Withagen
2016-06-27 17:50 cmake Sage Weil
2016-06-28 7:35 ` cmake Willem Jan Withagen
2016-06-28 8:41 ` cmake Willem Jan Withagen
2016-06-28 8:57 ` cmake Willem Jan Withagen
2016-06-28 13:42 ` cmake Sage Weil
2016-06-28 16:05 ` cmake Willem Jan Withagen
2016-06-29 16:51 ` cmake Willem Jan Withagen
2016-06-30 19:03 ` cmake Willem Jan Withagen
2016-07-05 19:09 ` cmake Willem Jan Withagen
2016-06-28 20:28 ` cmake Casey Bodley
2016-06-28 21:43 ` cmake Mark Nelson
2016-07-04 9:05 ` cmake Willem Jan Withagen
2016-07-04 10:37 ` cmake Brad Hubbard
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=295720458.28620860.1449188812348.JavaMail.zimbra@redhat.com \
--to=mbenjamin@redhat.com \
--cc=aemerson@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=zaitcev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox