<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 01:34:26 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>Whamcloud Community JIRA</title>
    <link>https://jira.whamcloud.com</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>9.4.14</version>
        <build-number>940014</build-number>
        <build-date>05-12-2023</build-date>
    </build-info>


<item>
            <title>[LU-3497] Lustre build system hardcoded to using ZFS development headers in /usr/include only. </title>
                <link>https://jira.whamcloud.com/browse/LU-3497</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;Currently the LB_ZFS_USER macro test only for /usr/include patch for development headers. This puts a hard requirement of installing the zfs development rpm on any build box. For a non administrator on a build box this is not a option. Those needed headers are also available in the source tree of zfs so we can use that as a second option to allow a normal user to build lustre rpms.&lt;/p&gt;</description>
                <environment>Any build box.</environment>
        <key id="19525">LU-3497</key>
            <summary>Lustre build system hardcoded to using ZFS development headers in /usr/include only. </summary>
                <type id="1" iconUrl="https://jira.whamcloud.com/secure/viewavatar?size=xsmall&amp;avatarId=11303&amp;avatarType=issuetype">Bug</type>
                                            <priority id="2" iconUrl="https://jira.whamcloud.com/images/icons/priorities/critical.svg">Critical</priority>
                        <status id="5" iconUrl="https://jira.whamcloud.com/images/icons/statuses/resolved.png" description="A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.">Resolved</status>
                    <statusCategory id="3" key="done" colorName="success"/>
                                    <resolution id="1">Fixed</resolution>
                                        <assignee username="mdiep">Minh Diep</assignee>
                                    <reporter username="simmonsja">James A Simmons</reporter>
                        <labels>
                            <label>yuc2</label>
                    </labels>
                <created>Mon, 24 Jun 2013 14:13:13 +0000</created>
                <updated>Thu, 18 Dec 2014 18:21:09 +0000</updated>
                            <resolved>Tue, 3 Sep 2013 19:52:15 +0000</resolved>
                                    <version>Lustre 2.4.1</version>
                    <version>Lustre 2.5.0</version>
                                    <fixVersion>Lustre 2.5.0</fixVersion>
                    <fixVersion>Lustre 2.4.2</fixVersion>
                                        <due></due>
                            <votes>0</votes>
                                    <watches>5</watches>
                                                                            <comments>
                            <comment id="61090" author="simmonsja" created="Mon, 24 Jun 2013 14:25:06 +0000"  >&lt;p&gt;Patch at &lt;a href=&quot;http://review.whamcloud.com/#/c/6750/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/#/c/6750/&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="61091" author="pjones" created="Mon, 24 Jun 2013 14:28:18 +0000"  >&lt;p&gt;Thanks James! Minh could you please take care of this one?&lt;/p&gt;</comment>
                            <comment id="61317" author="mdiep" created="Tue, 25 Jun 2013 15:56:11 +0000"  >&lt;p&gt;Hi James,&lt;/p&gt;

&lt;p&gt;I hit this when I built without zfs/spl installed on the system&lt;/p&gt;

&lt;p&gt;checking zfs source directory... /mnt/build/build/lu3497/BUILD/usr/src/zfs-0.6.1/&lt;br/&gt;
checking zfs build directory... /mnt/build/build/lu3497/BUILD/usr/src/zfs-0.6.1/2.6.32-358.11.1.el6_lustre.g4b6bec2.x86_64&lt;br/&gt;
checking zfs source version... 0.6.1-24_gf9ca914&lt;br/&gt;
checking zfs file name for module symbols... Module.symvers&lt;br/&gt;
checking zfs devel headers... Not found&lt;br/&gt;
configure: error:&lt;/p&gt;

&lt;p&gt;Required zfs osd cannot be built due to missing zfs development headers.&lt;/p&gt;

&lt;p&gt;...&lt;/p&gt;


&lt;p&gt;&lt;span class=&quot;error&quot;&gt;&amp;#91;mpiuser@client-1 lu3497&amp;#93;&lt;/span&gt;$ ls BUILD/usr/src/zfs-0.6.1/&lt;br/&gt;
2.6.32-358.11.1.el6_lustre.g4b6bec2.x86_64  include  zfs_config.h.in  zfs.release.in&lt;br/&gt;
&lt;span class=&quot;error&quot;&gt;&amp;#91;mpiuser@client-1 lu3497&amp;#93;&lt;/span&gt;$ ls BUILD/usr/src/zfs-0.6.1/include/&lt;br/&gt;
linux  sys  zfeature_common.h  zfs_comutil.h  zfs_deleg.h  zfs_fletcher.h  zfs_namecheck.h  zfs_prop.h  zpios-ctl.h  zpios-internal.h&lt;br/&gt;
&lt;span class=&quot;error&quot;&gt;&amp;#91;mpiuser@client-1 lu3497&amp;#93;&lt;/span&gt;$ &lt;/p&gt;</comment>
                            <comment id="61324" author="simmonsja" created="Tue, 25 Jun 2013 17:24:40 +0000"  >&lt;p&gt;In the &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-1930&quot; title=&quot;Fix Lustre build of backend file systems&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-1930&quot;&gt;&lt;del&gt;LU-1930&lt;/del&gt;&lt;/a&gt; patch I seen similar behavior of the headers being in different locations. It was different for the tar ball versus the source rpm in the past. I was hoping that changed but guess not.&lt;/p&gt;</comment>
                            <comment id="61486" author="mdiep" created="Fri, 28 Jun 2013 15:28:41 +0000"  >&lt;p&gt;James,&lt;/p&gt;

