[LU-2878] "make install" Broken Created: 26/Feb/13 Updated: 14/Dec/21 Resolved: 14/Dec/21 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | Lustre 2.8.0, Lustre 2.9.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Critical |
| Reporter: | Doug Oucharek (Inactive) | Assignee: | WC Triage |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Severity: | 3 |
| Rank (Obsolete): | 6953 |
| Description |
|
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: *** Missing ldiskfs symbols. Ensure you have built ldiskfs: *** - /home/build/lustre-release/ldiskfs/ldiskfs/Module.symvers 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. |
| Comments |
| Comment by Brian Murrell (Inactive) [ 27/Feb/13 ] |
|
make install can't be removed as that is used by make rpms (indirectly given that the RPM specfile uses make install). The curious question becomes, why does make install work in the building of RPMs but not when used otherwise? |
| Comment by Oleg Drokin [ 04/Mar/13 ] |
|
I don't know any developers who use make install, everybody I know runs their tests out of their build trees directly. |
| Comment by Doug Oucharek (Inactive) [ 14/Mar/13 ] |
|
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? 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. 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. 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)? |
| Comment by Doug Oucharek (Inactive) [ 04/Oct/16 ] |
|
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. |