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
Brian J. Murrell
2010-Oct-13 18:39 UTC
[Lustre-devel] How was lustre-1.8.4.tar.gz created?
On Fri, 2010-10-08 at 18:16 -0700, Jay Lan wrote:> So, how was lustre-1.8.4.tar.gz generated?[ assuming you have a git clone of prime ] $ git checkout 1.8.4 $ autogen.sh $ ./configure -disable-modules --disable-utils --disable-liblustre --disable-tests --disable-doc $ make dist That''s it. b. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part Url : http://lists.lustre.org/pipermail/lustre-devel/attachments/20101013/7f59dfc6/attachment.bin