<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 01:58:17 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-6216] Compilation error libtool on ppc64</title>
                <link>https://jira.whamcloud.com/browse/LU-6216</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;Upon building Lustre for ppc64 the following error breaks the build in Jenkins Job &apos;lustre-ppc&apos;:&lt;/p&gt;
&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;libtool: link: mpicc -g -Wall -fPIC -D_GNU_SOURCE -g -O2 -Werror -m64 -o mdsrate mdsrate.o  -L/var/lib/jenkins/workspace/lustre-ppc/arch/ppc64/build_type/client/distro/el6/ib_stack/inkernel/BUILD/BUILD/lustre-2.6.93/lustre/utils -llustreapi ../../../libcfs/libcfs/libcfs.a -lkeyutils
libtool: link: mpicc -g -Wall -fPIC -D_GNU_SOURCE -g -O2 -Werror -m64 -o cascading_rw cascading_rw.o lp_utils.o  -L/var/lib/jenkins/workspace/lustre-ppc/arch/ppc64/build_type/client/distro/el6/ib_stack/inkernel/BUILD/BUILD/lustre-2.6.93/lustre/utils -llustreapi ../../../libcfs/libcfs/libcfs.a -lkeyutils
cc1: warnings being treated as errors
llapi_hsm_test.c: In function &apos;test101_progress&apos;:
llapi_hsm_test.c:563: error: format &apos;%llu&apos; expects type &apos;long long unsigned int&apos;, but argument 8 has type &apos;__u64&apos;
llapi_hsm_test.c: In function &apos;test102_progress&apos;:
llapi_hsm_test.c:599: error: format &apos;%llu&apos; expects type &apos;long long unsigned int&apos;, but argument 8 has type &apos;__u64&apos;
llapi_hsm_test.c: In function &apos;test103_progress&apos;:
llapi_hsm_test.c:631: error: format &apos;%llu&apos; expects type &apos;long long unsigned int&apos;, but argument 8 has type &apos;__u64&apos;
llapi_hsm_test.c: In function &apos;test104_progress&apos;:
llapi_hsm_test.c:669: error: format &apos;%llu&apos; expects type &apos;long long unsigned int&apos;, but argument 8 has type &apos;__u64&apos;
llapi_hsm_test.c: In function &apos;test105_progress&apos;:
llapi_hsm_test.c:704: error: format &apos;%llu&apos; expects type &apos;long long unsigned int&apos;, but argument 8 has type &apos;__u64&apos;
llapi_hsm_test.c: In function &apos;test106_progress&apos;:
llapi_hsm_test.c:736: error: format &apos;%llu&apos; expects type &apos;long long unsigned int&apos;, but argument 8 has type &apos;__u64&apos;
llapi_hsm_test.c: In function &apos;test107_progress&apos;:
llapi_hsm_test.c:768: error: format &apos;%llu&apos; expects type &apos;long long unsigned int&apos;, but argument 8 has type &apos;__u64&apos;
llapi_hsm_test.c: In function &apos;test108_progress&apos;:
llapi_hsm_test.c:803: error: format &apos;%llu&apos; expects type &apos;long long unsigned int&apos;, but argument 8 has type &apos;__u64&apos;
llapi_hsm_test.c: In function &apos;test109_progress&apos;:
llapi_hsm_test.c:835: error: format &apos;%llu&apos; expects type &apos;long long unsigned int&apos;, but argument 8 has type &apos;__u64&apos;
llapi_hsm_test.c: In function &apos;test110_progress&apos;:
llapi_hsm_test.c:869: error: format &apos;%llu&apos; expects type &apos;long long unsigned int&apos;, but argument 9 has type &apos;__u64&apos;
llapi_hsm_test.c: In function &apos;test111_progress&apos;:
llapi_hsm_test.c:905: error: format &apos;%llu&apos; expects type &apos;long long unsigned int&apos;, but argument 9 has type &apos;__u64&apos;
llapi_hsm_test.c: In function &apos;test112_progress&apos;:
llapi_hsm_test.c:942: error: format &apos;%llu&apos; expects type &apos;long long unsigned int&apos;, but argument 9 has type &apos;__u64&apos;
llapi_hsm_test.c:961: error: format &apos;%llu&apos; expects type &apos;long long unsigned int&apos;, but argument 9 has type &apos;__u64&apos;
make[4]: *** [llapi_hsm_test.o] Error 1
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;Build log can be accessed via:&lt;br/&gt;
&lt;a href=&quot;https://build.hpdd.intel.com/job/lustre-ppc/138/arch=ppc64,build_type=client,distro=el6,ib_stack=inkernel/consoleFull&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://build.hpdd.intel.com/job/lustre-ppc/138/arch=ppc64,build_type=client,distro=el6,ib_stack=inkernel/consoleFull&lt;/a&gt;&lt;/p&gt;</description>
                <environment></environment>
        <key id="28578">LU-6216</key>
            <summary>Compilation error libtool on ppc64</summary>
                <type id="1" iconUrl="https://jira.whamcloud.com/secure/viewavatar?size=xsmall&amp;avatarId=11303&amp;avatarType=issuetype">Bug</type>
                                            <priority id="4" iconUrl="https://jira.whamcloud.com/images/icons/priorities/minor.svg">Minor</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="ys">Yang Sheng</assignee>
                                    <reporter username="heckes">Frank Heckes</reporter>
                        <labels>
                            <label>ppc</label>
                    </labels>
                <created>Thu, 5 Feb 2015 21:39:59 +0000</created>
                <updated>Tue, 3 Mar 2015 05:08:42 +0000</updated>
                            <resolved>Tue, 3 Mar 2015 05:08:42 +0000</resolved>
                                    <version>Lustre 2.7.0</version>
                                    <fixVersion>Lustre 2.7.0</fixVersion>
                    <fixVersion>Lustre 2.8.0</fixVersion>
                                        <due></due>
                            <votes>0</votes>
                                    <watches>8</watches>
                                                                            <comments>
                            <comment id="106058" author="jlevi" created="Fri, 6 Feb 2015 18:17:43 +0000"  >&lt;p&gt;Yang Sheng,&lt;br/&gt;
