From: Aurelien Degremont <aurelien.degremont@cea.fr>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] Cannot easily build from master source anymore
Date: Thu, 02 Dec 2010 15:22:58 +0100 [thread overview]
Message-ID: <4CF7ABC2.3000400@cea.fr> (raw)
In-Reply-To: <DA432BB3-C1EC-433B-8936-923B98D7C446@oracle.com>
Andreas Dilger a ?crit :
> On 2010-12-01, at 12:45, James Simmons wrote:
>>> I noticed there was a refactor for packaging and versioning in Lustre
>>> prime master branch.
>>> Unfortunately, we cannot simply do anymore
>>>
>>> git clone ...
>>> sh ./autogen.sh
>>> ./configure ..
>>> make
>>>
>>> to build lustre source
>>>
>>> What's the trick now ?
>>> Maybe it could be useful to update Wiki page:
>>> http://wiki.lustre.org/index.php/Building_Lustre_Code
>> Let me guess.
>>
>> checking for stdint.h... yes
>> checking for unistd.h... yes
>> checking whether to configure just enough for make dist... no
>> checking for buildid... configure: error: most recent tag found: v2_0_0
>> does not match current version 2.0.56.
>> make: *** No rule to make target `rpms'. Stop.
>> make: *** No rule to make target `rpms'. Stop.
>
> My recollection from Brian's previous postings is that this is somehow related to an old "git" version being used.
We are using either git v1.5.5.6. Is this so old?
> That said, I'd be happy to remove this as a requirement, and just stick with the version if there is a mismatch, printing only a warning if the git version is too old.
I think it will be a good idea
--
Aurelien Degremont
CEA
next prev parent reply other threads:[~2010-12-02 14:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-01 10:16 [Lustre-devel] Cannot easily build from master source anymore Aurelien Degremont
2010-12-01 19:45 ` James Simmons
2010-12-01 22:54 ` Andreas Dilger
2010-12-02 14:22 ` Aurelien Degremont [this message]
2010-12-14 16:57 ` Brian J. Murrell
2010-12-16 11:19 ` Aurelien Degremont
2010-12-16 18:53 ` Christopher J. Morrone
2010-12-17 11:02 ` Aurelien Degremont
2010-12-16 16:56 ` Robert Read
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=4CF7ABC2.3000400@cea.fr \
--to=aurelien.degremont@cea.fr \
--cc=lustre-devel@lists.lustre.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.