From: Thomas Mueller <thomas@chaschperli.ch>
To: ceph-devel@vger.kernel.org
Subject: Re: make with -j fails
Date: Mon, 5 Jul 2010 06:15:10 +0000 (UTC) [thread overview]
Message-ID: <i0rt9e$ao1$2@dough.gmane.org> (raw)
In-Reply-To: Pine.LNX.4.64.1007041509540.27399@cobra.newdream.net
Am Sun, 04 Jul 2010 15:10:49 -0700 schrieb Sage Weil:
> On Sun, 4 Jul 2010, Thomas Mueller wrote:
>
>> Am Fri, 02 Jul 2010 07:38:47 -0700 schrieb Sage Weil:
>>
>> > On Fri, 2 Jul 2010, Thomas Mueller wrote:
>> >> as soon as I try to use the -j option the make fails. tried with -j2
>> >> and - j8
>> >>
>> >> is it supposed to work to call make with "-j" to speedup the
>> >> compilation time?
>> >
>> > Yeah. The ceph_ver.h is autogenerated to include the git commit id,
>> > and the rules are a bit wonky. I fixed a couple problems and I think
>> > it should be working now. (I can't be sure, since for some reason I
>> > never see these errors in my environment.) Can you let me know if
>> > it's better now? You'll need to rm ceph_ver.h and make clean to be
>> > sure.
>> >
>> > Thanks!
>> > sage
>>
>> i've recreated the repo (rm -Rf && git clone && git checkout
>> origin/unstable) and ran "./autogen.sh && ./configure --without-debug
>> --without-hadoop && make -j8"
>>
>> bails aut with this (but only the first time as Gregory wrote in his
>> mail):
>
> Ok, I redid the ceph_ver.h rules again and I think I have it working,
> this time with a simpler set of dependencies. Can you let me know if it
> works for you?
>
> sage
perfect, now it compiles with -j8 in the first time!
with -j8: real 0m19.681s, user 0m54.967s, sys 0m13.045s
with -j1: real 1m32.983s, user 1m12.738s, sys 0m18.164s
- Thomas
next prev parent reply other threads:[~2010-07-05 6:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-02 7:23 make with -j fails Thomas Mueller
2010-07-02 14:38 ` Sage Weil
2010-07-04 14:14 ` Thomas Mueller
2010-07-04 22:10 ` Sage Weil
2010-07-05 6:15 ` Thomas Mueller [this message]
2010-07-02 17:04 ` 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='i0rt9e$ao1$2@dough.gmane.org' \
--to=thomas@chaschperli.ch \
--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.