public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: scameron@beardog.cce.hp.com
Cc: fstests@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: Problem building xfsprogs
Date: Wed, 23 Jul 2014 06:56:05 +1000	[thread overview]
Message-ID: <20140722205605.GJ20518@dastard> (raw)
In-Reply-To: <20140722160641.GU17967@beardog.cce.hp.com>

[cc xfs@oss.sgi.com - list for XFS issues]

On Tue, Jul 22, 2014 at 11:06:41AM -0500, 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

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

       reply	other threads:[~2014-07-22 20:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20140722160641.GU17967@beardog.cce.hp.com>
2014-07-22 20:56 ` Dave Chinner [this message]
2014-07-22 21:09   ` Problem building xfsprogs scameron
2014-07-22 21:47     ` Dave Chinner
2014-07-23 14:01       ` scameron
2014-07-23 22:19         ` Dave Chinner
2014-07-22 21:50     ` Eric Sandeen
2014-07-22 21:14   ` Martin Furuhjelm
2014-07-22 21:18     ` Eric Sandeen
2014-07-22 21:20     ` scameron
2014-07-22 21:56     ` Dave Chinner

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=20140722205605.GJ20518@dastard \
    --to=david@fromorbit.com \
    --cc=fstests@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox