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-108 Lustre <p>On master, "configure --prefix=/some/path" appears to be broken for at least libcfs.ko. I wanted to "make install" into a subdirectory in my home directory, and it failed at this point:</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java">test -z <span class="code-quote">"/bghome/morrone/local/lib"</span> || /bin/mkdir -p <span class="code-quote">"/bghome/morrone/local/lib"</span> /usr/bin/install -c -m 644 libcfsutil.a <span class="code-quote">'/bghome/morrone/local/lib'</span> ( cd <span class="code-quote">'/bghome/morrone/local/lib'</span> &amp;&amp; ranlib libcfsutil.a ) test -z <span class="code-quote">"" || /bin/mkdir -p "</span>" test -z <span class="code-quote">"/lib/modules/2.6.32-71.el6.ppc64/updates/kernel/net/lustre"</span> || /bin/mkdir -p <span class="code-quote">"/lib/modules/2.6.32-71.el6.ppc64/updates/kernel/net/lustre"</span> /usr/bin/install -c -m 644 libcfs.ko <span class="code-quote">'/lib/modules/2.6.32-71.el6.ppc64/updates/kernel/net/lustre'</span> /usr/bin/install: cannot remove `/lib/modules/2.6.32-71.el6.ppc64/updates/kernel/net/lustre/libcfs.ko': Permission denied make[4]: *** [install-modulenetDATA] Error 1 make[4]: Leaving directory `/bghome/morrone/lustre/libcfs/libcfs' make[3]: *** [install-am] Error 2 make[3]: Leaving directory `/bghome/morrone/lustre/libcfs/libcfs' make[2]: *** [install-recursive] Error 1 make[2]: Leaving directory `/bghome/morrone/lustre/libcfs/libcfs' make[1]: *** [install-recursive] Error 1 make[1]: Leaving directory `/bghome/morrone/lustre/libcfs' make: *** [install-recursive] Error 1 </pre> </div></div> <p>Notice it tried to install libcfs.ko into /lib instead of /bghome/morrone/local/lib. (I had specified --prefix=/bghome/morrone/local).</p> LU-108

configure --prefix broken for libcfs.ko on master

Bug Minor Resolved Cannot Reproduce Brian Murrell Christopher Morrone Thu, 3 Mar 2011 15:56:38 +0000 Fri, 4 Mar 2011 18:32:57 +0000 Fri, 4 Mar 2011 18:32:57 +0000 Lustre 2.1.0 0 0 <p>Brian</p> <p>Could you please look at this one?</p> <p>Thanks</p> <p>Peter</p> <p>Chris,</p> <p>configure's --prefix is not meant to influence where the modules go &#8211; only the stuff that would normally be in one's /usr (i/e/ /usr/lib, /usr/bin, etc.)</p> <p>What you are looking for is typically implemented in Makefiles as "DESTDIR". i.e. "make install DESTDIR=/bghome/morrone/local. This something that is typically created for packaging systems so that they can install into a given tree and package it up without polluting the system tree.</p> <p>So looking to our lustre.spec.in for guidance, we can see in the %install scriptlet:</p> <p>make install DESTDIR=$RPM_BUILD_ROOT</p> <p>So, indeed our Makefiles use DESTDIR to install <b>everything</b> under another directory.</p> <p>Let me know if that resolves your issue.</p> <p>Well, it doesn't change the fact that "make install" just plain doesn't work when --prefix is used by itself. If nothing else, that seems to break the principle of least surprise.</p> <p>If --prefix is not functional, then perhaps it should be disabled...but thats pretty standard to autoconf, so that would be pretty odd.</p> <p>Is there a reason that --prefix can't set DESTDIR globally?</p> <p>Actually, right now --prefix and DESTDIR don't play well together, which seems to argue<br/> that it really SHOULD be disabled. If I specify the same path with both --prefix and DESTDIR, they will be concatonated for the non-modules, which is completely wrong.</p> <p>make install works just fine when configure is given a --prefix because configure's --prefix is only meant to relocate things that would usually go in /usr. An example of what configure's --prefix is for is if you wanted to install the libraries and binaries in /usr/local instead of /usr. Of course, in such a situation, installing the kernel modules in /usr/local/lib/modules would be wrong since the kernel would then not be able to find them.</p> <p>What you are looking to do, relocate the entire installation to a root other than /, really is exactly what make's DESTDIR is for.</p> <p>configure's --prefix shouldn't set DESTDIR because they are used for two different things.</p> <p>Per your example of setting --prefix and DESTDIR to the same thing and having them concatenated for non-modules... this is entirely the expected behavior given what configure's --prefix and make's DESTDIR are for.</p> <p>To further exemplify, Imagine you wanted your binaries and libraries, etc. in /usr/local/</p> {bin,lib,...} <p> and you wanted to stage an installation in "/var/tmp/install" (where you want the modules in /var/tmp/install/lib/modules/$(uname -r)/ because /var/tmp/install acts as the "virtual root" of your installation &#8211; i.e. somewhere you could to a "tar -C /var/tmp/install -cvf ... to tar it all up for relocation), you would do:</p> <p>$ configure --prefix=/usr/local ...<br/> $ make<br/> $ make install DESTDIR=/var/tmp/install</p> <p>Here you can see how --prefix and DESTDIR are used together to achieve different goals.</p> <blockquote> <p>$ configure --prefix=/usr/local ...<br/> $ make<br/> $ make install DESTDIR=/var/tmp/install</p></blockquote> <p>This is broken. I did this:</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java">$ configure --prefix=/bgusr/morrone/local $ make $ make install DESTDIR=/bgusr/morrone/local </pre> </div></div> <p>And things that should appear under /usr wound up here:</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java">/bgusr/morrone/local/bgusr/morrone/local </pre> </div></div> <p>Oh wait, I think I see what you meant by "stage" now.</p> <p>Seems odd for something that uses configure to work that way. Usually --prefix has the meaning that DESTDIR does in Lustre, and things like --prefix-exec are used to change various parts.</p> <p>But I suppose it'll do.</p> <p>I think you see the difference betwen --prefix and DESTDIR now but just to be pedantic about it...</p> <blockquote> <p>Seems odd for something that uses configure to work that way. Usually --prefix has the meaning that DESTDIR does in Lustre, and things like --prefix-exec are used to change various parts.</p></blockquote> <p>All of this is really not unique to Lustre but actually how most (autoconf based at least) FOSS packages work. If you look in just about any rpm SPEC file you will see this use of DESTDIR in the %install scriptlet. If you look at rpmbuild's output for any such packages (not just lustre) you will also see that rpmbuild typically calls configure explicitly with --prefix=/usr (and typically a ton of other location directives). i.e. Redhat's RPM calls configure with:</p> <p>+ ./configure ... --prefix=/usr --exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc --datadir=/usr/share --includedir=/usr/include --libdir=/usr/lib64 --libexecdir=/usr/libexec --localstatedir=/var --sharedstatedir=/usr/com --mandir=/usr/share/man --infodir=/usr/share/info ...</p> <p>So using DESTDIR is a workable solution for you?</p> <p>Yes, thanks, that is fine.</p> <p>Great. I just wanted to make sure my proposed solution was workable for you before I closed the ticket.</p> Development Rank 1|hzw17z: Rank (Obsolete) 10279 Severity