https://jira.whamcloud.com This file is an XML representation of an issue en-us 9.4.14 940014 05-12-2023 https://jira.whamcloud.com/browse/LUDOC-124 Lustre Documentation <p>So I use the basic instructions on the wiki for building locally. So far it has worked well for me until...</p> <p>I needed kernel debuginfo rpms built and ZFS. </p> <p>These rpms greatly simplify debugging and profiling. Several common tool utilize this data. </p> <p>Our build server via the lbuild procedure we get 30 some odd packages including zfs and most of the debuginfo you could want.</p> <p>Also <a href="https://jira.whamcloud.com/browse/LU-2662" title="Build: pthread build issue" class="issue-link" data-issue-key="LU-2662"><del>LU-2662</del></a> shows that building local and lbuild are two different things. </p> <p>In general it would be nice to have lbuild documentation. </p> LUDOC-124

A question of kernel debuginfo rpms

Improvement Minor Open Unresolved Lustre Manual Triage Keith Mannthey Wed, 13 Feb 2013 22:09:56 +0000 Thu, 15 Sep 2016 14:44:00 +0000 0 3 <p>I would like to reframe this as basic Lbuild instructions are needed in a public spot. </p> <p>Lbuild is hard to use but is the proper way to build lustre. As an opensource project Building the code is an important part of the life cycle. </p> <p>reassigning to Jodi so that it goes through triage</p> <p>I noticed with Lustre 2.5 "make rpms" is making a larger set of packages. </p> <p>I would argue that lbuild is Intel's historic and obsolete method for building. It is by no means the <em>proper</em> way way of building anything. There are many things that it does that a proper build and packaging system should not.</p> <p>For instance, rather than properly expressing and testing rpm build dependencies, lbuild invents its own way to install dependencies, and manually cpio unpacks binary rpms. That is just horrible. No one should follow that example.</p> <p>I entirely agree that there should be good build documentation, but we should document <em>good</em> procedures, not lbuild's methods.</p> <p>It has been about a year so I don't think Lbuild is going into the Lustre Manual in time soon. In the last year I have learn to use lbuild a bit and I agree lbuild is it own 1 off thing. </p> <p>The manual reciently received an update on the Building Source section:</p> <p><a href="http://build.whamcloud.com/job/lustre-manual/lastSuccessfulBuild/artifact/lustre_manual.xhtml#installinglustrefromsourcecode" class="external-link" target="_blank" rel="nofollow noopener">http://build.whamcloud.com/job/lustre-manual/lastSuccessfulBuild/artifact/lustre_manual.xhtml#installinglustrefromsourcecode</a></p> <p>I believe the source material here is the wiki page - neither of which describe using lbuild.</p> <p>My preference is to remove 'document lbuild' from this ticket and remain focused on enhancing the documentation to show how to get debug info from the 'make rpm' route.</p> <p>It kind of looks like the entire chapter needs work. Rather than clog this ticket, I started <a href="https://jira.whamcloud.com/browse/LUDOC-224" title="Chapter 30 partial review" class="issue-link" data-issue-key="LUDOC-224"><del>LUDOC-224</del></a> with some review comments.</p> Development Rank 1|hzvj3r: Rank (Obsolete) 6809