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/LU-2878 Lustre <p>A recent set of Livermore changes to the build system has broken "make install". "make all" still works. For some reason, ldiskfs is failing a dependency check:</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"> *** Missing ldiskfs symbols. Ensure you have built ldiskfs: *** - /home/build/lustre-release/ldiskfs/ldiskfs/Module.symvers </pre> </div></div> <p>Either a- this needs to be fixed so developers who don't want to have to build RPM's every time can continue to use "make install", or b- "make install" should be removed.</p> LU-2878

"make install" Broken

Bug Critical Resolved Won't Do WC Triage Doug Oucharek Tue, 26 Feb 2013 22:50:19 +0000 Tue, 14 Dec 2021 22:58:51 +0000 Tue, 14 Dec 2021 22:58:51 +0000 Lustre 2.8.0 Lustre 2.9.0 0 4 <p><tt>make install</tt> can't be removed as that is used by <tt>make rpms</tt> (indirectly given that the RPM specfile uses <tt>make install</tt>).</p> <p>The curious question becomes, why does <tt>make install</tt> work in the building of RPMs but not when used otherwise?</p> <p>I don't know any developers who use make install, everybody I know runs their tests out of their build trees directly.</p> <p>I was using "make install" because with LNet, I have to use multiple VM's running a real file system so I can monitor the LNet packets. When I started with Whamcloud, I could not find any good documentation how how to build and run stuff directly out of the build tree. Does such documentation exist?</p> <p>So, my developer instincts are to run "make install" which is fairly standard for development. And, until recently, this worked leading me to believe this is the way to do things.</p> <p>I understand "make rpms' works but that seems to come with a lot of overhead for development purposes. However, with "make install" broken, I have resorted to "make rpms" and then load the RPM's after they are built.</p> <p>So, where is the documentation on how to do this directly from build tree? Is that approach only good for running the test suite (which does not cover LNet very well)?</p> <p>For me, the rpms created via "make rpms" under RHEL 7.2 don't work. That is another bug I will be opening. However, with rpms not working, it would be nice to fall back to "make install" to get things done. But "make install" is still broken. I am increasing the priority of this ticket.</p> Development Rank 1|hzvjxz: Rank (Obsolete) 6953 Severity