From: Daniel Gryniewicz <dang@redhat.com>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: Matt Benjamin <mbenjamin@redhat.com>,
"Adam C. Emerson" <aemerson@redhat.com>,
ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: cmake
Date: Fri, 4 Dec 2015 09:15:58 -0500 [thread overview]
Message-ID: <CAL-2WbEdQDHO-FY_Ns0vigWv1S0gMUk8X1NSQKaXH3kB2Lrn5w@mail.gmail.com> (raw)
In-Reply-To: <20151204015942.19951132@lembas.zaitcev.lan>
On Fri, Dec 4, 2015 at 3:59 AM, Pete Zaitcev <zaitcev@redhat.com> wrote:
> On Thu, 3 Dec 2015 19:26:52 -0500 (EST)
> Matt Benjamin <mbenjamin@redhat.com> wrote:
>
>> Could you share the branch you are trying to build? (ceph/wip-5073 would not appear to be it.)
>
> It's the trunk with a few of my insignificant cleanups.
>
> But I found a fix: deleting the CMakeFiles/ and CMakeCache.txt let
> it run. Thanks again for the tip about the separate build directory.
>
FWIW, many cmake issues can be fixed by nuking the cmake generated
files. This is one of the big advantages to a separate build dir,
since the simplest way to do this is to nuke the build dir.
Daniel
next prev parent reply other threads:[~2015-12-04 14:16 UTC|newest]
Thread overview: 35+ 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 ` cmake Matt Benjamin
2015-12-04 8:59 ` cmake Pete Zaitcev
2015-12-04 14:15 ` Daniel Gryniewicz [this message]
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 --
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
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
2009-04-01 17:35 cmake Shane Dixon
2009-04-02 5:30 ` cmake Jeremy Lainé
2009-04-02 16:44 ` cmake Otavio Salvador
2009-04-02 18:07 ` cmake Koen Kooi
2009-04-02 17:07 ` cmake Robert Schuster
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=CAL-2WbEdQDHO-FY_Ns0vigWv1S0gMUk8X1NSQKaXH3kB2Lrn5w@mail.gmail.com \
--to=dang@redhat.com \
--cc=aemerson@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=mbenjamin@redhat.com \
--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 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.