From: Dave Chinner <david@fromorbit.com>
To: Fernando Seiti Furusato <ferseiti@linux.vnet.ibm.com>
Cc: xfs@oss.sgi.com, Daniel Bast <daniel.bast@gmx.net>,
Breno Leitao <brenohl@br.ibm.com>,
793495@bugs.debian.org
Subject: Re: xfsprogs fails to build on debian ppc64el
Date: Sun, 2 Aug 2015 08:52:30 +1000 [thread overview]
Message-ID: <20150801225230.GR16638@dastard> (raw)
In-Reply-To: <55BBEF4F.6070809@linux.vnet.ibm.com>
On Fri, Jul 31, 2015 at 06:57:35PM -0300, Fernando Seiti Furusato wrote:
> That error is common when configure is generated using out-of-date config.guess
> and config.sub.
> The ones that come with the package are, in fact, old.
config.sub and config.guess are generated by the build, we don't
ship them directly from the git repository. Perhaps you are building
from a release tarball rather than from a clean git repository
working area? Can you confirm this is the case?
If so, can you remove the configure, config.sub and config.guess
files and see if you get the same problem?
> This package used to run dh_autotools-dev_updateconfig and
> dh_autotools-dev_restoreconfig, which worked because it only updates those
> files.
>
> They were replaced by dh_autoreconf and dh_autoreconf_clean, which should
> update them, but does not run flawlessly.
> I think something is wrong with the m4 macros but I am not sure what.
> There are errors when running dh_autoreconf alone.
>
> # dh_autoreconf
> libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `.'.
> libtoolize: copying file `./ltmain.sh'
> libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4'.
> libtoolize: copying file `m4/libtool.m4'
> libtoolize: copying file `m4/ltoptions.m4'
> libtoolize: copying file `m4/ltsugar.m4'
> libtoolize: copying file `m4/ltversion.m4'
> libtoolize: copying file `m4/lt~obsolete.m4'
> libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
> autoheader: warning: missing template: HAVE_UMODE_T
> autoheader: Use AC_DEFINE([HAVE_UMODE_T], [], [Description])
> autoheader: warning: missing template: HAVE___PSINT_T
> autoheader: warning: missing template: HAVE___PSUNSIGNED_T
> autoheader: warning: missing template: HAVE___U32
> autoreconf: /usr/bin/autoheader failed with exit status: 1
> dh_autoreconf: autoreconf -f -i returned exit code 1
>
> I will keep working on it, but all I will be able to do if I get to a conclusion
> is send a patch here.
> Thus it will have to be dealt with by the maintainers anyway.
The XFS list is cc'd on the bug, so the upstream maintainers are
watching and will see the patch when you post it. ;)
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2015-08-01 22:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-31 15:21 xfsprogs fails to build on debian ppc64el Daniel Bast
2015-07-31 21:57 ` Fernando Seiti Furusato
2015-08-01 22:52 ` Dave Chinner [this message]
2015-08-02 13:06 ` Bug#793495: " Daniel Bast
2015-08-02 22:13 ` Dave Chinner
2015-08-04 15:24 ` Fernando Seiti Furusato
2015-08-04 22:58 ` Dave Chinner
2015-08-05 13:00 ` Fernando Seiti Furusato
2015-08-05 13:47 ` Dave Chinner
2015-08-05 15:52 ` Fernando Seiti Furusato
2015-08-06 0:21 ` Dave Chinner
2015-08-06 7:10 ` Nathan Scott
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=20150801225230.GR16638@dastard \
--to=david@fromorbit.com \
--cc=793495@bugs.debian.org \
--cc=brenohl@br.ibm.com \
--cc=daniel.bast@gmx.net \
--cc=ferseiti@linux.vnet.ibm.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