Could you please take this one?&lt;br/&gt;
Thank you!&lt;/p&gt;</comment>
                            <comment id="106815" author="ys" created="Thu, 12 Feb 2015 17:21:39 +0000"  >&lt;p&gt;We have ever build Lustre on ppc64 successful before. But maybe lost some thing in cleanup works. &lt;/p&gt;</comment>
                            <comment id="106890" author="adilger" created="Thu, 12 Feb 2015 23:45:44 +0000"  >&lt;p&gt;The llapi_hsm_test.c file was only just added in 2.6.92.  It makes sense to change these printf lines to cast the arguments into &lt;tt&gt;(unsigned long long)&lt;/tt&gt; to avoid the use of LPU64 in userspace.&lt;/p&gt;</comment>
                            <comment id="107247" author="fzago" created="Wed, 18 Feb 2015 17:09:22 +0000"  >&lt;p&gt;I&apos;ll take that one. I have some other changes in that file too.&lt;/p&gt;</comment>
                            <comment id="107248" author="fzago" created="Wed, 18 Feb 2015 17:10:09 +0000"  >&lt;p&gt;BTW, can the PPC build be accessible in the regular build page? I only see i386 and x86_64 builds.&lt;/p&gt;</comment>
                            <comment id="107253" author="simmonsja" created="Wed, 18 Feb 2015 18:06:02 +0000"  >&lt;p&gt;Totally agree. We need to add ppc64 to the mix since places like ORNL are picking up ppc64 machines.&lt;/p&gt;</comment>
                            <comment id="107316" author="gerrit" created="Thu, 19 Feb 2015 01:03:38 +0000"  >&lt;p&gt;frank zago (fzago@cray.com) uploaded a new patch: &lt;a href=&quot;http://review.whamcloud.com/13800&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/13800&lt;/a&gt;&lt;br/&gt;
Subject: &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-6216&quot; title=&quot;Compilation error libtool on ppc64&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-6216&quot;&gt;&lt;del&gt;LU-6216&lt;/del&gt;&lt;/a&gt; tests: compile fixes for PPC64, and for clang&lt;br/&gt;
Project: fs/lustre-release&lt;br/&gt;
Branch: master&lt;br/&gt;
Current Patch Set: 1&lt;br/&gt;
Commit: cf7eef56809503d016f36e10dddec1c73400597b&lt;/p&gt;</comment>
                            <comment id="107330" author="heckes" created="Thu, 19 Feb 2015 10:47:19 +0000"  >&lt;p&gt;PPC builds aren&apos;t part of the well known Jenkins jobs, but a separate one has been created : &apos;lustre-ppc&apos; (&lt;a href=&quot;https://build.hpdd.intel.com/job/lustre-ppc/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://build.hpdd.intel.com/job/lustre-ppc/&lt;/a&gt;). Drawback is that builds are on master and your change(s) won&apos;t be compiled on ppc64 till they&apos;re landed.&lt;/p&gt;</comment>
                            <comment id="107477" author="adilger" created="Fri, 20 Feb 2015 13:07:47 +0000"  >&lt;p&gt;Frank, it probably makes more sense to run the PPC builds on lustre-reviews rather than master, since it will essentially also test master (plus the current patch), but at least it has some chance of catching PPC regressions &lt;em&gt;before&lt;/em&gt; they land.&lt;/p&gt;

&lt;p&gt;If this patch fixes the PPC builds, after it lands it would also be good to get the PPC builds to comment into Gerrit if there is a build failure.&lt;/p&gt;</comment>
                            <comment id="107511" author="fzago" created="Fri, 20 Feb 2015 16:26:49 +0000"  >&lt;p&gt;I&apos;m all for it. A clang build-only on i386/x86_64 would be nice too.&lt;/p&gt;</comment>
                            <comment id="108203" author="gerrit" created="Fri, 27 Feb 2015 06:33:27 +0000"  >&lt;p&gt;Oleg Drokin (oleg.drokin@intel.com) merged in patch &lt;a href=&quot;http://review.whamcloud.com/13800/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/13800/&lt;/a&gt;&lt;br/&gt;
Subject: &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-6216&quot; title=&quot;Compilation error libtool on ppc64&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-6216&quot;&gt;&lt;del&gt;LU-6216&lt;/del&gt;&lt;/a&gt; tests: compile fixes for PPC64, and for clang&lt;br/&gt;
Project: fs/lustre-release&lt;br/&gt;
Branch: master&lt;br/&gt;
Current Patch Set: &lt;br/&gt;
Commit: b851f20baba124302c5a0882496503376d0f6616&lt;/p&gt;</comment>
                            <comment id="108526" author="pjones" created="Tue, 3 Mar 2015 05:08:42 +0000"  >&lt;p&gt;Landed for 2.7 and 2.8&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10011">
                    <name>Related</name>
                                                                <inwardlinks description="is related to">
                                                        </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|hzx5rz:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10090" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>17388</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>