From: Eric Sandeen <sandeen@sandeen.net>
To: Emmanuel Florac <eflorac@intellique.com>, xfs@oss.sgi.com
Subject: Re: compiling xfs-progs 3.2.x
Date: Tue, 23 Sep 2014 12:25:35 -0500 [thread overview]
Message-ID: <5421AD0F.4040109@sandeen.net> (raw)
In-Reply-To: <20140923184149.05a57dba@harpe.intellique.com>
On 9/23/14 11:41 AM, Emmanuel Florac wrote:
>
> Hi list,
> xfs-progs 3.1.x compile easily, however I can't get around compiling
> 3.2.x (debian 7.6) :
>
> ./configure
> ./configure: line 2098: AC_PROG_LIBTOOL: command not found
> ./configure: line 2204: syntax error near unexpected token `xfsprogs'
> ./configure: line 2204: `AC_PACKAGE_GLOBALS(xfsprogs)'
>
> Any hint on where to start would be appreciated. Libtool version is the
> same as testing and unstable (2.4.2).
>
> Thanks,
>
I'm not at all autoconf savvy, so just guessing here.
there were very few changes to configure.ac since v3.1.11:
diff --git a/configure.ac b/configure.ac
index b968977..ae17c68 100644
--- a/configure.ac
+++ b/configure.ac
@@ -1,4 +1,4 @@
-AC_INIT([xfsprogs], [3.1.11])
+AC_INIT([xfsprogs], [3.2.0-alpha2])
AC_PREREQ(2.50)
AC_CONFIG_AUX_DIR([.])
AC_CONFIG_MACRO_DIR([m4])
@@ -112,12 +112,14 @@ AC_HAVE_FIEMAP
AC_HAVE_PREADV
AC_HAVE_SYNC_FILE_RANGE
AC_HAVE_BLKID_TOPO($enable_blkid)
+AC_HAVE_READDIR
AC_CHECK_SIZEOF([long])
AC_CHECK_SIZEOF([char *])
AC_TYPE_PSINT
AC_TYPE_PSUNSIGNED
AC_TYPE_U32
+AC_TYPE_UMODE_T
AC_MANUAL_FORMAT
AC_CONFIG_FILES([include/builddefs])
if you do a make realclean & re-make, does it help? (if you check out v3.1.11 and do the same, does it still build?)
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-09-23 17:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-23 16:41 compiling xfs-progs 3.2.x Emmanuel Florac
2014-09-23 17:25 ` Eric Sandeen [this message]
2014-09-23 19:28 ` Emmanuel Florac
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=5421AD0F.4040109@sandeen.net \
--to=sandeen@sandeen.net \
--cc=eflorac@intellique.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