All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Martin Furuhjelm <martin.furuhjelm@seagate.com>,
	Dave Chinner <david@fromorbit.com>
Cc: scameron@beardog.cce.hp.com, fstests@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: Problem building xfsprogs
Date: Tue, 22 Jul 2014 16:18:24 -0500	[thread overview]
Message-ID: <53CED520.5090707@sandeen.net> (raw)
In-Reply-To: <CAK2EqxR93J8441Ajj8no7_Pu1WSDLaVsKG=_FLMYvTnOUEzKGQ@mail.gmail.com>

On 7/22/14, 4:14 PM, Martin Furuhjelm wrote:
> I have just recently gone through the process of attempting to build and run xfstests based on the current sources from oss.sgi.com <http://oss.sgi.com>.
> 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:

FWIW, on fedora, simply:

# yum install xfsprogs xfsprogs-devel xfsprogs-qa-devel

should be enough (along w/ the other dependencies like libuuid, libacl, etc) to build xfstests.

-Eric

> git gcc libtool automake make gettext-tools libattr-devel libacl-devel libuuid-devel ncurses-devel quota indent libcap-progs btrfsprogs
> 
> I then git and built xfsprogs followed by xfsdump and finally xfstests
> 
> After adding the fsgqa group and user the appropriate definitions of TEST_DEV and SCRATCH_DEV the quick test (./check -g quick)
> runs with 5 errors on xfs and one error on ext4.
> 
> If you just want xfstest to run - you may want to start with SUSE and the procedure above.
> 
> Martin Furuhjlem
> 
> On Tue, Jul 22, 2014 at 2:56 PM, Dave Chinner <david@fromorbit.com <mailto:david@fromorbit.com>> wrote:
> 
>     [cc xfs@oss.sgi.com <mailto:xfs@oss.sgi.com> - list for XFS issues]
> 
>     On Tue, Jul 22, 2014 at 11:06:41AM -0500, scameron@beardog.cce.hp.com <mailto:scameron@beardog.cce.hp.com> wrote:
>     >
>     > I'm trying to build xfsprogs (in order to run xfstests), and I'm running into this:
>     >
>     > [scameron@localhost xfsprogs]$ git log --oneline | head -1
>     > ba24eb7 logprint: Fix printing of AGF and AGI buffers
>     > [scameron@localhost xfsprogs]$ git pull
>     > Already up-to-date.
>     > [scameron@localhost xfsprogs]$ git diff
>     > [scameron@localhost xfsprogs]$ ./configure
>     > checking build system type... x86_64-unknown-linux-gnu
>     > checking host system type... x86_64-unknown-linux-gnu
>     > checking for gcc... gcc
>     > checking for C compiler default output file name... a.out
>     >
>     > [...snip...]
>     >
>     > checking for library containing blkid_probe_all... -lblkid
>     > checking for blkid_probe_get_topology... yes
>     > checking for readdir... yes
>     > checking size of long... 8
>     > checking size of char *... 8
>     > checking for __psint_t ... no
>     > checking for __psunsigned_t ... no
>     > checking for __u32 ... yes
>     > checking for umode_t... yes
>     > configure: creating ./config.status
>     > config.status: creating include/builddefs
>     > config.status: creating include/platform_defs.h
>     > config.status: include/platform_defs.h is unchanged
>     > config.status: executing libtool commands
>     > [scameron@localhost xfsprogs]$ make
>     > Building include
> 
>     Nothing built in the include directory - is this a clean build area?
> 
>     > Building libxfs
>     > gmake[2]: *** No rule to make target `.ltdep', needed by `ltdepend'.  Stop.
>     > gmake[1]: *** [libxfs] Error 2
>     > make: *** [default] Error 2
>     >
>     > Any ideas what's wrong here?
> 
>     The automatic dependency generation failed to generate the .ltdep
>     file. But it can't be a clean build area, because the libxfs build
>     rule is:
> 
>     default: crc32selftest ltdepend $(LTLIBRARY)
> 
>     and I don't see the crc32selftest rule being executed before the
>     dependencies are generated. It shoul dlook something like:
> 
>     $ make
>     ....
>     configure: creating ./config.status
>     config.status: creating include/builddefs
>     config.status: creating include/platform_defs.h
>     config.status: executing libtool commands
>     Building include
>         [LN]     xfs
>         [LN]     disk
>     Building libxfs
>         [CC]     gen_crc32table
>         [GENERATE] crc32table.h
>         [TEST]    CRC32
>     CRC_LE_BITS = 32
>     crc32: tests passed, 225944 bytes in 131 usec
>     crc32c: tests passed, 225944 bytes in 131 usec
>         [CC]     cache.lo
>     ....
> 
>     So the first thing I'd do is run 'make realclean; make' to restart
>     the build for a clean workarea first. If that doesn't fix the
>     problem, then I'll need to know versions of libtool, gcc, etc that
>     you are using and you'll need to post the output of "make realclean;
>     make Q=" so we can see the command line that is actually failing.
> 
>     Cheers,
> 
>     Dave.
>     --
>     Dave Chinner
>     david@fromorbit.com <mailto:david@fromorbit.com>
>     --
>     To unsubscribe from this list: send the line "unsubscribe fstests" in
>     the body of a message to majordomo@vger.kernel.org <mailto:majordomo@vger.kernel.org>
>     More majordomo info at  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
> 
> 
> 
> 
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
> 


