From: Jay Lan <jay.zen.lan@gmail.com>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] How was lustre-1.8.4.tar.gz created?
Date: Fri, 08 Oct 2010 18:16:05 -0700 [thread overview]
Message-ID: <4CAFC255.8090906@gmail.com> (raw)
There is a lustre-1.8.4.tar.gz
<http://cds.sun.com/is-bin/INTERSHOP.enfinity/WFS/CDS-CDS_SMI-Site/en_US/-/USD/VerifyItem-Start/lustre-1.8.4.tar.gz?BundledLineItemUUID=neSJ_hCyazAAAAErvoBKP45J&OrderID=z0qJ_hCyYf0AAAErAH9KP45J&ProductID=QUOJ_hCxLIwAAAEqfGgMmTUo&FileName=/lustre-1.8.4.tar.gz>
at the download site.
At the top dir, comparing to the tree you check out from
git, it does not have augogen.sh and misses the libcfs
directory completely, but it contains tree_status that
should be generated later in building.
So, how was lustre-1.8.4.tar.gz generated?
I used 'git archive v1_8_4' to populate a workarea,
and built lustre software with that. The resulting rpm
caused 2.6.18-194.3.1 kernel to crash when modprobe
lustre.ko at ib_core:rdma_node_get_transport+0x14/0x2.
However, if I built using the tar ball from the download area,
it worked great. So, what was the trick? How would I be able
to build a 1.8.4 for rhel5.5 from the git repository?
Thanks,
Jay
next reply other threads:[~2010-10-09 1:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-09 1:16 Jay Lan [this message]
2010-10-13 18:39 ` [Lustre-devel] How was lustre-1.8.4.tar.gz created? Brian J. Murrell
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=4CAFC255.8090906@gmail.com \
--to=jay.zen.lan@gmail.com \
--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.