<div dir="ltr">I have just recently gone through the process of attempting to build and run xfstests based on the current sources from <a href="http://oss.sgi.com" target="_blank">oss.sgi.com</a>.<div>Not having exactly the correct packages and kernel version creates problems. The build on FEDORA fails complaining about too many symlinks, I was successful on SUSE V 13 updated to kernel v3.15 and adding the following packages before attempting git and the build:
<div><br></div><div><span><span style="font-size:15px;font-family:'Courier New';color:rgb(0,0,0);font-weight:bold;vertical-align:baseline;white-space:pre-wrap;background-color:transparent">git gcc libtool automake make gettext-tools libattr-devel libacl-devel libuuid-devel ncurses-devel quota indent libcap-progs btrfsprogs</span></span><br>
</div><div><span><span style="font-size:15px;font-family:'Courier New';color:rgb(0,0,0);font-weight:bold;vertical-align:baseline;white-space:pre-wrap;background-color:transparent"><br></span></span></div><div>I then git and built xfsprogs followed by xfsdump and finally xfstests</div>
<div><br></div><div>After adding the fsgqa group and user the appropriate definitions of TEST_DEV and SCRATCH_DEV the quick test (<span style="color:rgb(0,0,0);font-family:'Courier New';font-size:15px;font-weight:bold;white-space:pre-wrap;background-color:transparent">./check -g quick</span>)</div>
<div>runs with 5 errors on xfs and one error on ext4.</div><div><br></div><div>If you just want xfstest to run - you may want to start with SUSE and the procedure above.</div><div><br></div><div>Martin Furuhjlem</div><div>
<br></div><div class="gmail_extra"><div class="gmail_quote">On Tue, Jul 22, 2014 at 2:56 PM, Dave Chinner <span dir="ltr"><<a href="mailto:david@fromorbit.com" target="_blank">david@fromorbit.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">[cc <a href="mailto:xfs@oss.sgi.com" target="_blank">xfs@oss.sgi.com</a> - list for XFS issues]<br>
<div><div><br>
On Tue, Jul 22, 2014 at 11:06:41AM -0500, <a href="mailto:scameron@beardog.cce.hp.com" target="_blank">scameron@beardog.cce.hp.com</a> wrote:<br>
><br>
> I'm trying to build xfsprogs (in order to run xfstests), and I'm running into this:<br>
><br>
> [scameron@localhost xfsprogs]$ git log --oneline | head -1<br>
> ba24eb7 logprint: Fix printing of AGF and AGI buffers<br>
> [scameron@localhost xfsprogs]$ git pull<br>
> Already up-to-date.<br>
> [scameron@localhost xfsprogs]$ git diff<br>
> [scameron@localhost xfsprogs]$ ./configure<br>
> checking build system type... x86_64-unknown-linux-gnu<br>
> checking host system type... x86_64-unknown-linux-gnu<br>
> checking for gcc... gcc<br>
> checking for C compiler default output file name... a.out<br>
><br>
> [...snip...]<br>
><br>
> checking for library containing blkid_probe_all... -lblkid<br>
> checking for blkid_probe_get_topology... yes<br>
> checking for readdir... yes<br>
> checking size of long... 8<br>
> checking size of char *... 8<br>
> checking for __psint_t ... no<br>
> checking for __psunsigned_t ... no<br>
> checking for __u32 ... yes<br>
> checking for umode_t... yes<br>
> configure: creating ./config.status<br>
> config.status: creating include/builddefs<br>
> config.status: creating include/platform_defs.h<br>
> config.status: include/platform_defs.h is unchanged<br>
> config.status: executing libtool commands<br>
> [scameron@localhost xfsprogs]$ make<br>
> Building include<br>
<br>
</div></div>Nothing built in the include directory - is this a clean build area?<br>
<div><br>
> Building libxfs<br>
> gmake[2]: *** No rule to make target `.ltdep', needed by `ltdepend'. Stop.<br>
> gmake[1]: *** [libxfs] Error 2<br>
> make: *** [default] Error 2<br>
><br>
> Any ideas what's wrong here?<br>
<br>
</div>The automatic dependency generation failed to generate the .ltdep<br>
file. But it can't be a clean build area, because the libxfs build<br>
rule is:<br>
<br>
default: crc32selftest ltdepend $(LTLIBRARY)<br>
<br>
and I don't see the crc32selftest rule being executed before the<br>
dependencies are generated. It shoul dlook something like:<br>
<br>
$ make<br>
....<br>
<div>configure: creating ./config.status<br>
config.status: creating include/builddefs<br>
config.status: creating include/platform_defs.h<br>
</div>config.status: executing libtool commands<br>
Building include<br>
[LN] xfs<br>
[LN] disk<br>
Building libxfs<br>
[CC] gen_crc32table<br>
[GENERATE] crc32table.h<br>
[TEST] CRC32<br>
CRC_LE_BITS = 32<br>
crc32: tests passed, 225944 bytes in 131 usec<br>
crc32c: tests passed, 225944 bytes in 131 usec<br>
[CC] cache.lo<br>
....<br>
<br>
So the first thing I'd do is run 'make realclean; make' to restart<br>
the build for a clean workarea first. If that doesn't fix the<br>
problem, then I'll need to know versions of libtool, gcc, etc that<br>
you are using and you'll need to post the output of "make realclean;<br>
make Q=" so we can see the command line that is actually failing.<br>
<br>
Cheers,<br>
<br>
Dave.<br>
--<br>
Dave Chinner<br>
<a href="mailto:david@fromorbit.com" target="_blank">david@fromorbit.com</a><br>
<div>--<br>
To unsubscribe from this list: send the line "unsubscribe fstests" in<br>
the body of a message to <a href="mailto:majordomo@vger.kernel.org" target="_blank">majordomo@vger.kernel.org</a><br>
</div>More majordomo info at <a href="https://urldefense.proofpoint.com/v1/url?u=http://vger.kernel.org/majordomo-info.html&k=2a4Akkj3oY%2FOkjwft1MTMw%3D%3D%0A&r=jY8ozfSdJMiFQxJbqMIFvF4Q5MYg6nOaolSGt082e48%3D%0A&m=bI0%2F1zZckAg2ytRBSMleHvthTKGuNDtYaUYrC%2BGOuV4%3D%0A&s=7e28774591d3b095daa0b053b597ecb5e73203b4a403132664165f44ac3aaa49" target="_blank">https://urldefense.proofpoint.com/v1/url?u=http://vger.kernel.org/majordomo-info.html&k=2a4Akkj3oY%2FOkjwft1MTMw%3D%3D%0A&r=jY8ozfSdJMiFQxJbqMIFvF4Q5MYg6nOaolSGt082e48%3D%0A&m=bI0%2F1zZckAg2ytRBSMleHvthTKGuNDtYaUYrC%2BGOuV4%3D%0A&s=7e28774591d3b095daa0b053b597ecb5e73203b4a403132664165f44ac3aaa49</a><br>
</blockquote></div><br></div></div></div>