WARNING: multiple messages have this Message-ID (diff)
From: Eric Sandeen <sandeen@sandeen.net>
To: Martin Furuhjelm <martin.furuhjelm@seagate.com>,
	Dave Chinner <david@fromorbit.com>
Cc: scameron@beardog.cce.hp.com, fstests@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: Problem building xfsprogs
Date: Tue, 22 Jul 2014 16:18:24 -0500	[thread overview]
Message-ID: <53CED520.5090707@sandeen.net> (raw)
In-Reply-To: <CAK2EqxR93J8441Ajj8no7_Pu1WSDLaVsKG=_FLMYvTnOUEzKGQ@mail.gmail.com>

On 7/22/14, 4:14 PM, Martin Furuhjelm wrote:
> I have just recently gone through the process of attempting to build and run xfstests based on the current sources from oss.sgi.com <http://oss.sgi.com>.
> 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:

FWIW, on fedora, simply:

# yum install xfsprogs xfsprogs-devel xfsprogs-qa-devel

should be enough (along w/ the other dependencies like libuuid, libacl, etc) to build xfstests.

-Eric

> git gcc libtool automake make gettext-tools libattr-devel libacl-devel libuuid-devel ncurses-devel quota indent libcap-progs btrfsprogs
> 
> I then git and built xfsprogs followed by xfsdump and finally xfstests
> 
> After adding the fsgqa group and user the appropriate definitions of TEST_DEV and SCRATCH_DEV the quick test (./check -g quick)
> runs with 5 errors on xfs and one error on ext4.
> 
> If you just want xfstest to run - you may want to start with SUSE and the procedure above.
> 
> Martin Furuhjlem
> 
> On Tue, Jul 22, 2014 at 2:56 PM, Dave Chinner <david@fromorbit.com <mailto:david@fromorbit.com>> wrote:
> 
>     [cc xfs@oss.sgi.com <mailto:xfs@oss.sgi.com> - list for XFS issues]
> 
>     On Tue, Jul 22, 2014 at 11:06:41AM -0500, scameron@beardog.cce.hp.com <mailto:scameron@beardog.cce.hp.com> wrote:
>     >
>     > I'm trying to build xfsprogs (in order to run xfstests), and I'm running into this:
>     >
>     > [scameron@localhost xfsprogs]$ git log --oneline | head -1
>     > ba24eb7 logprint: Fix printing of AGF and AGI buffers
>     > [scameron@localhost xfsprogs]$ git pull
>     > Already up-to-date.
>     > [scameron@localhost xfsprogs]$ git diff
>     > [scameron@localhost xfsprogs]$ ./configure
>     > checking build system type... x86_64-unknown-linux-gnu
>     > checking host system type... x86_64-unknown-linux-gnu
>     > checking for gcc... gcc
>     > checking for C compiler default output file name... a.out
>     >
>     > [...snip...]
>     >
>     > checking for library containing blkid_probe_all... -lblkid
>     > checking for blkid_probe_get_topology... yes
>     > checking for readdir... yes
>     > checking size of long... 8
>     > checking size of char *... 8
>     > checking for __psint_t ... no
>     > checking for __psunsigned_t ... no
>     > checking for __u32 ... yes
>     > checking for umode_t... yes
>     > configure: creating ./config.status
>     > config.status: creating include/builddefs
>     > config.status: creating include/platform_defs.h
>     > config.status: include/platform_defs.h is unchanged
>     > config.status: executing libtool commands
>     > [scameron@localhost xfsprogs]$ make
>     > Building include
> 
>     Nothing built in the include directory - is this a clean build area?
> 
>     > Building libxfs
>     > gmake[2]: *** No rule to make target `.ltdep', needed by `ltdepend'.  Stop.
>     > gmake[1]: *** [libxfs] Error 2
>     > make: *** [default] Error 2
>     >
>     > Any ideas what's wrong here?
> 
>     The automatic dependency generation failed to generate the .ltdep
>     file. But it can't be a clean build area, because the libxfs build
>     rule is:
> 
>     default: crc32selftest ltdepend $(LTLIBRARY)
> 
>     and I don't see the crc32selftest rule being executed before the
>     dependencies are generated. It shoul dlook something like:
> 
>     $ make
>     ....
>     configure: creating ./config.status
>     config.status: creating include/builddefs
>     config.status: creating include/platform_defs.h
>     config.status: executing libtool commands
>     Building include
>         [LN]     xfs
>         [LN]     disk
>     Building libxfs
>         [CC]     gen_crc32table
>         [GENERATE] crc32table.h
>         [TEST]    CRC32
>     CRC_LE_BITS = 32
>     crc32: tests passed, 225944 bytes in 131 usec
>     crc32c: tests passed, 225944 bytes in 131 usec
>         [CC]     cache.lo
>     ....
> 
>     So the first thing I'd do is run 'make realclean; make' to restart
>     the build for a clean workarea first. If that doesn't fix the
>     problem, then I'll need to know versions of libtool, gcc, etc that
>     you are using and you'll need to post the output of "make realclean;
>     make Q=" so we can see the command line that is actually failing.
> 
>     Cheers,
> 
>     Dave.
>     --
>     Dave Chinner
>     david@fromorbit.com <mailto:david@fromorbit.com>
>     --
>     To unsubscribe from this list: send the line "unsubscribe fstests" in
>     the body of a message to majordomo@vger.kernel.org <mailto:majordomo@vger.kernel.org>
>     More majordomo info at  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
> 
> 
> 
> 
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
> 

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2014-07-22 21:18 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-22 16:06 Problem building xfsprogs scameron
2014-07-22 20:56 ` Dave Chinner
2014-07-22 20:56   ` Dave Chinner
2014-07-22 21:09   ` scameron
2014-07-22 21:09     ` scameron
2014-07-22 21:47     ` Dave Chinner
2014-07-22 21:47       ` Dave Chinner
2014-07-23 14:01       ` scameron
2014-07-23 14:01         ` scameron
2014-07-23 22:19         ` Dave Chinner
2014-07-23 22:19           ` Dave Chinner
2014-07-22 21:50     ` Eric Sandeen
2014-07-22 21:50       ` Eric Sandeen
2014-07-22 21:14   ` Martin Furuhjelm
2014-07-22 21:18     ` Eric Sandeen [this message]
2014-07-22 21:18       ` Eric Sandeen
2014-07-22 21:20     ` scameron
2014-07-22 21:20       ` scameron
2014-07-22 21:56     ` Dave Chinner
2014-07-22 21:56       ` Dave Chinner
2014-07-22 21:51 ` Theodore Ts'o
2014-07-22 22:04   ` Dave Chinner
2014-07-22 22:19     ` Theodore Ts'o
2014-07-22 23:04       ` Dave Chinner
2014-07-23  0:38         ` Theodore Ts'o
2014-07-23 14:08   ` scameron

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=53CED520.5090707@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=david@fromorbit.com \
    --cc=fstests@vger.kernel.org \
    --cc=martin.furuhjelm@seagate.com \
    --cc=scameron@beardog.cce.hp.com \
    --cc=xfs@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.