&lt;p&gt;I have been looking into this and have a question:&lt;/p&gt;

&lt;p&gt;rpm2cpio /mnt/build/build/lu3497/BUILD/RPMS/x86_64/kmod-zfs-devel-0.6.1-24_gf9ca914.el6.x86_64.rpm&lt;br/&gt;
+ cpio -vid&lt;br/&gt;
./usr/src/zfs-0.6.1&lt;br/&gt;
./usr/src/zfs-0.6.1/include&lt;br/&gt;
./usr/src/zfs-0.6.1/include/linux&lt;br/&gt;
./usr/src/zfs-0.6.1/include/linux/blkdev_compat.h&lt;/p&gt;

&lt;p&gt;....&lt;/p&gt;

&lt;p&gt;+ rpm2cpio /mnt/build/build/lu3497/BUILD/RPMS/x86_64/zfs-devel-0.6.1-24_gf9ca914.el6.x86_64.rpm&lt;br/&gt;
+ cpio -vid&lt;br/&gt;
./lib64/libnvpair.so&lt;br/&gt;
./lib64/libuutil.so&lt;br/&gt;
./lib64/libzfs.so&lt;br/&gt;
./lib64/libzpool.so&lt;br/&gt;
./usr/include/libspl&lt;br/&gt;
./usr/include/libspl/assert.h&lt;br/&gt;
./usr/include/libspl/atomic.h&lt;/p&gt;

&lt;p&gt;Could you help me understand why we need zfs-devel and kmod-zfs-devel?&lt;br/&gt;
why kmod-zfs-devel does not include libspl and libzfs?&lt;/p&gt;

&lt;p&gt;should I rpm2cpio zfs-devel under /usr/src/zfs-$version so lustre build can find it?&lt;/p&gt;</comment>
                            <comment id="61490" author="simmonsja" created="Fri, 28 Jun 2013 16:12:10 +0000"  >&lt;p&gt;kmod is for handling kernel modules and their internals only. The normal zfs-devel is for building the user land utilities. Lustre needs both, one for osd-zfs and the other for the mount.lustre and friends.&lt;br/&gt;
Its my first time playing with kmod myself. I&apos;m getting the hang of it now.&lt;/p&gt;</comment>
                            <comment id="64796" author="mdiep" created="Wed, 21 Aug 2013 22:29:53 +0000"  >&lt;p&gt;Please review the latest update of the patch &lt;a href=&quot;http://review.whamcloud.com/#/c/6750/4&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/#/c/6750/4&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="65645" author="jlevi" created="Tue, 3 Sep 2013 19:52:15 +0000"  >&lt;p&gt;Patch landed to master. Please let me know if more work is needed in this ticket and I will reopen.&lt;/p&gt;</comment>
                            <comment id="65715" author="simmonsja" created="Wed, 4 Sep 2013 11:34:15 +0000"  >&lt;p&gt;Could we land this to 2.4 as well.&lt;/p&gt;</comment>
                            <comment id="65721" author="pjones" created="Wed, 4 Sep 2013 12:50:47 +0000"  >&lt;p&gt;We&apos;ll certainly consider this issue for 2.4.2 but it is too late to include it in 2.4.1&lt;/p&gt;</comment>
                            <comment id="71621" author="simmonsja" created="Fri, 15 Nov 2013 14:02:35 +0000"  >&lt;p&gt;Oleg can you see if &lt;a href=&quot;http://review.whamcloud.com/#/c/6750&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/#/c/6750&lt;/a&gt; can be cherry picked for 2.4.2.&lt;/p&gt;</comment>
                            <comment id="84178" author="brian" created="Thu, 15 May 2014 14:29:47 +0000"  >&lt;p&gt;So presumably the libraries needed to build userspace tools linked with libzfs are in the &lt;tt&gt;zfs-devel&lt;/tt&gt; package also, yes?&lt;/p&gt;

&lt;p&gt;I don&apos;t see how this patch enables the build of userspace tools wanting to &lt;tt&gt;-lzfs&lt;/tt&gt; to find the libs in the unpacked &lt;tt&gt;zfs-devel&lt;/tt&gt;.  Is it not part of this work or am I just missing it?  Maybe linking with &lt;tt&gt;-lzfs&lt;/tt&gt; has just not been necessary yet?&lt;/p&gt;</comment>
                            <comment id="84700" author="simmonsja" created="Thu, 22 May 2014 14:20:05 +0000"  >&lt;p&gt;At the time of the patch creating we didn&apos;t need to link to libzfs.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10010">
                    <name>Duplicate</name>
                                                                <inwardlinks description="is duplicated by">
                                        <issuelink>
            <issuekey id="19099">LU-3377</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                            <customfield id="customfield_10890" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10390" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|hzvtun:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10090" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>8794</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10060" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Severity</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10022"><![CDATA[3]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                        </customfields>
    </item>
</channel>
</rss>