All of lore.kernel.org
 help / color / mirror / Atom feed
From: scameron@beardog.cce.hp.com
To: fstests@vger.kernel.org
Cc: scameron@beardog.cce.hp.com
Subject: Problem building xfsprogs
Date: Tue, 22 Jul 2014 11:06:41 -0500	[thread overview]
Message-ID: <20140722160641.GU17967@beardog.cce.hp.com> (raw)


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
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?

-- steve


             reply	other threads:[~2014-07-22 16:08 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-22 16:06 scameron [this message]
2014-07-22 20:56 ` Problem building xfsprogs 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
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=20140722160641.GU17967@beardog.cce.hp.com \
    --to=scameron@beardog.cce.hp.com \
    --cc=fstests@vger.kernel.org \
    /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.