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?
Just some observations from my side:
Extracting the released tarball over a clean xfsprogs git repo and removing the .gitignore file, then git status reveals:
Untracked files:
(use "git add <file>..." to include in what will be committed)
.gitcensus
aclocal.m4
config.guess
config.sub
configure
install-sh
ltmain.sh
m4/libtool.m4
m4/ltoptions.m4
m4/ltsugar.m4
m4/ltversion.m4
m4/lt~obsolete.m4
po/xfsprogs.pot
Looks like there are a lot of untracked file. Is this intentional, to have potentially auto-generated but un-versioned files in a release tarball?
It gets even more interesting, comparing debian source vs official release:
There are differences in the following files:
modified: aclocal.m4
modified: config.guess
modified: config.sub
modified: configure
modified: ltmain.sh
modified: m4/libtool.m4
modified: po/xfsprogs.pot
So, imho the debian source tarball also doesnât look clean, neither against the release tarball nor against a clean git checkout.
Just my 2 cents, maybe that helps someone to solve this.
Cheers,
Daniel